-----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: i386 Version: 17.11-0+deb13u1 Distribution: trixie-security Urgency: medium Maintainer: all / amd64 / i386 Build Daemon (x86-grnet-03) 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: f06c2d39cc48a3cd153ac8757a69d088282a4fc2 14348 libecpg-compat3-dbgsym_17.11-0+deb13u1_i386.deb 38213c6b3462735c25ff35f7e3c5380fb9e896f8 25268 libecpg-compat3_17.11-0+deb13u1_i386.deb 4aa1d40c7500c3d68927e0cb6ef7deb4429724f3 276192 libecpg-dev-dbgsym_17.11-0+deb13u1_i386.deb c0575e105e964b98a4d14e99c9d50315c0e1c676 319956 libecpg-dev_17.11-0+deb13u1_i386.deb 0bfdf1c41fe84f96298f4031a6fd11ac8f7497a6 103424 libecpg6-dbgsym_17.11-0+deb13u1_i386.deb c5de2868b251114a88abd459c6f66705117a6ed8 74008 libecpg6_17.11-0+deb13u1_i386.deb 3b3b29512312e6bbb93cbebfd12b1100bc348fe1 83428 libpgtypes3-dbgsym_17.11-0+deb13u1_i386.deb c2c14ff9242c304b7b3160a3a40ef27c3b71c7ae 55564 libpgtypes3_17.11-0+deb13u1_i386.deb e2dcf4ba4c8d058a8ef644fa644c6a9f5198a9f0 169264 libpq-dev_17.11-0+deb13u1_i386.deb bbb8196ee25db808ccba1cc3dab774dc2f28369b 261968 libpq5-dbgsym_17.11-0+deb13u1_i386.deb 2ab6825cafcf0c994daa7186cedfb85c5e463b0e 247012 libpq5_17.11-0+deb13u1_i386.deb 0b852b686e6df4d72bef696dad9f272ec20aa1a0 17793336 postgresql-17-dbgsym_17.11-0+deb13u1_i386.deb de6c65b582461833699f5f486366f8ee72b151e1 17449 postgresql-17_17.11-0+deb13u1_i386-buildd.buildinfo b97e18c54f70fdc208f2635b0d5f33baa2148640 16928564 postgresql-17_17.11-0+deb13u1_i386.deb 91143f1796f80d10fdfcd3ee445fcc32a4f840ad 2644964 postgresql-client-17-dbgsym_17.11-0+deb13u1_i386.deb 0dc12fc26369d2efc8cf434d9a1390182c466265 2099664 postgresql-client-17_17.11-0+deb13u1_i386.deb 3d9d875039950001c16ebc360aa9c72b17db21c5 190896 postgresql-plperl-17-dbgsym_17.11-0+deb13u1_i386.deb 515be0b6d7b29ffe36bfbbf53c1fd6b7aded89fe 97176 postgresql-plperl-17_17.11-0+deb13u1_i386.deb 9dd2ee0e149a248a5f09ee0f8b6c42c4d464198a 188948 postgresql-plpython3-17-dbgsym_17.11-0+deb13u1_i386.deb 8a05cf3d0462b98e56de945b361f2110f15d5cec 121960 postgresql-plpython3-17_17.11-0+deb13u1_i386.deb 5e66d0ab79c0b5c1b072f1e587aba8cc8b1f1656 77760 postgresql-pltcl-17-dbgsym_17.11-0+deb13u1_i386.deb c9bd849a5cbf37034845df75d770ed38ea300b7e 52132 postgresql-pltcl-17_17.11-0+deb13u1_i386.deb 32256943000c67417afccbc8fe3ec46d5292e220 53868 postgresql-server-dev-17-dbgsym_17.11-0+deb13u1_i386.deb 020f3b66efb0d8d5e1e4751467e73d28edc81839 1349404 postgresql-server-dev-17_17.11-0+deb13u1_i386.deb Checksums-Sha256: c3de37cd2b9f55f3aa4298b78709bd1c30eb5c02ea83a73cf7ea88ea7d9c26a8 14348 libecpg-compat3-dbgsym_17.11-0+deb13u1_i386.deb d10927976deea87e0e990ef005d03c9befa0bf9d6aaca6e042ef61a8e5e40de5 25268 libecpg-compat3_17.11-0+deb13u1_i386.deb d676017fc599dba7f19cf886e3270b4e11c2e76a1b67e339946ab69fd1b1d50a 276192 libecpg-dev-dbgsym_17.11-0+deb13u1_i386.deb e550d5e896b9a55de7c30f0514964c0590d19836760c58b114ebd0ba7f6cd7d8 319956 libecpg-dev_17.11-0+deb13u1_i386.deb 4fecf4f20999323133928cdb98ec19d4d68da38850b8a48d70fbf90dd9bb5d6a 103424 libecpg6-dbgsym_17.11-0+deb13u1_i386.deb 7904db3c6e04b5b12b2c8051045443021ede6c732635c7edbb944e2c70072b1d 74008 libecpg6_17.11-0+deb13u1_i386.deb a8d6f6f771c455dc709da22e026367a7d6a5b053a6ea938aae353de69e4f8c44 83428 libpgtypes3-dbgsym_17.11-0+deb13u1_i386.deb 88d46ec5efba91aa803a0440208930361d1bcf436b9e1ed377c193b7adb66cfe 55564 libpgtypes3_17.11-0+deb13u1_i386.deb d9f20de3c7b205d0bbcf664cd60e6c3b02f7c2f528c452bab8300be7196b35c9 169264 libpq-dev_17.11-0+deb13u1_i386.deb 7095ab021aeb2c22a4017dc7e8df8e30e8dadfe92c45813e02fb87e478a7e952 261968 libpq5-dbgsym_17.11-0+deb13u1_i386.deb 1145cad9c1b675172539eebb45f521d76078d7227b3d86fbf2c51d5440ceff01 247012 libpq5_17.11-0+deb13u1_i386.deb f5f39348124012025e377327e913b9586229a48de817a5c3a9f4ee7587493543 17793336 postgresql-17-dbgsym_17.11-0+deb13u1_i386.deb 2ffbd46fd07bd103e5ffe18c75fd848008ecd45c205ccba0fad4dd33306c089e 17449 postgresql-17_17.11-0+deb13u1_i386-buildd.buildinfo 91cc4c36ea409d09a789f9a5976311cfd1834f0f02e38b9cdca39f5d480f9091 16928564 postgresql-17_17.11-0+deb13u1_i386.deb dea60986bbaa3ced1b66d908f12671c54edc4220d6015aa829912fb360693fca 2644964 postgresql-client-17-dbgsym_17.11-0+deb13u1_i386.deb 619fdb077dda2a6a1187a92f70d04c275eb3ba4521b91991da7f41223e4b7606 2099664 postgresql-client-17_17.11-0+deb13u1_i386.deb 84a4c9f489afd219a210cb82bb57c1c9b74897fecacc93296b5a3b3c38b80b32 190896 postgresql-plperl-17-dbgsym_17.11-0+deb13u1_i386.deb 0ef779407ddf2137096bf36ec2e30c8da1969118041b44fe4f10649f6cc6ae92 97176 postgresql-plperl-17_17.11-0+deb13u1_i386.deb d690a1f01027001c11c8ac4805d0803d8c5ec3a4b4610e3d833d5d014a30a1bb 188948 postgresql-plpython3-17-dbgsym_17.11-0+deb13u1_i386.deb 59b1d4668061602dba2b3d8312d053d3ce6ee130b65c08fa00ca01c180c7330a 121960 postgresql-plpython3-17_17.11-0+deb13u1_i386.deb b51c90a86b176ec2508ffddff494b188fcd8668691b0fa69a6be2282216eb663 77760 postgresql-pltcl-17-dbgsym_17.11-0+deb13u1_i386.deb d4873cfe0d1611daab27c8c3cd70541750f6a6c56aaf2384c4d27d07d24ca4b5 52132 postgresql-pltcl-17_17.11-0+deb13u1_i386.deb d86051013a270ef3f209c0d33d6207f56836c2c680e6fe874ebf32e481947a9f 53868 postgresql-server-dev-17-dbgsym_17.11-0+deb13u1_i386.deb ce0b26580b3feb8325d28c0d08ef124281d10b13ccf2fd954f5b412e8a7a0c08 1349404 postgresql-server-dev-17_17.11-0+deb13u1_i386.deb Files: ffd9ef1e5ac22aa9f4f7b42d2f1ffff7 14348 debug optional libecpg-compat3-dbgsym_17.11-0+deb13u1_i386.deb ff938e7d533c90584ba3a0a4bdb7fcb7 25268 libs optional libecpg-compat3_17.11-0+deb13u1_i386.deb 20e01d11d8ccfa4942d77f5b18f155d8 276192 debug optional libecpg-dev-dbgsym_17.11-0+deb13u1_i386.deb a866d13cc6f4a09f1be6777c319031cb 319956 libdevel optional libecpg-dev_17.11-0+deb13u1_i386.deb 3ca2fd04cb0fda5092c5b8c8da2a23df 103424 debug optional libecpg6-dbgsym_17.11-0+deb13u1_i386.deb b178d07e3a3128db7c74d2480de680b3 74008 libs optional libecpg6_17.11-0+deb13u1_i386.deb bae2a335d1f8df2bb587c2b1a1471a62 83428 debug optional libpgtypes3-dbgsym_17.11-0+deb13u1_i386.deb 1ebfb3b0b02b533bcfbda91d4380f552 55564 libs optional libpgtypes3_17.11-0+deb13u1_i386.deb e407f3f718aed68ee0975fc9cf1a0142 169264 libdevel optional libpq-dev_17.11-0+deb13u1_i386.deb 03d547b38f6b8751270569e2a73adabe 261968 debug optional libpq5-dbgsym_17.11-0+deb13u1_i386.deb 9598e86b2616a089a03df072a3cd890a 247012 libs optional libpq5_17.11-0+deb13u1_i386.deb a14e32e60447d98fd5307fba1e2e569a 17793336 debug optional postgresql-17-dbgsym_17.11-0+deb13u1_i386.deb 02af799d8e6307100b33a9ae6187e216 17449 database optional postgresql-17_17.11-0+deb13u1_i386-buildd.buildinfo 986abf9e5fefe7f082fc8635be423002 16928564 database optional postgresql-17_17.11-0+deb13u1_i386.deb 7eba3054fd9a9a8a6836caba813f2095 2644964 debug optional postgresql-client-17-dbgsym_17.11-0+deb13u1_i386.deb 977ef2c971cec5b8c42fb41ccccc84b2 2099664 database optional postgresql-client-17_17.11-0+deb13u1_i386.deb 0b828aeaa839463fd121b0897c024139 190896 debug optional postgresql-plperl-17-dbgsym_17.11-0+deb13u1_i386.deb 68c23e436a48ade99a655677eac99be5 97176 database optional postgresql-plperl-17_17.11-0+deb13u1_i386.deb 065f77610d440bdc3e7b2886033b4991 188948 debug optional postgresql-plpython3-17-dbgsym_17.11-0+deb13u1_i386.deb 54f74c1fba7fdafa7fb3db972e6fbe06 121960 database optional postgresql-plpython3-17_17.11-0+deb13u1_i386.deb 181d89f98ec46957be45c6be4590ef28 77760 debug optional postgresql-pltcl-17-dbgsym_17.11-0+deb13u1_i386.deb 5cbef82694f38cbaee024b37919b5ab9 52132 database optional postgresql-pltcl-17_17.11-0+deb13u1_i386.deb 98fd86dc68f749b1595859582de9f195 53868 debug optional postgresql-server-dev-17-dbgsym_17.11-0+deb13u1_i386.deb e4cc945da664f4a4b2c600578f87fc34 1349404 libdevel optional postgresql-server-dev-17_17.11-0+deb13u1_i386.deb -----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEE5ZI1lXv5WjhHIVjsN8Ugyu9dQiQFAmp9lX8ACgkQN8Ugyu9d QiRxCRAAvCqWrTMA+SX01yCzU0PmxwPR4yGJ0RDzXFDfpn3qr27xRvBe2uZY0Bu5 33BPdy3kTTCNZG9+aXqHXYC9AnJaTqyAOtbs/VABPxWbuQiAJ4NEL8tXXUIWzQ9q Opqj6sbCPELhEVP2zuJxbmVwE1ct0d0c1ashT5TusyGm/h/qceZFwA+jAVqPjY6H MLQHVkpqYIJMnDbhtitDzoVUeBMizTCmD7SyBWiKrmX1WX/00W3R9C28GU/CvqbD 3UfW+Z4rejBbssg01Ta6AYy2j9muI3IWX+FLEktn7vh2Ytxub8lFBcGqWFJrdazs qnAojr5Xns/aNKDDFYBYK8XqfK7uL3/7mUCFufqUPlRNbE8WyNqEvv4EtMgbLEpm ypAXB5oxsJWhHKAYjbTi8123rCdlmEtnm5nGK9DuGU7kxcT/NUVz3aTAQRnRczQ/ K5+ohT1Beu6F3ES1aRf9B8UJYt2aDWDRIhrTn6BWWoRxOq3FNZFHPaXdV2bUsIcZ ezSIj7Z77x+Lhs3No1dc700Uxm4MHDVCLFl09TkZyxWSYoKuV4Onm1fiHCu/FFcS 20hT8AQThQ633nGRUOhR1ilqd0cujofAPBOwQjIGXvv/KwATtAfSmzsKUpA43Umx FBTmm53jgNKAfff2ATb//h4T6n+SLpbu8wT3Eu5UBJuH1OnTbIY= =vIyd -----END PGP SIGNATURE-----