Debian Package Tracker
Register | Log in
Subscribe

postgresql-18

The World's Most Advanced Open Source Relational Database

Choose email to subscribe with

general
  • source: postgresql-18 (main)
  • version: 18.6-3
  • maintainer: Debian PostgreSQL Maintainers (DMD)
  • uploaders: Peter Eisentraut [DMD] – Christoph Berg [DMD] – Martin Pitt [DMD]
  • arch: all any
  • std-ver: 4.7.4
  • VCS: Git (Browse, QA)
versions [more versions can be listed by madison] [old versions available from snapshot.debian.org]
[pool directory]
  • testing: 18.4-1
  • unstable: 18.6-3
versioned links
  • 18.4-1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
  • 18.6-3: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
binaries
  • libecpg-compat3
  • libecpg-dev
  • libecpg6
  • libpgtypes3
  • libpq-dev (2 bugs: 0, 2, 0, 0)
  • libpq-oauth
  • libpq5
  • postgresql-18 (5 bugs: 0, 5, 0, 0)
  • postgresql-18-jit
  • postgresql-client-18
  • postgresql-doc-18
  • postgresql-plperl-18
  • postgresql-plpython3-18
  • postgresql-pltcl-18
  • postgresql-server-dev-18
action needed
debian/patches: 7 patches with invalid metadata, 6 patches to forward upstream high

Among the 13 debian patches available in version 18.6-3 of the package, we noticed the following issues:

  • 7 patches with invalid metadata that ought to be fixed.
  • 6 patches where the metadata indicates that the patch has not yet been forwarded upstream. You should either forward the patch upstream or update the metadata to document its real status.
Created: 2025-09-23 Last update: 2026-08-16 09:19
28 security issues in forky high

There are 28 open security issues in forky.

