-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Format: 1.8 Date: Tue, 11 Aug 2026 23:32:38 +0200 Source: postgresql-17 Binary: libecpg-compat3 libecpg-compat3-dbgsym libecpg-dev libecpg-dev-dbgsym libecpg6 libecpg6-dbgsym libpgtypes3 libpgtypes3-dbgsym libpq-dev libpq5 libpq5-dbgsym postgresql-17 postgresql-17-dbgsym postgresql-client-17 postgresql-client-17-dbgsym postgresql-plperl-17 postgresql-plperl-17-dbgsym postgresql-plpython3-17 postgresql-plpython3-17-dbgsym postgresql-pltcl-17 postgresql-pltcl-17-dbgsym postgresql-server-dev-17 postgresql-server-dev-17-dbgsym Architecture: amd64 Version: 17.11-0+deb13u1 Distribution: trixie-security Urgency: medium Maintainer: amd64 / i386 Build Daemon (x86-csail-01) Changed-By: Christoph Berg Description: libecpg-compat3 - older version of run-time library for ECPG programs libecpg-dev - development files for ECPG (Embedded PostgreSQL for C) libecpg6 - run-time library for ECPG programs libpgtypes3 - shared library libpgtypes for PostgreSQL 17 libpq-dev - header files for libpq5 (PostgreSQL library) libpq5 - PostgreSQL C client library postgresql-17 - The World's Most Advanced Open Source Relational Database postgresql-client-17 - front-end programs for PostgreSQL 17 postgresql-plperl-17 - PL/Perl procedural language for PostgreSQL 17 postgresql-plpython3-17 - PL/Python 3 procedural language for PostgreSQL 17 postgresql-pltcl-17 - PL/Tcl procedural language for PostgreSQL 17 postgresql-server-dev-17 - development files for PostgreSQL 17 server-side programming Changes: postgresql-17 (17.11-0+deb13u1) trixie-security; urgency=medium . * New upstream version 17.11. . + Restrict logical decoding output plugins to the set specified by a new server parameter `output_plugin_libraries` (Jacob Champion) . Previously, a replication user could select any loadable library for logical decoding, allowing exploits of various sorts. To allow locking this down without breaking setups that worked before, introduce a whitelist of allowed output plugins. . By default, only the output plugins shipped as part of PostgreSQL (`pgoutput` and `test_decoding`) are included in `output_plugin_libraries`. Installations that rely on other output plugins must add them after updating the server, for example . output_plugin_libraries = 'pgoutput, test_decoding, my_trusted_decoder' . Additionally, pg_upgrade --check will fail if the `output_plugin_libraries` parameter on the new cluster does not permit the plugins of logical replication slots on the old cluster, when migrating from versions 17 and later. Make necessary additions to the new cluster's setting before performing pg_upgrade. . The PostgreSQL Project thanks Vladimir Tokarev and Yu Kunpeng for reporting this problem. (CVE-2026-6471) . + Fix contrib/pgcrypto's PGP encryption to detect unsupported ciphers (Daniel Gustafsson) . Previously, if OpenSSL rejected the requested cipher (for example, because it is running in FIPS mode, or the legacy provider hasn't been loaded), pgcrypto failed to notice the failure and simply XOR'd the non-encrypted block with the plaintext, rendering the "encryption" trivially breakable. This will typically occur with deprecated or non-FIPS cipher algorithms (cipher-algo=blowfish/bf, twofish, cast5, or 3des). . By default, pgcrypto will now fail to decrypt any messages that were affected in this way. To allow retrieval of such data, a new option `ignore-cipher-failure` has been added to pgp_pub_decrypt() and pgp_sym_decrypt(). Setting `ignore-cipher-failure=1` will restore their previous behavior, allowing the faulty encryption wrapper to be stripped off: . pgp_sym_decrypt(encrypted_column, any key, 'ignore-cipher-failure=1') . Once the affected messages are identified and stripped of their wrappers, they can then be re-encrypted with a modern algorithm. It is important however that the behavior of OpenSSL be the same as it was when the faulty messages were created: if the set of unsupported algorithms is not the same, this approach will not work. See the documentation for `ignore-cipher-failure`. . The PostgreSQL Project thanks Shishir Sharma for reporting this problem. (CVE-2026-14663) . + Fix psql to skip in-line data following a scripted COPY ... FROM STDIN command, even if the COPY fails before sending `PGRES_COPY_IN` (Tom Lane) . Previously, if a `COPY` command failed at startup (for instance, because the target table doesn't exist) psql would not realize that and would proceed to read the following in-line data as SQL commands. In the best case that's wrong and in the worst case it's a SQL-injection hazard. Teach psql to recognize syntactically-valid COPY ... FROM STDIN commands and to skip data on its own authority if the server doesn't respond with `PGRES_COPY_IN`. . While this fix is unlikely to affect any production SQL scripts, test scripts might intentionally exercise failing COPY ... FROM STDIN commands. Those will need to gain a `\.` data terminator line after each such command. . The PostgreSQL Project thanks Alexander Lakhin for reporting this problem. (CVE-2026-6464) . + Cross-check the output row type of a portal running EXECUTE or FETCH (Robert Haas) . EXECUTE and FETCH use two portals: an outer one for the statement itself, and an inner one running the query being executed on its behalf. It was previously possible to make the declared row types of the two portals diverge, leading to server memory disclosure and arbitrary code execution. . The PostgreSQL Project thanks Ben Morris (in collaboration with Claude and Anthropic Research) and Peter Geoghegan for reporting this problem. (CVE-2026-16239) . + Fix buffer overrun with long time zone abbreviation in to_char() (Tom Lane) . This can easily crash the server, and exploits leading to arbitrary code execution have been reported. . The PostgreSQL Project thanks Hcamael, Amjad Shahzad, Tan Zhen of AntAISecurityLab, Tomer Fichman, Zheng Yu, Amy Burnett (OpenAI Codex Security), Rick de Jager, Heewon Song, Sylvie Mayer, Aleksander Alekseev, and Hillai Ben Sasson for reporting this problem. (CVE-2026-14669) . + Fix buffer overrun in regexp match/split functions (Masahiko Sawada) . If passed invalidly-encoded data, these functions could write past the end of their conversion buffer. . The PostgreSQL Project thanks Francesco Verardi for reporting this problem. (CVE-2026-14664) . + Harden the ascii() function against invalid input (Michael Paquier) . By supplying invalidly-encoded input, this function could be coaxed to read and return a few bytes of data that it shouldn't. In assert-enabled builds, its assertions could be triggered too. . The PostgreSQL Project thanks Hcamael for reporting this problem. (CVE-2026-18024) . + Fix multirange type handling in pg_restore_attribute_stats() (OpenAI Security Research Team) . pg_restore_attribute_stats() treated multirange types just like their underlying range type. This works correctly for the bounds histogram, but it was wrong for all the other statistics kinds. . The PostgreSQL Project thanks Amy Burnett (OpenAI Codex Security) for reporting this problem. (CVE-2026-16238) . + Make scalarineqsel() check that a constant it expects to be of type tid actually is (Tom Lane) . This expectation will hold for all the built-in operators that use this estimator, but a maliciously-constructed operator could violate it, leading to a crash or server memory disclosure. . The PostgreSQL Project thanks Hcamael for reporting this problem. (CVE-2026-14668) . + Harden tsvector and tsquery code against overly long values (both individual lexemes and total vector/query length) (Tom Lane) . The documented limits were not enforced in all code paths. . The PostgreSQL Project thanks Yuhang Wu, Zhenpeng Lin, Zheng Yu, and Hcamael for reporting these problems. (CVE-2026-14662) . + Fix various places that mistakenly assumed they would not have to deal with more than `FUNC_MAX_ARGS` function arguments (Tom Lane) . Notably, the server's actual limit on the number of arguments to an aggregate function is `FUNC_MAX_ARGS - 1`, but the parser failed to enforce that, creating hazards downstream. . The PostgreSQL Project thanks Zheng Yu, ylwangtju, and Masahiko Sawada for reporting these problems. (CVE-2026-14679) . + Reject calls from SQL to functions that take or return type internal (Tom Lane) . The existing defenses against doing this have been shown to be insufficient, so add more explicit checks. . The PostgreSQL Project thanks Amy Burnett (OpenAI Codex Security) for reporting this problem. (CVE-2026-14680) . + Preserve the ownership of extended statistics objects when they are rebuilt by ALTER TABLE (Masahiko Sawada) . Previously, the role running ALTER TABLE gained ownership of such objects, but that seems inappropriate. . The PostgreSQL Project thanks Noah Misch for reporting this problem. (CVE-2026-6469) . + When deparsing an EXTRACT() function call, quote the field name if needed (Nathan Bossart) . The parser accepts any string literal as a field name in EXTRACT(), deferring validation to execution. If the call is stored and deparsed (for example during pg_dump), the string body was regurgitated verbatim, allowing SQL injection. . The PostgreSQL Project thanks Ben Morris (in collaboration with Claude and Anthropic Research) for reporting this problem. (CVE-2026-15741) . + Check for `USAGE` privilege on data types in places that formerly failed to check that (Nathan Bossart) . CREATE TYPE AS RANGE did not check, nor did ALTER TABLE OF, nor did commands that create stored expressions. These omissions allowed roles without `USAGE` privilege to nonetheless create objects depending on the type, possibly blocking the type's owner from changing the type later. . The PostgreSQL Project thanks Jingzhou Fu for reporting this problem. (CVE-2026-6470) . + Invalidate role-dependent cached plans after role changes (Ilya Staroverov, Shinya Kato, Nathan Bossart) . Role membership, role attribute, and database ownership changes may impact the expected behavior of row-level security policies, but previously we'd continue to use cached plans that were made according to the old state of affairs. . The PostgreSQL Project thanks Ilya Staroverov and Shinya Kato for reporting this problem. (CVE-2026-14666) . + Reject GSSEncRequest after direct SSL connection (Michael Paquier) . After establishing a TLS-encrypted connection, the server would still accept a request for GSSAPI encryption. If that succeeded, the connection would proceed using TLS encryption, but it would look like a GSS connection to the pg_hba rules. Thus, a pg_hba policy intending to disallow TLS would not be enforced correctly. . The PostgreSQL Project thanks p4p3r for reporting this problem. (CVE-2026-14681) . + Make mock SCRAM authentication secrets more plausible (Nathan Bossart) . If a SCRAM login is attempted against a role that doesn't exist or doesn't have a SCRAM secret, we generate a mock secret and carry out the authentication handshake anyway, to avoid revealing these facts to an attacker. But the mock secret was made with a fixed iteration count, which in itself can be an observable response discrepancy. Use the configuration setting `scram_iterations` instead, to make the mock secret look more like the installation's real secrets. . The PostgreSQL Project thanks Radim Marek for reporting this problem. (CVE-2026-14672) . + Fix out-of-bounds writes in ecpg applications caused by invalid bytea data received from the server (Michael Paquier) . ecpg assumed without checking that any bytea value must begin with `\x`. A broken or malicious server might send a string shorter than 2 bytes, resulting in memory clobber in the application. . The PostgreSQL Project thanks ylwangtju for reporting this problem. (CVE-2026-16241) . + Do not do backquote expansion on the argument of psql's \unrestrict command (Nathan Bossart) . This oversight in the fix for CVE-2025-8714 allows a malicious server to inject shell commands into plain-text dump output that will be run at restore time on the machine running psql, the exact scenario that CVE-2025-8714 intended to prevent. . The PostgreSQL Project thanks Lucas Velgus, Filip Janus, and Daniel Bakker for reporting this problem. (CVE-2026-18408) . + Remove pg_dump's assumption that pg_proc.protrftypes cannot have more than `FUNC_MAX_ARGS` entries (Tom Lane) . Since there could be entries for both input and output arguments, it's feasible for this array's length to exceed `FUNC_MAX_ARGS` (which constrains only input arguments). Even if that were not so, pg_dump cannot assume that the server was built with the same value of `FUNC_MAX_ARGS` that it has. An overrun would lead to a memory clobber inside pg_dump. . The PostgreSQL Project thanks Masahiko Sawada for reporting this problem. (CVE-2026-19385) . + Harden PL/Perl against "tied" Perl arrays and hashes (Tom Lane) . A tied object that doesn't behave like a regular one could lead to memory overwrite, or to constructing a corrupt result array (which would likely cause problems later). . The PostgreSQL Project thanks Hcamael for reporting this problem. (CVE-2026-14670) . + Fix integer overflows in memory-allocation calculations in PL/Perl and PL/Tcl (Heikki Linnakangas) . This is the same type of problem as CVE-2026-6473, just in a different part of the code, and is fixed in the same way. . The PostgreSQL Project thanks the Tulya Project (Team Dhiutsa, Bitecope Technologies Private Ltd) for reporting this problem. (CVE-2026-14677) . + Ensure that contrib/amcheck functions restrict `search_path` before executing index expressions (Noah Misch) . Because amcheck will run such index expressions as the owner of their tables, a caller could potentially hijack `search_path`-dependent functions to run arbitrary code as the table owner. By default this is not a vulnerability because only superusers are allowed to call amcheck functions; but if that privilege was granted out, it created a larger hazard than the documentation suggests. . The PostgreSQL Project thanks Yuelin Wang and Jacob Brazeal for reporting this problem. (CVE-2026-14673) . + Fix integer overflows in contrib/fuzzystrmatch's levenshtein() and levenshtein_less_equal() functions (Nathan Bossart) . Passing large cost values to these functions could cause integer overflows, thereby producing nonsensical results, and even causing out-of-bounds writes in some cases. . The PostgreSQL Project thanks Ben Morris (in collaboration with Claude and Anthropic Research) for reporting this problem. (CVE-2026-15742) . + Fix buffer overrun in contrib/pg_stat_statements (Álvaro Herrera) . Query normalization didn't accurately account for the amount of space the normalized string would require. . The PostgreSQL Project thanks Sajeeb Lohani (with TrendAI Zero Day Initiative) and Yuelin Wang for reporting this problem. (CVE-2026-14676) . + Fix datatype error in contrib/pg_trgm's GiST picksplit function (Heikki Linnakangas) . This mistake resulted in reading past the end of the buffer, typically causing bad split decisions; but a crash could ensue if you're very unlucky. . The PostgreSQL Project thanks Mehmet D. Ince for reporting this problem. (CVE-2026-14678) . + Remove the plan cache in contrib/refint (Ayush Tiwari) . This caching behavior has several serious bugs, notably that check_foreign_key() embeds the new key values in its cascade-UPDATE queries, so a cached plan reuses the originally-needed values rather than the key values that should be used. The simplest solution is to remove it. . The PostgreSQL Project thanks Hcamael for reporting this problem. (CVE-2026-14671) . * Fix psql -c 'truncate/create table; copy from stdin'. Checksums-Sha1: 91b7c0b3596e45f496711ea652f6c55210ecc797 16500 libecpg-compat3-dbgsym_17.11-0+deb13u1_amd64.deb 4858a514b3de26efcc339f87f1ffd04d3a97e959 24688 libecpg-compat3_17.11-0+deb13u1_amd64.deb 4db6da1eba70770d71b148aa43962538c8ee558b 279372 libecpg-dev-dbgsym_17.11-0+deb13u1_amd64.deb 30e5feceb31b0a92362477381208bcbf3072cb60 311604 libecpg-dev_17.11-0+deb13u1_amd64.deb 6534d63f380dd0c0a0fd0fe7efa0a46d35d7ba14 115328 libecpg6-dbgsym_17.11-0+deb13u1_amd64.deb 77533332f49b266ff7bb6d5f54b4fee2119c5ad6 70208 libecpg6_17.11-0+deb13u1_amd64.deb 1a25a5ac69fe72ec30c83276cecd5ae022dab2e1 90640 libpgtypes3-dbgsym_17.11-0+deb13u1_amd64.deb 253bb4b9418391db14c351a9cfd369d6dc6d6105 53320 libpgtypes3_17.11-0+deb13u1_amd64.deb 6ed1ab440e1fae66f260e691a14dfa7f7f97d3ec 159068 libpq-dev_17.11-0+deb13u1_amd64.deb 99ce12a189cb09cea7ea207c983b8c8c6a3141e9 299792 libpq5-dbgsym_17.11-0+deb13u1_amd64.deb ae2d1ea4f4bc3b4f26e5c4af1625515a80940e44 237376 libpq5_17.11-0+deb13u1_amd64.deb 33bef1ab4d5457c1df8ba747cb62dba47a9569be 19775088 postgresql-17-dbgsym_17.11-0+deb13u1_amd64.deb 924fc2411509356f9c1965fb7289ab9841808dd3 17611 postgresql-17_17.11-0+deb13u1_amd64-buildd.buildinfo 64c21255846b0fcc1df39e3712140a5255cea134 16678028 postgresql-17_17.11-0+deb13u1_amd64.deb bf46a586cc24a90d4d870437f08a82092ecc8484 3081912 postgresql-client-17-dbgsym_17.11-0+deb13u1_amd64.deb f4c7150d18ab72ccc25e0c03571293bac0f5edec 2071508 postgresql-client-17_17.11-0+deb13u1_amd64.deb 85c00bebccb28c9bf07326f523eaeac93cb98923 203856 postgresql-plperl-17-dbgsym_17.11-0+deb13u1_amd64.deb 1fb54f249108cd2c5c21a9591d688df31b0f3ccd 94128 postgresql-plperl-17_17.11-0+deb13u1_amd64.deb 1a4bd606f8c4b952c79a0258da1a16c03ee9900f 206096 postgresql-plpython3-17-dbgsym_17.11-0+deb13u1_amd64.deb 00342b2a0166cb764487c805be47bf76b3355e06 119348 postgresql-plpython3-17_17.11-0+deb13u1_amd64.deb cf7e6ebe899f08665634364824ef8c8ca54994e4 85076 postgresql-pltcl-17-dbgsym_17.11-0+deb13u1_amd64.deb 19455451c2944da2a505e55e39356854bc8cbb83 50588 postgresql-pltcl-17_17.11-0+deb13u1_amd64.deb d24c7bfc885506cf62a5e49019d9586f136ac293 55564 postgresql-server-dev-17-dbgsym_17.11-0+deb13u1_amd64.deb 7928d2d733f5fc2d5a32924f89eca2e35a991c18 1332720 postgresql-server-dev-17_17.11-0+deb13u1_amd64.deb Checksums-Sha256: fc6d349b88689aa5542cdde4133f60b52a13ccf4a6bb11fb1169b0db6d18ade1 16500 libecpg-compat3-dbgsym_17.11-0+deb13u1_amd64.deb 778eb4a120ae30b39b1e5a1f657c74b140f0f43a2ec15cc669f1413b490bcd29 24688 libecpg-compat3_17.11-0+deb13u1_amd64.deb f49b71a0d835ace2bd301572e27532ed6804e401b7a6a28a4f8228333e3778da 279372 libecpg-dev-dbgsym_17.11-0+deb13u1_amd64.deb 5f5899b4f546a2dd20ce00d9c917682ddc0e88246177ed1b70744141f9b86065 311604 libecpg-dev_17.11-0+deb13u1_amd64.deb 119e6b3abf8ca0b8d0ac6040399fee1bee849792befb28c1a4f0c5475980ec95 115328 libecpg6-dbgsym_17.11-0+deb13u1_amd64.deb 2cac8f93be69fd807c7626ccb8e4901a8499c392e6fe55d7be985b23a0b67631 70208 libecpg6_17.11-0+deb13u1_amd64.deb e820c9eba82b224e4651ee0317da8ec23a83cc0dfd789a6e44153360c18e5803 90640 libpgtypes3-dbgsym_17.11-0+deb13u1_amd64.deb 13a02413ef0f74c6dc2d8b5b192dd708c07f877b3fecb539ec370e3012adf5c9 53320 libpgtypes3_17.11-0+deb13u1_amd64.deb 54c0ee29d174e4fa0cfb8d6d37af5ad7b338ee3b29d392ae189425e122aee1f5 159068 libpq-dev_17.11-0+deb13u1_amd64.deb 5820ca4a1e8197bcd97c7b8952eb146e52fef207dcc4002c46892adff7fbf932 299792 libpq5-dbgsym_17.11-0+deb13u1_amd64.deb 20a4c9ef58b4baf90deda67cfb2cc062871c062830dddc234d28f5ac7931b86b 237376 libpq5_17.11-0+deb13u1_amd64.deb b4bd3b7e643b78f2c6556c3d5b15799d10541a69d0825a2369239667f0a0ea5d 19775088 postgresql-17-dbgsym_17.11-0+deb13u1_amd64.deb 29b98d049f3fc5e82bf94fa9b646e9aa244a5e74c092ec87d6e3d6678dd9f0fb 17611 postgresql-17_17.11-0+deb13u1_amd64-buildd.buildinfo d2ce1ddffafa783f9acda4c92c86fc21e8288bff3782d739294f14fa797d7886 16678028 postgresql-17_17.11-0+deb13u1_amd64.deb 245af19e7970db8fcc5323a43635c0358c3b5c9af69b09d678e0c8dce8c5440a 3081912 postgresql-client-17-dbgsym_17.11-0+deb13u1_amd64.deb 9d8558f8dd57c8e92e218a20698383575d53742ca3f9e7c2b7fe5f246d5216ae 2071508 postgresql-client-17_17.11-0+deb13u1_amd64.deb 5c98af8e5e08cf5c6f2eff31e027f75eadb074fc80abd6050bf0f55f102f495a 203856 postgresql-plperl-17-dbgsym_17.11-0+deb13u1_amd64.deb 99814a9bde4378f490a6d5abec04b008ba1251af627e8686576aaaf11310a1d7 94128 postgresql-plperl-17_17.11-0+deb13u1_amd64.deb 2741f06ef4ada724d84a08d3c4bc1fad429759294e04e54c377dda9888f2fe3b 206096 postgresql-plpython3-17-dbgsym_17.11-0+deb13u1_amd64.deb a005fb8cbaa8631449dee882a9c56233e5ba20299d5f28c15412b02aee65e8dd 119348 postgresql-plpython3-17_17.11-0+deb13u1_amd64.deb e0744c1ffeb21ddc34e2d8100c971ae8636f66802dbfd6b41ade48d3333d08aa 85076 postgresql-pltcl-17-dbgsym_17.11-0+deb13u1_amd64.deb 20b41ec085e147d74cbeed4b07a3272e2bd610daf1f38bde1013bfb92e4f429f 50588 postgresql-pltcl-17_17.11-0+deb13u1_amd64.deb c217414c5a5707d21253f481483585d570c308b31e3d1dfe07585251e730d3a5 55564 postgresql-server-dev-17-dbgsym_17.11-0+deb13u1_amd64.deb 59cb25f0a1def045aa334a9c025befc4a72dfc72d4a370f97d7d3f7342803d7e 1332720 postgresql-server-dev-17_17.11-0+deb13u1_amd64.deb Files: 2e62e35166e6fd0fb7ced13974294057 16500 debug optional libecpg-compat3-dbgsym_17.11-0+deb13u1_amd64.deb b08bbccd018b9080eae9e8d691b7ed65 24688 libs optional libecpg-compat3_17.11-0+deb13u1_amd64.deb d797ec79f92322ac06773b3dc362e483 279372 debug optional libecpg-dev-dbgsym_17.11-0+deb13u1_amd64.deb 5ac5afadb777a196b042d831e9d7335a 311604 libdevel optional libecpg-dev_17.11-0+deb13u1_amd64.deb 9eb81396df7e9a0b33238c257215138c 115328 debug optional libecpg6-dbgsym_17.11-0+deb13u1_amd64.deb e568fac1b3e63c437cce1d095ea64f6d 70208 libs optional libecpg6_17.11-0+deb13u1_amd64.deb 04d26d54f5c76c0f1e03eba3187f9395 90640 debug optional libpgtypes3-dbgsym_17.11-0+deb13u1_amd64.deb 8e9332d85335ad673f27ce60e579a4d6 53320 libs optional libpgtypes3_17.11-0+deb13u1_amd64.deb a04156443093078f7e3887e8140f7d1b 159068 libdevel optional libpq-dev_17.11-0+deb13u1_amd64.deb 083a8f65d8b5be424ad5680d4dfc0f45 299792 debug optional libpq5-dbgsym_17.11-0+deb13u1_amd64.deb 49845849569d3ae03ade43b352b276ee 237376 libs optional libpq5_17.11-0+deb13u1_amd64.deb 69b8904a33d09ec6bd2f1b63a3103384 19775088 debug optional postgresql-17-dbgsym_17.11-0+deb13u1_amd64.deb 9a5b7e1fed83aa96520bb403f48f18f5 17611 database optional postgresql-17_17.11-0+deb13u1_amd64-buildd.buildinfo 63fc9dc8effeac594530c08cc7634d5f 16678028 database optional postgresql-17_17.11-0+deb13u1_amd64.deb 020092047602cbe93a9c7c67f9ef3997 3081912 debug optional postgresql-client-17-dbgsym_17.11-0+deb13u1_amd64.deb 9740e4bdb64ac2337dedce090757d975 2071508 database optional postgresql-client-17_17.11-0+deb13u1_amd64.deb c98fd063e7afc918d94a7cdc1326c615 203856 debug optional postgresql-plperl-17-dbgsym_17.11-0+deb13u1_amd64.deb 6e4b63e7ac20b8c97bf49251203f303f 94128 database optional postgresql-plperl-17_17.11-0+deb13u1_amd64.deb f084d9f26665415264f4733f551e1d2d 206096 debug optional postgresql-plpython3-17-dbgsym_17.11-0+deb13u1_amd64.deb 962b707470d8d2c2df17e099b0c0d454 119348 database optional postgresql-plpython3-17_17.11-0+deb13u1_amd64.deb ce984f3978b6de4783e3a2df9f329af8 85076 debug optional postgresql-pltcl-17-dbgsym_17.11-0+deb13u1_amd64.deb 418517dd9018c2743de9caa0df73752f 50588 database optional postgresql-pltcl-17_17.11-0+deb13u1_amd64.deb 811a7c03fece50f5d8057696fee159cb 55564 debug optional postgresql-server-dev-17-dbgsym_17.11-0+deb13u1_amd64.deb 01a6c7a3c025507a9dfa88b3995554ba 1332720 libdevel optional postgresql-server-dev-17_17.11-0+deb13u1_amd64.deb -----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEEBDWXQb2umOtH4DRpYg9P9sm2dfEFAmp9ky4ACgkQYg9P9sm2 dfELRBAA3b2XXDIuxD0TK5mGCgz58YPrk4NBd8xI2cGg0qBr6irIp7JlBRu3gFBv GUKwkrVr79tWWQZPxGjlrCzmixonaVcU9M6mRW9olwJJBPAuq6tmQ9zPPG1I1Zzb q1NmjgubJEkgDz9ZEOiuGPFXwoZcrWEGcduP5K0lzE/xDN1g5zfy/5b+aVXoXQiN V53MhyCuGOe/AOExXzark8O+ZW5R9GdTwj+KL1LkWP276M91tPGT38qDKSZjpARf LllyEIUkhy6QbJBqzGp16z8jTN/yEMoI4SdzKVNyoQzIw/L5rbLvsCCxrnZclHxQ BX0i5lL04PKx3xeizPNqqNVWgN/4bfeBjjhPaKj+AcZrYgbj9Rl82KLxyWdmSQsY eAemgWg+eiUOH2caav4uhlGKewD3+SuSjRB26MGS2Wfz/63CzFsPBDvOJl6A2UT/ 6yonckwxPhqVeTa30FWn2aTPJCXuKMWx/li5M1Xqd6i7voISM26YQf2MY7V5VD93 ieTtRVUChkDxdBRNdRiU3wD8yu2mSyF7SXc0yG2J+sJyrX8NzpJ11DU/eZha6ucF dJU/VD6iuWAUXLDPpsGQkLKTroo2xjVIx0HL7bYJuteP2DVbCYJuLihHa6XALTsJ a8Lx0x67EKyU7rM2vOnxSLAupscNCkaxGGsLIew0y368BNOTtIA= =B52H -----END PGP SIGNATURE-----