-----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: ppc64el Version: 17.11-0+deb13u1 Distribution: trixie-security Urgency: medium Maintainer: ppc64el Build Daemon (ppc64el-conova-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: 01bf6d24572ba49e89c79817726dcfdcff268d41 17792 libecpg-compat3-dbgsym_17.11-0+deb13u1_ppc64el.deb 7c97fa069da819699005c5e67fbf411233519339 25936 libecpg-compat3_17.11-0+deb13u1_ppc64el.deb 2302188da00c2725b7f230b4824210ec57bc6770 240812 libecpg-dev-dbgsym_17.11-0+deb13u1_ppc64el.deb 6522d595f93912922cce6140fad9aa04ae0bbde3 314788 libecpg-dev_17.11-0+deb13u1_ppc64el.deb 66d0f973d1b191de5ce607ab76bfb4f01cc6c600 116760 libecpg6-dbgsym_17.11-0+deb13u1_ppc64el.deb 0187e45a8983e34bddbfaca4e5a4a26ea661a863 73320 libecpg6_17.11-0+deb13u1_ppc64el.deb c160811ce990f560baf73f2eb8e4d9792c17fe54 94564 libpgtypes3-dbgsym_17.11-0+deb13u1_ppc64el.deb 495eb60186d085fa416c00779fd41f8b318967e8 56780 libpgtypes3_17.11-0+deb13u1_ppc64el.deb d8d2220794dce9f35880b68bc5fd3fae654cb6a5 172860 libpq-dev_17.11-0+deb13u1_ppc64el.deb 8a10c04822f41674f1db081571dbd37a38f14ea4 311912 libpq5-dbgsym_17.11-0+deb13u1_ppc64el.deb 18bb00cad92f56cf4ae6bb3d161a78bf00f72648 249396 libpq5_17.11-0+deb13u1_ppc64el.deb 5c5e93608b4296aac72c6218b3795e7bea30a5b1 19526072 postgresql-17-dbgsym_17.11-0+deb13u1_ppc64el.deb 5578442bc66d349436c3e4a957acbcdbe3b63bd5 17714 postgresql-17_17.11-0+deb13u1_ppc64el-buildd.buildinfo ee3423775cf03c68d684055576c1f43debf0c019 16908784 postgresql-17_17.11-0+deb13u1_ppc64el.deb 1b908bfb74cacb50fb14e68003feda04e4a1e9eb 2959712 postgresql-client-17-dbgsym_17.11-0+deb13u1_ppc64el.deb 7058cc168b1fa6130ae3ed4c27ed3821d5a651f0 2096716 postgresql-client-17_17.11-0+deb13u1_ppc64el.deb afab28de8db92736bb6d1688184e74df5bf5c718 202680 postgresql-plperl-17-dbgsym_17.11-0+deb13u1_ppc64el.deb 3a71934d419f9973326e0dd13c292dce6d9f8f38 95040 postgresql-plperl-17_17.11-0+deb13u1_ppc64el.deb 7fbb6848b749020bbac8f72078c5ae5f199538ff 201616 postgresql-plpython3-17-dbgsym_17.11-0+deb13u1_ppc64el.deb 3d73b704ac3cfbdf89e29040600cdbbb4558d9b5 119320 postgresql-plpython3-17_17.11-0+deb13u1_ppc64el.deb f544119fb77c094c93624a85885302f9c35ba488 85056 postgresql-pltcl-17-dbgsym_17.11-0+deb13u1_ppc64el.deb 20140359e19273e68ddf30d3ac9d16f9e8e68892 50800 postgresql-pltcl-17_17.11-0+deb13u1_ppc64el.deb 505c356b185ac85cccce0c40762e645b45e89c05 55872 postgresql-server-dev-17-dbgsym_17.11-0+deb13u1_ppc64el.deb 59b7a041ac59ad9d90efdd58f9d09a7a54d78be3 1348352 postgresql-server-dev-17_17.11-0+deb13u1_ppc64el.deb Checksums-Sha256: 0885f7751a8085fc7d2b479bc70b17dcc50850eed3c004f878def1508e926a88 17792 libecpg-compat3-dbgsym_17.11-0+deb13u1_ppc64el.deb 5b6ad800d939218d3e01be698fe8f687d0e76cd40612ec89230616b8207ac1b9 25936 libecpg-compat3_17.11-0+deb13u1_ppc64el.deb ff81bfe78fcd941f4ac4d823a73bbbe5e025ccb63f3a062a0a1f5bb38857f88f 240812 libecpg-dev-dbgsym_17.11-0+deb13u1_ppc64el.deb 2ea6059bc67f314c3a416ec5f2f08f49b4246d891683304b1411b044848c80c6 314788 libecpg-dev_17.11-0+deb13u1_ppc64el.deb 302f94e1acc5a5c5e02db8f3c827197f0bd2138dd3b5e890c530829d00ba450c 116760 libecpg6-dbgsym_17.11-0+deb13u1_ppc64el.deb 6a5e9695f77a493cce69c5f93fce02c309bfdc3e7405c4ef9e6d91eb1dc3ff4f 73320 libecpg6_17.11-0+deb13u1_ppc64el.deb 46e37ef7c489d0f566d57d5e6b6e68f0dcfeeb2bf9e4a03fcbe25197961375e2 94564 libpgtypes3-dbgsym_17.11-0+deb13u1_ppc64el.deb d1985aac1068ee5e3b8d14474cc7762ddca9a76f3b1cf2436c7648b90cd8a53f 56780 libpgtypes3_17.11-0+deb13u1_ppc64el.deb 2c82efb62e36a31005f87d8471d70b7e3da87cb6ea76d35ef7aa6d01e31e15bb 172860 libpq-dev_17.11-0+deb13u1_ppc64el.deb ecd69283cb0a74d17b91d57e021c0648ab00599a8b9311e9e15454a743ff2386 311912 libpq5-dbgsym_17.11-0+deb13u1_ppc64el.deb 6898256210b25fbbfc703e5af7e10d0f7bdf9e55a57f208570edfe4fe9275422 249396 libpq5_17.11-0+deb13u1_ppc64el.deb 8f3a1a8d2c20ecdaec3d1d9e93b9197511a16bf9b8ea1ecce9a0929245a8fc95 19526072 postgresql-17-dbgsym_17.11-0+deb13u1_ppc64el.deb 174cef81a968cb4f945fad53f7db7cf190c952752b7dc9f48ee2ae2051a109c0 17714 postgresql-17_17.11-0+deb13u1_ppc64el-buildd.buildinfo 4406c475f9c4f65ee5153534b3ca5458aba718375f50d80f45474ccf07359fa4 16908784 postgresql-17_17.11-0+deb13u1_ppc64el.deb 4c89fdc47f72267263adde7300ed39192c6017a5d1c2015260ff3ce5d3b044d2 2959712 postgresql-client-17-dbgsym_17.11-0+deb13u1_ppc64el.deb 2f44b8fa8f31cf92e8c9781268208d1de8c6e19d132d5daaaf5112cded0a0931 2096716 postgresql-client-17_17.11-0+deb13u1_ppc64el.deb 4401ad8f36ca68543a8b1120ba2326b328880fcf026d673e836316e4f6d3fa35 202680 postgresql-plperl-17-dbgsym_17.11-0+deb13u1_ppc64el.deb 59ab9ca9c853404a6139b5015f90063e5c9ad663a73a9d67fe9bc9cb42c97835 95040 postgresql-plperl-17_17.11-0+deb13u1_ppc64el.deb 41cdde88cdfc3c3640dbf524b07b07a89b508afd3ff3ad9e040ed584da820f68 201616 postgresql-plpython3-17-dbgsym_17.11-0+deb13u1_ppc64el.deb b7e9acdec29e489687100cd1ad2857f3a33045c76e26b7d7a28aab63d64de986 119320 postgresql-plpython3-17_17.11-0+deb13u1_ppc64el.deb fc2214862a702a1017d9bc74a68537631cfc0d3f71d3f318eecf0a02997aa772 85056 postgresql-pltcl-17-dbgsym_17.11-0+deb13u1_ppc64el.deb e4f8201104f47bf11a98b7e41d9dd9706d8db97488ded5b7cc273cebf2b614b6 50800 postgresql-pltcl-17_17.11-0+deb13u1_ppc64el.deb bbe61ced033c683a1859c7c0e624605605006c23b9fb307934969edfc1797aec 55872 postgresql-server-dev-17-dbgsym_17.11-0+deb13u1_ppc64el.deb 802e9aa1a7969836747680faea155f3edce53d53b5bfed24cbe7440325294ac1 1348352 postgresql-server-dev-17_17.11-0+deb13u1_ppc64el.deb Files: 526894198d42cd92bb375448df60c969 17792 debug optional libecpg-compat3-dbgsym_17.11-0+deb13u1_ppc64el.deb 8ffbb414d47a7b6495bd7c3f882d849c 25936 libs optional libecpg-compat3_17.11-0+deb13u1_ppc64el.deb 9f09ca41a4017ab16b24ff2f071daa83 240812 debug optional libecpg-dev-dbgsym_17.11-0+deb13u1_ppc64el.deb 804db12e5ab3d831063a098b80f61ffb 314788 libdevel optional libecpg-dev_17.11-0+deb13u1_ppc64el.deb 9351ee0ae1bba1957bdde94844d8afbe 116760 debug optional libecpg6-dbgsym_17.11-0+deb13u1_ppc64el.deb 4b92f04c760a33ba88e4f8e4894abc19 73320 libs optional libecpg6_17.11-0+deb13u1_ppc64el.deb 82c5306b86389d0bde959880f11cb795 94564 debug optional libpgtypes3-dbgsym_17.11-0+deb13u1_ppc64el.deb f74a82d155575ab9f47ab95abe768f0f 56780 libs optional libpgtypes3_17.11-0+deb13u1_ppc64el.deb 52f8fa7bd58540e0ad6e2fb2d5ae3a14 172860 libdevel optional libpq-dev_17.11-0+deb13u1_ppc64el.deb 02f2725e6c926a69211fd9d4d36d385c 311912 debug optional libpq5-dbgsym_17.11-0+deb13u1_ppc64el.deb 4e14d7946dff48a4948a000722cc8384 249396 libs optional libpq5_17.11-0+deb13u1_ppc64el.deb f649f951262030db771d9b5e6a147537 19526072 debug optional postgresql-17-dbgsym_17.11-0+deb13u1_ppc64el.deb 63ee8864c020257c892259d55bb5d866 17714 database optional postgresql-17_17.11-0+deb13u1_ppc64el-buildd.buildinfo 8cd4121006cf7e2891095df393337848 16908784 database optional postgresql-17_17.11-0+deb13u1_ppc64el.deb d15cd0c2cb69270c879600e555011e24 2959712 debug optional postgresql-client-17-dbgsym_17.11-0+deb13u1_ppc64el.deb 8fed0ab83c49007162d98641909f87df 2096716 database optional postgresql-client-17_17.11-0+deb13u1_ppc64el.deb c12f58abc2c75558a8f7474b9238bec8 202680 debug optional postgresql-plperl-17-dbgsym_17.11-0+deb13u1_ppc64el.deb 808349f82deb43d5f879691e4c819efc 95040 database optional postgresql-plperl-17_17.11-0+deb13u1_ppc64el.deb 831f7f38fb77ada061217e41b6f625c0 201616 debug optional postgresql-plpython3-17-dbgsym_17.11-0+deb13u1_ppc64el.deb d900faa68d95f336f569e1e0bfa1d137 119320 database optional postgresql-plpython3-17_17.11-0+deb13u1_ppc64el.deb 52339c268d8768e111ed23060dd56ed1 85056 debug optional postgresql-pltcl-17-dbgsym_17.11-0+deb13u1_ppc64el.deb aa3f4fbb70952c9f0a6269642741572b 50800 database optional postgresql-pltcl-17_17.11-0+deb13u1_ppc64el.deb fe96df3f8d638f354cd2330223f9966b 55872 debug optional postgresql-server-dev-17-dbgsym_17.11-0+deb13u1_ppc64el.deb a6e4f25b6efdcaa6b13ea227c7ed90f2 1348352 libdevel optional postgresql-server-dev-17_17.11-0+deb13u1_ppc64el.deb -----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEEDoRc43uRWMOoIqIgDNLUPhbmg7MFAmp9kcsACgkQDNLUPhbm g7PEpg//T5jkTK0S7Im+/FbxQcti6MwCOvBYSlP2SOTmMtnE2mJRpNHTyFru/9Yr xIWB9IxEH79BfpV09kwOD08UiFTZKCH7Rk4Ud10KhZOcIlSXMl3tPpEnn2+ZNOb5 RIOmf5M5PYIbn5VXfljQ5LEC9cx/wUGBBrxSevFshjofsYBzHSibe3UWbXCSRbEc JkLsi/q4MILgvQY71MOUlJo9MpSsVEa6xPjoPv1CDCsTgSgy36Hig/WIQUAojxhl aA47u8ljMOgXfx8W0Jr25+DWao5pjaE3JlXEBspfKYTrASfzk40rpa4VPsLKj/iM m6PSbsRjB4DYEVFaQ/3Pgs8E4ekzUAu+CXeuhmXhzvJi6O5u9aYlFIghzc4+tm3B vJbQBSBP6ChZ46CMpr+ab/dIZ6Autias/V7VrJtv3HgikA5WCYNvhHA3vd7qy2JT P2xJKw1mIC5GAjrqfpuLmEZk2zSSv4+CrKDVpe2Koxko/Xh1Ely50PCvvS2aSnR/ ijbZ3W97+41Z7BtxPrb5BCV5OJaCw9GtQ6Sx9vOC666ESwVGOBIRITS9YU3NWdyG wicnyH7SKcJB0zv11icfEO4SnJWsIX6V6hCClkS/ygs2AREzs+MhYvWGhCl9ogSe sSzOP2Ppcp+q98ztcPcIzcgHgzdc4C/xQF3hwWhQ4cqXQ69QMKA= =9yEi -----END PGP SIGNATURE-----