28 important issues:
  • CVE-2026-6464: Untrusted data inclusion in PostgreSQL psql COPY may allow a server administrator to elicit execution of data lines as psql commands, via error injection. If the "COPY FROM STDIN" or "\copy FROM STDIN" command fails before the server indicates that it awaits input rows, psql processes the in-line data rows as psql commands. "COPY FROM" with a filename is unaffected. The server administrator has no inherent control over the data rows, so a complete attack requires the attacker to separately acquire control of both the server and the data rows. Alternatively, an attacker controlling data rows alone might complete an attack through a coincidental error that they don't control. Versions before PostgreSQL 18.5, 17.11, 16.15, 15.19, and 14.24 are affected.
  • CVE-2026-6469: Incorrect ownership assignment in PostgreSQL ALTER TABLE ALTER TYPE command reassigns ownership of dependent statistics objects to the current user. This wrongly allows the table owner to run DROP STATISTICS and ALTER STATISTICS via this improper ownership. It wrongly denies those commands to the prior statistics object owner. DROP TABLE remains able to remove statistics objects, so this exploit achieves nothing in many ownership arrangements. Versions before PostgreSQL 18.5, 17.11, 16.15, 15.19, and 14.24 are affected.
  • CVE-2026-6470: Missing authorization in PostgreSQL DDL commands allows an object creator to achieve denial of service against ALTER and DROP of the type, via creating a dependency on the type. Many DDL operations did check the privilege, but assigning a range subtype and referencing the type from an SQL expression did not. Versions before PostgreSQL 18.5, 17.11, 16.15, 15.19, and 14.24 are affected.
  • CVE-2026-6471: Missing authorization in PostgreSQL logical decoding allows a non-superuser holding REPLICATION privilege to dlopen any file visible to the operating system account running the server, via the choice of logical decoding plugin. This in turn runs arbitrary code as that account. Versions before PostgreSQL 18.5, 17.11, 16.15, 15.19, and 14.24 are affected.
  • CVE-2026-14662: Integer wraparound in PostgreSQL tsvector and tsquery data type functions allows an unprivileged database user to cause the server to undersize an allocation and write out-of-bounds, via crafted large inputs. This may execute arbitrary code as the operating system user running the database. These types are typically sourced from application logic, not taken from the application's user. Hence, application users attacking the database, through the application as a conduit, are unlikely. CVE-2026-6473 had fixed similar problems. Versions before PostgreSQL 18.5, 17.11, 16.15, 15.19, and 14.24 are affected.
  • CVE-2026-14663: Cleartext storage in PostgreSQL pgcrypto disabled ciphers allows a user to recover cleartext, via direct observation of the faulty ciphertext. The OpenSSL version and OpenSSL configuration determine the disabled ciphers. If the application accepts encrypted data as input, decryption will succeed even with the wrong key. This in turn loses the modest protection from the Modification Detection Code (MDC). Affected functions are pgp_sym_encrypt, pgp_sym_decrypt, pgp_pub_encrypt, pgp_pub_decrypt, pgp_sym_encrypt_bytea, pgp_sym_decrypt_bytea, pgp_pub_encrypt_bytea, and pgp_pub_decrypt_bytea. Versions before PostgreSQL 18.5, 17.11, 16.15, 15.19, and 14.24 are affected.
  • CVE-2026-14664: Heap buffer overflow in PostgreSQL regexp allows the query author to execute arbitrary code as the operating system user running the database, via text that would not pass encoding validation. This shares heritage with CVE-2026-2006, but this case involved unanticipated data growth when round-tripped through pg_wchar. Versions before PostgreSQL 18.5, 17.11, 16.15, 15.19, and 14.24 are affected.
  • CVE-2026-14666: Incomplete tracking in PostgreSQL of changes to role membership, role attributes, and database ownership allows a query to continue using cached row-level security policies after those changes require a different policy, via plan reuse. Stale policies continue until some other event invalidates the cache or connection termination ends the session. This permits a user to complete reads and modifications that were recently permitted but now forbidden. An attacker must tailor an attack to a particular application's pattern of privilege removal and role-specific row security policies. Versions before PostgreSQL 18.5, 17.11, 16.15, 15.19, and 14.24 are affected.
  • CVE-2026-14668: Type confusion regarding input of PostgreSQL ctid data type selectivity estimator allows an object creator to view a calculation derived from the value of an arbitrary 4-byte span of memory, via a chosen non-ctid input. While the calculation loses precision, substantial memory value recovery appears possible. Versions before PostgreSQL 18.5, 17.11, 16.15, 15.19, and 14.24 are affected.
  • CVE-2026-14669: Heap buffer overflow in PostgreSQL to_char(timestamptz) allows the party choosing the timezone to execute arbitrary code as the operating system user running the database, via a long POSIX timezone abbreviation. Versions before PostgreSQL 18.5, 17.11, 16.15, 15.19, and 14.24 are affected.
  • CVE-2026-14670: Heap buffer overflow in PostgreSQL plperl return of a tied hash allows the function owner to execute arbitrary code as the operating system user running the database, via a crafted function body. Versions before PostgreSQL 18.5, 17.11, 16.15, 15.19, and 14.24 are affected.
  • CVE-2026-14671: Type confusion in PostgreSQL module "refint" allows an object creator to execute arbitrary code as the operating system user running the database. The fix for this emerged as a non-security bug report, and the fix appear in the git repository with subject "refint: Remove plan cache.", without a CVE number. Versions before PostgreSQL 18.5, 17.11, 16.15, 15.19, and 14.24 are affected.
  • CVE-2026-14672: Observable response discrepancy in PostgreSQL SCRAM authentication allows an unauthenticated user to test the existence of a user via observing the SCRAM iteration count. This requires the probed user to have a non-default scram_iterations count, because the authentication challenge for a nonexistent user reports the default scram_iterations. Within major versions 16-18, minor versions before PostgreSQL 18.5, 17.11, and 16.15 are affected. Versions before PostgreSQL 16 are unaffected.
  • CVE-2026-14673: Untrusted search path in PostgreSQL amcheck allows a grantee of amcheck function EXECUTE privilege to execute arbitrary functions as the owners of expression indexes that depend on the search path, via setting a hostile search path before calling the amcheck function. Within major versions 18, 16, 15, and 14, minor versions before PostgreSQL 18.5, 16.15, 15.19, and 14.24 are affected. PostgreSQL 17 is unaffected.
  • CVE-2026-14676: Heap buffer overflow in PostgreSQL pg_stat_statements allows the query author to execute arbitrary code as the operating system user running the database, via crafted queries containing array constants. Within major version 18, minor versions before PostgreSQL 18.5 are affected. Versions before PostgreSQL 18 are unaffected.
  • CVE-2026-14677: Integer wraparound in PostgreSQL 32-bit builds of pltcl and plperl allows an object creator to cause the server to undersize an allocation and write out-of-bounds via crafted function bodies. This may execute arbitrary code as the operating system user running the database. CVE-2026-6473 had fixed similar problems. Versions before PostgreSQL 18.5, 17.11, 16.15, 15.19, and 14.24 are affected.
  • CVE-2026-14678: Buffer over-read in PostgreSQL pg_trgm index picksplit function reads past end of a heap buffer. This might allow a table maintainer to infer limited memory values, via the lossy signal of index split choices. Versions before PostgreSQL 18.5, 17.11, 16.15, 15.19, and 14.24 are affected.
  • CVE-2026-14679: Stack buffer overflow in PostgreSQL argument name matching allows an object creator to achieve unknown impacts via OUT parameter count. The attack can write only 0x0 and 0x1 bytes. Versions before PostgreSQL 18.5, 17.11, 16.15, 15.19, and 14.24 are affected.
  • CVE-2026-14680: Type confusion with PostgreSQL "internal" data type arguments allows any user to execute arbitrary code as the operating system user running the database, via calls to functions with that argument type. Type "internal" represents a class of mutually-incompatible data structures not intended for access from SQL. The system intended to prevent such function calls, but this prevention had gaps. Versions before PostgreSQL 18.5, 17.11, 16.15, 15.19, and 14.24 are affected.
  • CVE-2026-14681: Improper enforcement of message integrity in PostgreSQL GSSAPI support allows a user to negotiate GSSAPI contrary to pg_hba.conf rules, via initial direct TLS connection. Despite a pg_hba.conf that appears to require GSSAPI, the connection may exchange data over TLS encryption alone. If the TLS settings are more permissive than the GSS settings, the connection may continue with lesser protection. Within major versions 17-18, minor versions before PostgreSQL 18.5 and 17.11 are affected. Versions before PostgreSQL 17 are unaffected.
  • CVE-2026-15741: SQL injection in PostgreSQL EXTRACT() deparse allows an object owner to execute arbitrary SQL as a superuser via a hostile object definition. Attacks affect expression deparse consumers broadly, including pg_dump, psql commands like \sf, and any similar usage in non-core tools. Versions before PostgreSQL 18.5, 17.11, 16.15, 15.19, and 14.24 are affected.
  • CVE-2026-15742: Integer wraparound in PostgreSQL fuzzystrmatch allows a user to direct writes to a huge range of addresses, executing arbitrary code as the operating system user running the database, via extreme inputs to SQL function levenshtein() or levenshtein_less_equal(). Versions before PostgreSQL 18.5, 17.11, 16.15, 15.19, and 14.24 are affected.
  • CVE-2026-16238: Type confusion in PostgreSQL pg_restore_attribute_stats() allows an object creator to execute arbitrary code as the operating system user running the database, via conflation of range and multirange values. Within major version 18, minor versions before PostgreSQL 18.5 are affected. Versions before PostgreSQL 18 are unaffected.
  • CVE-2026-16239: Type confusion in PostgreSQL "portal"/cursor lifecycle allows a user to execute arbitrary code as the operating system user running the database, via re-creation of a cursor or other portal with different types. Versions before PostgreSQL 18.5, 17.11, 16.15, 15.19, and 14.24 are affected.
  • CVE-2026-16241: Integer underflow in PostgreSQL ECPG allows a database server administrator to achieve temporary denial of service against the ECPG client via sending a bytea value lacking the mandatory prefix. The client overwrites a huge memory region with bytes outside attacker knowledge or control. This typically yields a simple SIGSEGV, but rare cases might achieve client-specific integrity impact via the write. Versions before PostgreSQL 18.5, 17.11, 16.15, 15.19, and 14.24 are affected.
  • CVE-2026-18024: Buffer over-read in PostgreSQL ascii() SQL function allows a user to disclose up to 3 bytes after the end of a specific allocation, via a crafted text value. This is the same class of defect that CVE-2026-2006 fixed, though this instance has less impact. Versions before PostgreSQL 18.5, 17.11, 16.15, 15.19, and 14.24 are affected.
  • CVE-2026-18408: Untrusted data inclusion in pg_dump in PostgreSQL allows a malicious superuser of the origin server to inject arbitrary code for restore-time execution as the client operating system account running psql to restore the dump, via psql \restrict meta-command input expansion. The fix for CVE-2025-8714 introduced \restrict and \unrestrict to block this attack, but \unrestrict itself was sufficient for an attack. pg_dumpall is also affected. pg_restore is affected when used to generate a plain-format dump. Non-core use of \restrict would be affected, but we've not identified non-core use. Versions before PostgreSQL 18.5, 17.11, 16.15, 15.19, and 14.24 are affected.
  • CVE-2026-19385: Heap buffer overflow in PostgreSQL pg_dump of long function transform lists allows an object creator to execute arbitrary code as the operating system user running pg_dump, via a crafted transform list. Versions before PostgreSQL 18.5, 17.11, 16.15, 15.19, and 14.24 are affected.
