-----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: arm64 Version: 17.11-0+deb13u1 Distribution: trixie-security Urgency: medium Maintainer: arm64 Build Daemon (arm-conova-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: 10c273702d13a75d4ddf056e730cf94a72760bbb 16984 libecpg-compat3-dbgsym_17.11-0+deb13u1_arm64.deb 3b076ad53022ed43231c51c57b956555caf79c85 24708 libecpg-compat3_17.11-0+deb13u1_arm64.deb a87e35a4ba3da4911804819a332c4da0ceef14b5 271216 libecpg-dev-dbgsym_17.11-0+deb13u1_arm64.deb 83bf77ee6e59305ec1b36ce3503e2b65a7eb88c1 293484 libecpg-dev_17.11-0+deb13u1_arm64.deb bc5a4b299e634ee93c8a4b073150cba992b76baa 115504 libecpg6-dbgsym_17.11-0+deb13u1_arm64.deb c974621ca54d3289bf780d2cc79f68e83b8f4abf 67536 libecpg6_17.11-0+deb13u1_arm64.deb 8581defc40ed018772f0844ae770ef277765aaf9 89348 libpgtypes3-dbgsym_17.11-0+deb13u1_arm64.deb 881c418bbd7a73c7c3e023045f1e383f55312c95 51116 libpgtypes3_17.11-0+deb13u1_arm64.deb 6f0ef080ff38d64767335dd57c85b6a05ec999bc 156400 libpq-dev_17.11-0+deb13u1_arm64.deb 6b8201a79c8c8e8f5afb00ff95af390136f21364 298788 libpq5-dbgsym_17.11-0+deb13u1_arm64.deb 7a1eee1da7feb9c7ce5a35605615d02f0b9a3825 229628 libpq5_17.11-0+deb13u1_arm64.deb a6b15c242dd049ae229799e7e1c518a709f998df 19662244 postgresql-17-dbgsym_17.11-0+deb13u1_arm64.deb 5185a15ab687b0f7fa60834ae4cfb48817c1489f 17576 postgresql-17_17.11-0+deb13u1_arm64-buildd.buildinfo acc0c42b7cbec9631297db1fd89861a64cea2d73 16181424 postgresql-17_17.11-0+deb13u1_arm64.deb eb6568fbb708ff6778d83cbf04ae309e63bd1a51 3104364 postgresql-client-17-dbgsym_17.11-0+deb13u1_arm64.deb 0d63717e34d0e9abcdba6453b6c792ec50bcc15e 2018616 postgresql-client-17_17.11-0+deb13u1_arm64.deb 4d7b59106b9f788ed7bb3bc7fccfc5b4fc21de68 198572 postgresql-plperl-17-dbgsym_17.11-0+deb13u1_arm64.deb 8d828cc9660bf44124ebc2796e20f135776655e4 90436 postgresql-plperl-17_17.11-0+deb13u1_arm64.deb 24772b9fc135b449f42faff05859c4da5ac88a5d 202280 postgresql-plpython3-17-dbgsym_17.11-0+deb13u1_arm64.deb 71fe46a4e3621f2e8c96a85e6367a218837a383e 115844 postgresql-plpython3-17_17.11-0+deb13u1_arm64.deb e0dc26f779ee5be97bfbf63a1f69247d2ef0b6db 84232 postgresql-pltcl-17-dbgsym_17.11-0+deb13u1_arm64.deb c0c6b62ee105a8be202a16e3c50a44807e1dc741 49168 postgresql-pltcl-17_17.11-0+deb13u1_arm64.deb f4cf5cac19f8b1a43decabcf1d13a2e67cceaccd 56044 postgresql-server-dev-17-dbgsym_17.11-0+deb13u1_arm64.deb faae61a71e36a0b2b966e071960d93bbf07965c7 1323296 postgresql-server-dev-17_17.11-0+deb13u1_arm64.deb Checksums-Sha256: 30e3571f21eee95ab278a43b9c4ab46c5b764c84ea9f144875e6dc3bb8392cb9 16984 libecpg-compat3-dbgsym_17.11-0+deb13u1_arm64.deb 1d6231bd3896c91b70b99561a04f2d6deb71413621e0833561d19b149d9e94fb 24708 libecpg-compat3_17.11-0+deb13u1_arm64.deb 89dd61750d57b595a0734446f9354243df8671557091b9a3e14b45274124b22f 271216 libecpg-dev-dbgsym_17.11-0+deb13u1_arm64.deb 8c2a6261ea208e53b68579626c5b9a3089edc710b977709bf65ad4a22c46e83b 293484 libecpg-dev_17.11-0+deb13u1_arm64.deb 0bfec9576fa2d6eeafefc9e8f8685b7c468bbd2ae817450e55d9494d0808f121 115504 libecpg6-dbgsym_17.11-0+deb13u1_arm64.deb bf7d5eca8185193c7e9c471c9746279e401fe54d5b91ea601c7319b63142a03c 67536 libecpg6_17.11-0+deb13u1_arm64.deb ee763f60295c93b920f7687bc15b7d34d7fd51ffc4410bfc6541ab8a65cb1455 89348 libpgtypes3-dbgsym_17.11-0+deb13u1_arm64.deb 9a79d694fd31522d7ff470a29ff66adc5f021b65c458eeccbbf8c0354a7aea7d 51116 libpgtypes3_17.11-0+deb13u1_arm64.deb 3231fe52f6cfb99261e63a7b2c465982b0a44c5b2e9a2c123d3f3f6fa9198a69 156400 libpq-dev_17.11-0+deb13u1_arm64.deb ee2cae629fc6ca581b31cbbee5041ee2c61df4f688628ba1ff92f1cb3f31c9b2 298788 libpq5-dbgsym_17.11-0+deb13u1_arm64.deb 1eb5e3126a6978446a4f02f53ce74c7ce4b7f13e48ec45adddcce1881d233458 229628 libpq5_17.11-0+deb13u1_arm64.deb ededa9acb13b925d97892600926afd5f5d9164ed5a7aceca0a4f3b2a5442faa0 19662244 postgresql-17-dbgsym_17.11-0+deb13u1_arm64.deb 60c7c2a7fea6e96110d6ffa0ec377ceb5bceefbcaa9906d2bc7aaee7a1ea1d77 17576 postgresql-17_17.11-0+deb13u1_arm64-buildd.buildinfo 7565afa5ba192ed8dc5a8e25d6392c45f2ff22d5acbb4eeea80906196bce82fe 16181424 postgresql-17_17.11-0+deb13u1_arm64.deb d49141d71f06781e7185f7a6acfcb9af3d0fa2d56271f02a463727ddec01b2cd 3104364 postgresql-client-17-dbgsym_17.11-0+deb13u1_arm64.deb 681864141a87da77cb1d1ff26dc4d53c6277974eea01ce57fd15ea57593543b7 2018616 postgresql-client-17_17.11-0+deb13u1_arm64.deb 05bc342787d1b824fb7cc8e4656c86dae7d6d6afa225c4ff19a47bf3a7d759ec 198572 postgresql-plperl-17-dbgsym_17.11-0+deb13u1_arm64.deb 68692eda3dbbf418f0d6f288c2e54907951044a9030511786c461b87eca6f3bc 90436 postgresql-plperl-17_17.11-0+deb13u1_arm64.deb c9ee1455c2a89502744a2c03ac06625cbfbb31bce548a20ebca85b82c50c4fcc 202280 postgresql-plpython3-17-dbgsym_17.11-0+deb13u1_arm64.deb 1d8942969d529724ef8d4b6de150c7713a423da12c7a11d2255ad750c02f8ec9 115844 postgresql-plpython3-17_17.11-0+deb13u1_arm64.deb 062ad8c7b6d99b8c4974a251436e22ff35c9984a46bcd4ee91af82d19ebf688b 84232 postgresql-pltcl-17-dbgsym_17.11-0+deb13u1_arm64.deb 2606f70f7456422e17b2ac326207fe74f415399e228b04f08d012ebcdfbfd2b2 49168 postgresql-pltcl-17_17.11-0+deb13u1_arm64.deb 0e1f12e1496e4ac585974d7abb6d6c3d8c90c527c4b8dfd6265c8da9e496a5fa 56044 postgresql-server-dev-17-dbgsym_17.11-0+deb13u1_arm64.deb efc2a276c9307972c551a56ac54572bf70be3cb1a19b170953432b46d439b7dc 1323296 postgresql-server-dev-17_17.11-0+deb13u1_arm64.deb Files: 62a3c4072bf0507ce95c429e0aa34acf 16984 debug optional libecpg-compat3-dbgsym_17.11-0+deb13u1_arm64.deb cd0fbe013cc0e99075dbcab416562668 24708 libs optional libecpg-compat3_17.11-0+deb13u1_arm64.deb 4ec9e2f190954c5e67a2897c70b903bc 271216 debug optional libecpg-dev-dbgsym_17.11-0+deb13u1_arm64.deb 0728fa6919bfdb0e4771168c67acff09 293484 libdevel optional libecpg-dev_17.11-0+deb13u1_arm64.deb c1cb11844bf7ef224eddc2f9354da4fa 115504 debug optional libecpg6-dbgsym_17.11-0+deb13u1_arm64.deb 4c689c004453ff6ae360da68139778e1 67536 libs optional libecpg6_17.11-0+deb13u1_arm64.deb d719735f949e504f2c91855b7e2e20d9 89348 debug optional libpgtypes3-dbgsym_17.11-0+deb13u1_arm64.deb 429269137bb61a25318aa6841e27f44c 51116 libs optional libpgtypes3_17.11-0+deb13u1_arm64.deb 37b5081a3ff0f334954067f8b4c49e4c 156400 libdevel optional libpq-dev_17.11-0+deb13u1_arm64.deb 59c3f4f9b34558218b8e62f470b2f4d4 298788 debug optional libpq5-dbgsym_17.11-0+deb13u1_arm64.deb f744afc74f9f2c4c31c1622b2ab00252 229628 libs optional libpq5_17.11-0+deb13u1_arm64.deb d8551b3aa6db06b72385a2d6214bd806 19662244 debug optional postgresql-17-dbgsym_17.11-0+deb13u1_arm64.deb 75d814479e3735bcf1e8642a8d298618 17576 database optional postgresql-17_17.11-0+deb13u1_arm64-buildd.buildinfo 03210070b2bc1b1b6c84e703e8882bf4 16181424 database optional postgresql-17_17.11-0+deb13u1_arm64.deb 65fbd8eb4fede5fc393da1b8ffc33d99 3104364 debug optional postgresql-client-17-dbgsym_17.11-0+deb13u1_arm64.deb add718286681c9b8055b7bdf2b00a376 2018616 database optional postgresql-client-17_17.11-0+deb13u1_arm64.deb 285cc1d68c28be98d9ed1ec0d16e9f08 198572 debug optional postgresql-plperl-17-dbgsym_17.11-0+deb13u1_arm64.deb ca91580029d1503ff2e6a2b4ebef55a7 90436 database optional postgresql-plperl-17_17.11-0+deb13u1_arm64.deb f8b4281cd637381b7a438c351f338ecd 202280 debug optional postgresql-plpython3-17-dbgsym_17.11-0+deb13u1_arm64.deb 7e16602d6a86382825f5ab14bfa99da5 115844 database optional postgresql-plpython3-17_17.11-0+deb13u1_arm64.deb dec682017eb8276e2c4b29ff41b471e3 84232 debug optional postgresql-pltcl-17-dbgsym_17.11-0+deb13u1_arm64.deb eb4c8c6824a7196798faae970c2ecbb7 49168 database optional postgresql-pltcl-17_17.11-0+deb13u1_arm64.deb d4f979fc5e53f0b197c4327d9d65f188 56044 debug optional postgresql-server-dev-17-dbgsym_17.11-0+deb13u1_arm64.deb bca431507d6e4f15dfff94c593dcf890 1323296 libdevel optional postgresql-server-dev-17_17.11-0+deb13u1_arm64.deb -----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEElFiH1oZRZh1t4FSiXVp1sEH/1mIFAmp9kVcACgkQXVp1sEH/ 1mKArQ/8CsI+WA1d87JXR8t8dMoCcPGqfm7bUHs80aFdqHif8sdJqXD5Xy49FPQA oHG3v1jHcxb3yuL9rEttHGcBeLopw5eVi7F3KgPFySdSkQfG5O5n0ITAy5S0jCha +hkFlLFeaxhi1zikCw/hwv2q8XMCWo73N738vQtzzhvEiJuBRLJjhxehs+e48fZz 5ngeg/VYWYhNNqNNKqjY7X8oHqYsTeir+FgIOqfye5IrG+HL5dSk1t2h5JM657z9 W5R9nbNurTryRi3XZZuzxEvd0LklBfe26pp5gDh0wJqE6mRNakpVX+l8OhE0KpT1 hq8g882C90KcLX9oa+xcgrJTVgou4xG7kskO8O8AbCaNbFXZ36/jzcQGeudGzz3U vvIgPqEb9HRQ8v5RFLRNX6ils7Zr63gidZGY26taEbF+wWmKiJ0882Uo14XMwrk2 RvS81g5U9HGPYsR0EM2fJe9cw65SwCsy2Wy1O4BtAif0kvO0p/N3DnIL06dSkswY eUwp9muqENlOJEgqFZ3ZapUuXMLFeswOXwDjT+Se3anq/YG+y8JFcuVRkA7AJr2n s9T7uS8sx0WyBtX9qxxWE5Lp9Bq+EkiB0B6gYGgDw8816wSPItnpeqY971izgX1g sNt5fXEVObsXkBStxVJyy9LQpY6A6ZTfvXsAn0e/7Em6gtZuYNs= =HCja -----END PGP SIGNATURE-----