Created: 2026-08-13 Last update: 2026-08-16 07:00
lintian reports 5 errors and 1 warning high
Lintian reports 5 errors and 1 warning about this package. You should make the package lintian clean getting rid of them.
Created: 2026-08-14 Last update: 2026-08-14 03:31
The package has not entered testing even though the delay is over normal
The package has not entered testing even though the 5-day delay is over. Check why.
Created: 2026-08-21 Last update: 2026-08-22 21:02
1 bug tagged patch in the BTS normal
The BTS contains patches fixing 1 bug, consider including or untagging them.
Created: 2026-08-15 Last update: 2026-08-22 21:00
Depends on packages which need a new maintainer normal
The packages that postgresql-18 depends on which need a new maintainer are:
  • systemtap (#1114760)
    • Build-Depends: systemtap-sdt-dev
  • docbook-xsl (#802370)
    • Build-Depends: docbook-xsl
Created: 2025-09-22 Last update: 2026-08-22 20:00
version in VCS is newer than in repository, is it time to upload? normal
vcswatch reports that this package seems to have a new changelog entry (version 18.6-4, distribution UNRELEASED) and new commits in its VCS. You should consider whether it's time to make an upload.

Here are the relevant commit messages:
commit cd08a4149882f9dd745fed86e4b1a1fc30600098
Author: Christoph Berg <myon@debian.org>
Date:   Mon Aug 17 10:20:48 2026 +0200

    Add noperl nopython notcl build profiles.

commit fcd42c1801ff51ab3bb5396f9308939e4e460781
Merge: 7d7a94e 835645c
Author: Christoph Berg <myon@debian.org>
Date:   Mon Aug 17 09:45:21 2026 +0200

    Merge tag 'debian/18.6-3' into 18
    
    tagging postgresql-18 18.6-3
    
    # -----BEGIN PGP SIGNATURE-----
    #
    # iQIzBAABCAAdFiEEXEj+YVf0kXlZcIfGTFprqxLSp64FAmqAywUACgkQTFprqxLS
    # p644/w//ZKxj1MuX3veZfcS2JkyK7IKqRRS9iBcHsgrSVRm+wQv7vr5HaAnnt6DL
    # McVGqmzijNc9mo7Zyvskm27dCqpqUpyrT2yZvpYim3kytLc7qartnoR8w80Zy03d
    # jla4E7mg4EjcRjPu7XOcrcTnVi0xfCckajJ6CmYXcuxQoepE6VFpt9vAaAAWwnGm
    # zO/qb5R4ARod8ZwR2LtuthiGBg2j7zin8ZSfvY9WyB2UFQNNfGZiRHOofz0/Ja2b
    # q38AuowVbZzwTJemkVl5QjQk+jb1tXtpuwMHpfAAcUwLoSLauGZ2wp+IfEgYQhUW
    # MAqexVgln/hYcIfjje0ivluvPpMj7EmxjkCBqAqAHU8xQBvRL6fgnnr+A2soGdGp
    # hLY0QZUjs1xPcXlqK3PzEgK1dEgE9AIjnJKDWmulDWbSMaQAw5taLnoGDBZGnh8m
    # h7EmaP/xTfsmQaiIGLCnZt3VARBuExdsy+VhK3YrBPNL5I7ZFw8E4NDlhrNfR5Xk
    # lyJo3Al8FaDh11fjzhUeui7a8uuf5ua5IARn9fZ/dnhm44Vc1+CK86JX1dQFnNDg
    # gZkanEFBU289/xCyJmNzrNxbiGFzAQyGEj7PioR2xJRXLHH5rx8volURSgKm+4rX
    # nfLhslcenComiP9Ser9FK0rm0wpmVXekwzk3i+dOVpmM4pbAzQw=
    # =lxyv
    # -----END PGP SIGNATURE-----
    # gpg: Signatur vom Sa 15 Aug 2026 22:24:37 CEST
    # gpg:                mittels RSA-Schlüssel 5C48FE6157F49179597087C64C5A6BAB12D2A7AE
    # gpg: Korrekte Signatur von "Christoph Berg <cb@df7cb.de>" [ultimativ]
    # gpg:                     alias "Christoph Berg <myon@debian.org>" [ultimativ]
    # gpg:                     alias "Christoph Berg <myon@oftc.net>" [ultimativ]

commit 7d7a94e54c66cdb607ed8417ecb8d12a13acfe85
Author: Christoph Berg <myon@debian.org>
Date:   Sat Aug 15 21:38:21 2026 +0200

    Actually remove patch

commit f126d3c9c52aea76eee038699ac621cf25815cec
Author: Christoph Berg <myon@debian.org>
Date:   Fri Aug 14 23:28:28 2026 +0200

    Drop psql-count-every-COPY-FROM-STDIN patch, went upstream


https://salsa.debian.org/api/v4/projects/postgresql%2Fpostgresql API request failed: 401 Unauthorized at /srv/qa.debian.org/data/vcswatch/vcswatch line 410.
Created: 2026-08-14 Last update: 2026-08-17 11:03
testing migrations
  • This package will soon be part of the auto-perl transition. You might want to ensure that your package is ready for it. You can probably find supplementary information in the debian-release archives or in the corresponding release.debian.org bug.
  • This package will soon be part of the auto-openssl transition. You might want to ensure that your package is ready for it. You can probably find supplementary information in the debian-release archives or in the corresponding release.debian.org bug.
  • excuses:
    • Migration status for postgresql-18 (18.4-1 to 18.6-3): Waiting for test results or another package, or too young (no action required now - check later)
    • Issues preventing migration:
    • ∙ ∙ Autopkgtest for address-standardizer/3.7.0-1: amd64: Pass, arm64: Pass, ppc64el: Pass, s390x: Test triggered
    • ∙ ∙ Autopkgtest for asterisk/1:22.10.1+dfsg+~cs6.17.60671434-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Test triggered (failure will be ignored)
    • ∙ ∙ Autopkgtest for bacula/15.0.3-5: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Test triggered
    • ∙ ∙ Autopkgtest for bgw-replstatus/1.0.8-2: amd64: Pass, arm64: Pass, ppc64el: Pass, s390x: Test triggered
    • ∙ ∙ Autopkgtest for credcheck/5.0-2: amd64: Pass, arm64: Pass, ppc64el: Pass, s390x: Test triggered
    • ∙ ∙ Autopkgtest for cyrus-imapd: arm64: Test triggered (failure will be ignored)
    • ∙ ∙ Autopkgtest for cyrus-sasl2/2.1.28+dfsg1-11: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Test triggered
    • ∙ ∙ Autopkgtest for db2fce/0.0.17-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Test triggered
    • ∙ ∙ Autopkgtest for dbconfig-common/2.0.26: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Test triggered
    • ∙ ∙ Autopkgtest for documentdb/0.114-0-1: amd64: Pass, arm64: Pass, ppc64el: Pass, s390x: Test triggered
    • ∙ ∙ Autopkgtest for dovecot/1:2.4.4+dfsg1-2: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Test triggered
    • ∙ ∙ Autopkgtest for emboss/6.6.0+dfsg-19: amd64: Pass, arm64: Pass, ppc64el: Pass, s390x: Test triggered
    • ∙ ∙ Autopkgtest for extra-window-functions/1.0-7: amd64: Pass, arm64: Pass, ppc64el: Pass, s390x: Test triggered
    • ∙ ∙ Autopkgtest for gnocchi/4.7.0-5: amd64: Pass, arm64: Pass, armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻, ppc64el: Pass, s390x: Test triggered
    • ∙ ∙ Autopkgtest for gnustep-dl2/0.12.0+git20250112-2: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Test triggered
    • ∙ ∙ Autopkgtest for gnustep-sqlclient/1.9.0-10: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Test triggered
    • ∙ ∙ Autopkgtest for h3-pg/4.2.3-4: amd64: Pass, arm64: Pass, ppc64el: Pass, s390x: Test triggered
    • ∙ ∙ Autopkgtest for hoel/1.4.29-3: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Test triggered
    • ∙ ∙ Autopkgtest for hydra/9.7-1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), s390x: Test triggered
    • ∙ ∙ Autopkgtest for hypopg/1.4.3-1: amd64: Pass, arm64: Pass, ppc64el: Pass, s390x: Test triggered
    • ∙ ∙ Autopkgtest for icinga2/2.16.4-1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), s390x: Test triggered
    • ∙ ∙ Autopkgtest for icu-ext/1.11.0-1: amd64: Pass, arm64: Pass, ppc64el: Pass, s390x: Test triggered
    • ∙ ∙ Autopkgtest for ip4r/2.4.3-1: amd64: Pass, arm64: Pass, ppc64el: Pass, s390x: Test triggered
    • ∙ ∙ Autopkgtest for jsquery/1.2-3: amd64: Pass, arm64: Pass, ppc64el: Pass, s390x: Test triggered
    • ∙ ∙ Autopkgtest for laniakea/0.1.1-5.1: amd64: Pass, arm64: Pass, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, s390x: Test triggered
    • ∙ ∙ Autopkgtest for libpqxx/8.0.2-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Test triggered
    • ∙ ∙ Autopkgtest for libreoffice/4:26.2.5.2-2: amd64: Pass, arm64: Test triggered (failure will be ignored), armhf: Test triggered (failure will be ignored), i386: Test triggered (failure will be ignored), ppc64el: Pass, s390x: Pass
    • ∙ ∙ Autopkgtest for londiste-sql/3.8-9: amd64: Pass, arm64: Pass, armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: Pass, s390x: Test triggered
    • ∙ ∙ Autopkgtest for medusa/2.3-3: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Test triggered
    • ∙ ∙ Autopkgtest for mimeo/1.5.1-20: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Test triggered
    • ∙ ∙ Autopkgtest for mongo-fdw/5.5.3-1: amd64: Pass, arm64: Pass, ppc64el: Pass, s390x: Test triggered
    • ∙ ∙ Autopkgtest for motion/4.7.1-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Test triggered
    • ∙ ∙ Autopkgtest for node-libpq/1.11.0+~1.8.13-1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), s390x: Test triggered
    • ∙ ∙ Autopkgtest for orafce/4.16.7-1: amd64: Pass, arm64: Pass, ppc64el: Pass, s390x: Test triggered
    • ∙ ∙ Autopkgtest for osm2pgrouting/3.0.0-2: amd64: Pass, arm64: Pass, ppc64el: Pass, s390x: Test triggered
    • ∙ ∙ Autopkgtest for pg-auto-failover/2.2-4: amd64: Pass, arm64: Pass, ppc64el: Pass, s390x: Test triggered
    • ∙ ∙ Autopkgtest for pg-background/2.0.2-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Test triggered
    • ∙ ∙ Autopkgtest for pg-catcheck/1.6.0-2: amd64: Pass, arm64: Pass, ppc64el: Pass, s390x: Test triggered
    • ∙ ∙ Autopkgtest for pg-checksums/1.3-2: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Test triggered
    • ∙ ∙ Autopkgtest for pg-crash/0.3-2: amd64: Pass, arm64: Pass, ppc64el: Pass, s390x: Test triggered
    • ∙ ∙ Autopkgtest for pg-cron/1.6.7-3: amd64: Pass, arm64: Pass, ppc64el: Pass, s390x: Test triggered
    • ∙ ∙ Autopkgtest for pg-csv/1.0.2-1: amd64: Pass, arm64: Pass, ppc64el: Pass, s390x: Test triggered
    • ∙ ∙ Autopkgtest for pg-dirtyread/2.8-1: amd64: Pass, arm64: Pass, ppc64el: Pass, s390x: Test triggered
    • ∙ ∙ Autopkgtest for pg-failover-slots/1.2.1-1: amd64: Pass, arm64: Pass, ppc64el: Pass, s390x: Test triggered
    • ∙ ∙ Autopkgtest for pg-hint-plan-18/1.8.0-3: amd64: Pass, arm64: Pass, ppc64el: Pass, s390x: Test triggered
    • ∙ ∙ Autopkgtest for pg-partman/5.5.0-1: amd64: Pass, arm64: Pass, ppc64el: Pass, s390x: Test triggered
    • ∙ ∙ Autopkgtest for pg-permissions/1.4.1-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Test triggered
    • ∙ ∙ Autopkgtest for pg-pwhash/1.0-2: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Test triggered
    • ∙ ∙ Autopkgtest for pg-qualstats/2.1.4-1: amd64: Pass, arm64: Pass, ppc64el: Pass, s390x: Test triggered
    • ∙ ∙ Autopkgtest for pg-rage-terminator/0.1.7-12: amd64: Pass, arm64: Pass, ppc64el: Pass, s390x: Test triggered
    • ∙ ∙ Autopkgtest for pg-rational/0.0.3-1: amd64: Pass, arm64: Pass, ppc64el: Pass, s390x: Test triggered
    • ∙ ∙ Autopkgtest for pg-repack/1.5.3-1: amd64: Pass, arm64: Pass, ppc64el: Pass, s390x: Test triggered
    • ∙ ∙ Autopkgtest for pg-show-plans/2.1.8-1: amd64: Pass, arm64: Pass, ppc64el: Pass, s390x: Test triggered
    • ∙ ∙ Autopkgtest for pg-similarity/1.0-9: amd64: Pass, arm64: Pass, ppc64el: Pass, s390x: Test triggered
    • ∙ ∙ Autopkgtest for pg-snakeoil/1.4-4: amd64: Pass, arm64: Pass, ppc64el: Pass, s390x: Test triggered
    • ∙ ∙ Autopkgtest for pg-stat-kcache/2.3.2-1: amd64: Pass, arm64: Pass, ppc64el: Pass, s390x: Test triggered
    • ∙ ∙ Autopkgtest for pg-stat-log/0.1-2: amd64: Pass, arm64: Pass, ppc64el: Pass, s390x: Test triggered
    • ∙ ∙ Autopkgtest for pg-stat-plans/2.1.0-1: amd64: Pass, arm64: Pass, ppc64el: Pass, s390x: Test triggered
    • ∙ ∙ Autopkgtest for pg-statviz/1.1-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Test triggered
    • ∙ ∙ Autopkgtest for pg-track-settings/2.1.2-5: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Test triggered
    • ∙ ∙ Autopkgtest for pg-uuidv7/1.7.0-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Test triggered
    • ∙ ∙ Autopkgtest for pg-wait-sampling/1.1.11-1: amd64: Pass, arm64: Pass, ppc64el: Pass, s390x: Test triggered
    • ∙ ∙ Autopkgtest for pgagent/4.2.3-5: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Test triggered
    • ∙ ∙ Autopkgtest for pgaudit-18/18.0-3: amd64: Pass, arm64: Pass, ppc64el: Pass, s390x: Test triggered
    • ∙ ∙ Autopkgtest for pgauditlogtofile/1.8.5-1: amd64: Pass, arm64: Pass, ppc64el: Pass, s390x: Test triggered
    • ∙ ∙ Autopkgtest for pgbackrest/2.59.0-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Test triggered
    • ∙ ∙ Autopkgtest for pgcopydb/0.18-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Test triggered
    • ∙ ∙ Autopkgtest for pgextwlist/1.20-1: amd64: Pass, arm64: Pass, ppc64el: Pass, s390x: Test triggered
    • ∙ ∙ Autopkgtest for pgfaceting/0.2.0-6: amd64: Pass, arm64: Pass, armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: Pass, s390x: Test triggered
    • ∙ ∙ Autopkgtest for pgfincore/1.4.0-1: amd64: Pass, arm64: Pass, ppc64el: Pass, s390x: Test triggered
    • ∙ ∙ Autopkgtest for pglogical/2.4.8-1: amd64: Pass, arm64: Pass, ppc64el: Pass, s390x: Test triggered
    • ∙ ∙ Autopkgtest for pgmemcache/2.3.0-16: amd64: Pass, arm64: Pass, ppc64el: Pass, s390x: Test triggered
    • ∙ ∙ Autopkgtest for pgnodemx/2.0.1-1: amd64: Pass, arm64: Pass, ppc64el: Pass, s390x: Test triggered
    • ∙ ∙ Autopkgtest for pgpcre/0.20190509-9: amd64: Pass, arm64: Pass, ppc64el: Pass, s390x: Test triggered
    • ∙ ∙ Autopkgtest for pgpointcloud/1.2.5-4: amd64: Pass, arm64: Pass, ppc64el: Pass, s390x: Test triggered
    • ∙ ∙ Autopkgtest for pgpool2/4.7.2-1: amd64: Pass, arm64: Pass, ppc64el: Pass, s390x: Test triggered
    • ∙ ∙ Autopkgtest for pgq/3.5.1-2: amd64: Pass, arm64: Pass, ppc64el: Pass, s390x: Test triggered
    • ∙ ∙ Autopkgtest for pgq-node/3.5-9: amd64: Pass, arm64: Pass, armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: Pass, s390x: Test triggered
    • ∙ ∙ Autopkgtest for pgrouting/4.0.1-1: amd64: Pass, arm64: Pass, ppc64el: Pass, s390x: Test triggered
    • ∙ ∙ Autopkgtest for pgsentinel/1.4.2-1: amd64: Pass, arm64: Pass, ppc64el: Pass, s390x: Test triggered
    • ∙ ∙ Autopkgtest for pgsphere/1.5.2-1: amd64: Pass, arm64: Pass, ppc64el: Pass, s390x: Test triggered
    • ∙ ∙ Autopkgtest for pgsql-asn1oid/1.6-3: amd64: Pass, arm64: Pass, ppc64el: Pass, s390x: Test triggered
    • ∙ ∙ Autopkgtest for pgstat/1.4.0-3: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Test triggered
    • ∙ ∙ Autopkgtest for pgtap/1.3.4-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Test triggered
    • ∙ ∙ Autopkgtest for pgtt/4.6-1: amd64: Pass, arm64: Pass, ppc64el: Pass, s390x: Test triggered
    • ∙ ∙ Autopkgtest for pgvector/0.8.6-1: amd64: Pass, arm64: Pass, ppc64el: Pass, s390x: Test triggered
    • ∙ ∙ Autopkgtest for pldebugger/1:1.10-1: amd64: Pass, arm64: Pass, ppc64el: Pass, s390x: Test triggered
    • ∙ ∙ Autopkgtest for plpgsql-check/2.10.4-1: amd64: Pass, arm64: Pass, ppc64el: Pass, s390x: Test triggered
    • ∙ ∙ Autopkgtest for plprofiler/4.2.5-4: amd64: Pass, arm64: Pass, ppc64el: Pass, s390x: Test triggered
    • ∙ ∙ Autopkgtest for plr/1:8.4.8.6-1: amd64: Pass, arm64: Pass, ppc64el: Pass, s390x: Test triggered
    • ∙ ∙ Autopkgtest for postfix/3.11.6-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Test triggered
    • ∙ ∙ Autopkgtest for postgresql-18/18.6-3: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • ∙ ∙ Autopkgtest for postgresql-18-age/1.8.0~rc0-2: amd64: Pass, arm64: Pass, ppc64el: Pass, s390x: Test triggered
    • ∙ ∙ Autopkgtest for postgresql-common/293: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Test triggered
    • ∙ ∙ Autopkgtest for postgresql-debversion/1.2.0-3: amd64: Pass, arm64: Pass, ppc64el: Pass, s390x: Test triggered
    • ∙ ∙ Autopkgtest for postgresql-mysql-fdw/2.9.3-2: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), s390x: Test triggered
    • ∙ ∙ Autopkgtest for postgresql-numeral/1.3-9: amd64: Pass, arm64: Pass, ppc64el: Pass, s390x: Test triggered
    • ∙ ∙ Autopkgtest for postgresql-pgmp/1.0.6-1: amd64: Pass, arm64: Pass, ppc64el: Pass, s390x: Test triggered
    • ∙ ∙ Autopkgtest for postgresql-pllua/1:2.0.12-7: amd64: Pass, arm64: Pass, ppc64el: Pass, s390x: Test triggered
    • ∙ ∙ Autopkgtest for postgresql-plproxy/2.12.0-1: amd64: Pass, arm64: Pass, ppc64el: Pass, s390x: Test triggered
    • ∙ ∙ Autopkgtest for postgresql-plsh/1.20220917-4: amd64: Pass, arm64: Pass, ppc64el: Pass, s390x: Test triggered
    • ∙ ∙ Autopkgtest for postgresql-q3c/2.0.5-1: amd64: Pass, arm64: Pass, ppc64el: Pass, s390x: Test triggered
    • ∙ ∙ Autopkgtest for postgresql-rum/1.3.15-1: amd64: Pass, arm64: Pass, ppc64el: Pass, s390x: Test triggered
    • ∙ ∙ Autopkgtest for postgresql-semver/0.41.0-1: amd64: Pass, arm64: Pass, ppc64el: Pass, s390x: Test triggered
    • ∙ ∙ Autopkgtest for postgresql-set-user/4.2.0-1: amd64: Pass, arm64: Pass, ppc64el: Pass, s390x: Test triggered
    • ∙ ∙ Autopkgtest for postgresql-unit/7.10-2: amd64: Pass, arm64: Pass, ppc64el: Pass, s390x: Test triggered
    • ∙ ∙ Autopkgtest for powa-archivist/5.2.0-1: amd64: Pass, arm64: Pass, ppc64el: Pass, s390x: Test triggered
    • ∙ ∙ Autopkgtest for prefix/1.2.11-1: amd64: Pass, arm64: Pass, ppc64el: Pass, s390x: Test triggered
    • ∙ ∙ Autopkgtest for preprepare/0.9-10: amd64: Pass, arm64: Pass, ppc64el: Pass, s390x: Test triggered
    • ∙ ∙ Autopkgtest for pspg/5.8.16-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Test triggered
    • ∙ ∙ Autopkgtest for psqlodbc/1:18.00.0002-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Test triggered
    • ∙ ∙ Autopkgtest for psycopg2/2.9.12-2: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Test triggered
    • ∙ ∙ Autopkgtest for psycopg3/3.3.4-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Test triggered
    • ∙ ∙ Autopkgtest for pygresql/1:6.2.3-2: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Test triggered
    • ∙ ∙ Autopkgtest for request-tracker5/5.0.10+dfsg-3: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Test triggered
    • ∙ ∙ Autopkgtest for ruby-pg/1.6.3-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Test triggered
    • ∙ ∙ Autopkgtest for ruby-sequel-pg/1.19.0-1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), s390x: Test triggered
    • ∙ ∙ Autopkgtest for rust-pq-sys/0.7.5-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Test triggered
    • ∙ ∙ Autopkgtest for soci/4.1.2-3: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Test triggered
    • ∙ ∙ Autopkgtest for sqitch/1.6.1-2: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Test triggered
    • ∙ ∙ Autopkgtest for sqlsmith/1.5-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Test triggered
    • ∙ ∙ Autopkgtest for tablelog/0.6.4-4: amd64: Pass, arm64: Pass, ppc64el: Pass, s390x: Test triggered
    • ∙ ∙ Autopkgtest for tdigest/1.4.4-1: amd64: Pass, arm64: Pass, ppc64el: Pass, s390x: Test triggered
    • ∙ ∙ Autopkgtest for tds-fdw/2.0.5-2: amd64: Pass, arm64: Pass, ppc64el: Pass, s390x: Test triggered
    • ∙ ∙ Autopkgtest for timestamp9/1.4.0-2: amd64: Pass, arm64: Pass, ppc64el: Pass, s390x: Test triggered
    • ∙ ∙ Autopkgtest for tntdb/1.4-3: amd64: No tests, superficial or marked flaky ♻ (reference ♻), arm64: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), s390x: Test triggered
    • ∙ ∙ Autopkgtest for toastinfo/1.7-1: amd64: Pass, arm64: Pass, ppc64el: Pass, s390x: Test triggered
    • ∙ ∙ Autopkgtest for w1retap/1.5.5-2.1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Test triggered
    • Additional info (not blocking):
    • ∙ ∙ Piuparts tested OK - https://piuparts.debian.org/sid/source/p/postgresql-18.html
    • ∙ ∙ Reproduced on amd64 - info
    • ∙ ∙ Reproduced on arm64 - info
    • ∙ ∙ Reproduced on armhf - info
    • ∙ ∙ Reproduced on i386 - info
    • ∙ ∙ 7 days old (needed 5 days)
    • Not considered
news
[rss feed]
  • [2026-08-15] Accepted postgresql-18 18.6-3 (source) into unstable (Christoph Berg)
  • [2026-08-14] Accepted postgresql-18 18.6-2 (source) into unstable (Christoph Berg)
  • [2026-08-13] Accepted postgresql-18 18.6-1 (source) into unstable (Christoph Berg)
  • [2026-05-26] postgresql-18 18.4-1 MIGRATED to testing (Debian testing watch)
  • [2026-05-14] Accepted postgresql-18 18.4-1 (source) into unstable (Christoph Berg)
  • [2026-03-01] postgresql-18 18.3-1 MIGRATED to testing (Debian testing watch)
  • [2026-02-26] Accepted postgresql-18 18.3-1 (source) into unstable (Christoph Berg)
  • [2026-02-21] postgresql-18 18.2-1 MIGRATED to testing (Debian testing watch)
  • [2026-02-12] Accepted postgresql-18 18.2-1 (source) into unstable (Christoph Berg)
  • [2025-12-14] postgresql-18 18.1-2 MIGRATED to testing (Debian testing watch)
  • [2025-12-11] Accepted postgresql-18 18.1-2 (source) into unstable (Christoph Berg)
  • [2025-11-16] postgresql-18 18.1-1 MIGRATED to testing (Debian testing watch)
  • [2025-11-13] Accepted postgresql-18 18.1-1 (source) into unstable (Christoph Berg)
  • [2025-09-29] postgresql-18 18.0-1 MIGRATED to testing (Debian testing watch)
  • [2025-09-29] postgresql-18 18.0-1 MIGRATED to testing (Debian testing watch)
  • [2025-09-26] Accepted postgresql-18 18.0-1 (source) into unstable (Christoph Berg)
  • [2025-09-26] postgresql-18 18~rc1-3 MIGRATED to testing (Debian testing watch)
  • [2025-09-23] Accepted postgresql-18 18~rc1-3 (source) into unstable (Christoph Berg)
  • [2025-09-22] Accepted postgresql-18 18~rc1-2 (source) into unstable (Christoph Berg)
  • [2025-09-04] Accepted postgresql-18 18~rc1-1 (source) into experimental (Christoph Berg)
  • [2025-08-12] Accepted postgresql-18 18~beta3-1 (source) into experimental (Christoph Berg)
  • [2025-07-18] Accepted postgresql-18 18~beta2-1 (source) into experimental (Christoph Berg)
  • [2025-07-01] Accepted postgresql-18 18~beta1+20250701-1 (source) into experimental (Christoph Berg)
  • [2025-06-24] Accepted postgresql-18 18~beta1+20250624-1 (source) into experimental (Christoph Berg)
  • [2025-06-12] Accepted postgresql-18 18~beta1+20250612-1 (source) into experimental (Christoph Berg)
  • [2025-05-08] Accepted postgresql-18 18~beta1-1 (source) into experimental (Christoph Berg)
  • [2025-05-03] Accepted postgresql-18 18~~devel.20250502-1 (source amd64 all) into experimental (Debian FTP Masters) (signed by: Christoph Berg)
  • [2025-04-21] Accepted postgresql-18 18~~devel.20250421-1 (source) into experimental (Christoph Berg)
  • [2025-04-05] Accepted postgresql-18 18~~devel.20250405-1 (source) into experimental (Christoph Berg)
  • [2025-03-31] Accepted postgresql-18 18~~devel.20250331-1 (source) into experimental (Christoph Berg)
  • 1
  • 2
bugs [bug history graph]
  • all: 5
  • RC: 0
  • I&N: 5
  • M&W: 0
  • F&P: 0
  • patch: 1
links
  • homepage
  • lintian (5, 1)
  • buildd: logs, reproducibility, cross
  • popcon
  • browse source code
  • other distros
  • security tracker
  • l10n (100, 97)
  • debian patches
  • debci
ubuntu Ubuntu logo [Information about Ubuntu for Debian Developers]
  • version: 18.4-1ubuntu2
  • patches for 18.4-1ubuntu2

Debian Package Tracker — Copyright 2013-2025 The Distro Tracker Developers
Report problems to the tracker.debian.org pseudo-package in the Debian BTS.
Documentation — Bugs — Git Repository — Contributing