-----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: s390x Version: 17.11-0+deb13u1 Distribution: trixie-security Urgency: medium Maintainer: s390x Build Daemon (zandonai) 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: eb9b8ee23f942581167534e80bae067a7ac6122e 16968 libecpg-compat3-dbgsym_17.11-0+deb13u1_s390x.deb bb8cca60c9791224441a2c563c7f3da2030a72d7 24900 libecpg-compat3_17.11-0+deb13u1_s390x.deb 72fc2198a22e50d5f46207551530b111d9cc06e7 234368 libecpg-dev-dbgsym_17.11-0+deb13u1_s390x.deb b4eec4a2b57245d13c2d27d1dbbb06de309a63ff 308600 libecpg-dev_17.11-0+deb13u1_s390x.deb 6a5a14c9f44ed5db28341e543978df732fb7e7f0 115876 libecpg6-dbgsym_17.11-0+deb13u1_s390x.deb f4ab0e645bb44f4cb687e9dbe584337aca8eb1e4 70436 libecpg6_17.11-0+deb13u1_s390x.deb e07186385b6bc4d3fa1d404d78ac3fec44779f6a 92656 libpgtypes3-dbgsym_17.11-0+deb13u1_s390x.deb 82946787c5453e866868b5ca4ac4814938776f6d 55324 libpgtypes3_17.11-0+deb13u1_s390x.deb 1b301904f4cd52be22286ccf8c8dcc93a48853e9 156444 libpq-dev_17.11-0+deb13u1_s390x.deb 5eb82026e52903d16fb9bfc0ded119c0221fac17 300256 libpq5-dbgsym_17.11-0+deb13u1_s390x.deb 5821ee832620670f752c6126a7b8bbe9a3c6af50 232188 libpq5_17.11-0+deb13u1_s390x.deb 819f0bfa6549b6852d02bfe1a44420fc5588843c 19445344 postgresql-17-dbgsym_17.11-0+deb13u1_s390x.deb 94f7652ef6a5a8f5fabc9bf6043a62d8f81ed112 17451 postgresql-17_17.11-0+deb13u1_s390x-buildd.buildinfo 3069354950f07a748d2dd28f98ef2a6ece09a45e 17348172 postgresql-17_17.11-0+deb13u1_s390x.deb d37829e50733274b1cf6a58f641a31fb49d46313 2883828 postgresql-client-17-dbgsym_17.11-0+deb13u1_s390x.deb 4e584a009b3b6601f2f183bbdeff8e5b6d766260 2035920 postgresql-client-17_17.11-0+deb13u1_s390x.deb 2472807247a9b390284261e5168d9e2f0975d59c 198068 postgresql-plperl-17-dbgsym_17.11-0+deb13u1_s390x.deb 95913b2cc03bece000b0de654eca6f086b0c92a7 93404 postgresql-plperl-17_17.11-0+deb13u1_s390x.deb d98cf79957628a96884f4004bd1b1620d5bb3c99 198144 postgresql-plpython3-17-dbgsym_17.11-0+deb13u1_s390x.deb f959746b436b03d9c83f272c0525e32ccdef5aaf 117504 postgresql-plpython3-17_17.11-0+deb13u1_s390x.deb 50fd6341ba1bd9ea22813fe4ed1bbba9cedfd796 83880 postgresql-pltcl-17-dbgsym_17.11-0+deb13u1_s390x.deb eb9e78efd2f0e4f510dbad22ddb7589714fd0833 50152 postgresql-pltcl-17_17.11-0+deb13u1_s390x.deb 48fd39adb1b2d5d4eb009b48b49c5d12106a91f9 55020 postgresql-server-dev-17-dbgsym_17.11-0+deb13u1_s390x.deb cabcf40d19e9f32944d91931f6f51231bbf62a94 1333972 postgresql-server-dev-17_17.11-0+deb13u1_s390x.deb Checksums-Sha256: c19d616edc912fbd04c1ec8ea2743c30a479464b788905fd601e634b2eb1aec6 16968 libecpg-compat3-dbgsym_17.11-0+deb13u1_s390x.deb d98278dcea8a68a68fdb71a40c6b3ddb863de9da9ea767aa1c6e02b4096b0735 24900 libecpg-compat3_17.11-0+deb13u1_s390x.deb acc93e0ead30ae85d1b417030430231c0ce7aaef9a68f696f01ea5863f023c78 234368 libecpg-dev-dbgsym_17.11-0+deb13u1_s390x.deb 36a723c939f7bbf2dfa5b4d344e1bb7575fb9b20a3c40d8483f8f81c6b3cb00f 308600 libecpg-dev_17.11-0+deb13u1_s390x.deb 45a0383ce8ae835a61a06bee6251af35ee25edf6d2b73a51a74ad41ddaa9133e 115876 libecpg6-dbgsym_17.11-0+deb13u1_s390x.deb 5e707611873b0d74ee0ee9aee04d82c3fefea95ef6cc4bf390b9aca80d24ac34 70436 libecpg6_17.11-0+deb13u1_s390x.deb 3eea7490b87c24738c855c441343177ac4e12943c6e0c743074f730092de5309 92656 libpgtypes3-dbgsym_17.11-0+deb13u1_s390x.deb ef81600e31a80dc6cafad4fa9cb2806aed21e85447666281758ce68338e4738b 55324 libpgtypes3_17.11-0+deb13u1_s390x.deb 47b4f14e019d49f0a4fb1153233877baa95535773cd10f5a92606c69972675ef 156444 libpq-dev_17.11-0+deb13u1_s390x.deb 1e9e1915cd59bafb7a72213263bb285c066a954f6d43a599df52718e98455c95 300256 libpq5-dbgsym_17.11-0+deb13u1_s390x.deb 115bb9599e4ac03776fddb320460020c96ace47ef56e06259597326148c67587 232188 libpq5_17.11-0+deb13u1_s390x.deb d94a012919d99c6bcc5b5ad7cccf52beff21c820d09511a2e6eb246cb13f3217 19445344 postgresql-17-dbgsym_17.11-0+deb13u1_s390x.deb c6554f85f249b852767878563496eb822aad3263f7f8c9d73a9d18febe123345 17451 postgresql-17_17.11-0+deb13u1_s390x-buildd.buildinfo c19073ca1b023ced9f2dca6b0152c86b0ce7f29c2b4ade4ee09769d910cdad90 17348172 postgresql-17_17.11-0+deb13u1_s390x.deb ee54910ab0feba434118f3b4120a0cd9c10caa0c0cc887949b183964914e5c5b 2883828 postgresql-client-17-dbgsym_17.11-0+deb13u1_s390x.deb e741a7d5d83625956c2b2930d659fab5fa5ac4bd0e11b348483f9246c7b5f329 2035920 postgresql-client-17_17.11-0+deb13u1_s390x.deb 331ef879320f4e390894f7a07b101d1b834c0f031a602452f938621c449d1c28 198068 postgresql-plperl-17-dbgsym_17.11-0+deb13u1_s390x.deb ce520edc555effa7588e578c0d51d4e306d306958006fcc175fa6dd7fed6c53c 93404 postgresql-plperl-17_17.11-0+deb13u1_s390x.deb 4e4018fb5cf405cea0c9ee9dfc0b85c2e932498170f0ddedf4e8b2684c84e01e 198144 postgresql-plpython3-17-dbgsym_17.11-0+deb13u1_s390x.deb 3379f8d25eb6f8ad920c69e068ac711a940259246e7e520beec2058930f1184a 117504 postgresql-plpython3-17_17.11-0+deb13u1_s390x.deb 3d924b3ce922dba1c3a3624ecf70f5fe8135c45815a09163df715865dd5e8dbb 83880 postgresql-pltcl-17-dbgsym_17.11-0+deb13u1_s390x.deb d71892c79350579dc34f7c29088b542a97d60672a524919e3e7ef080a49429ed 50152 postgresql-pltcl-17_17.11-0+deb13u1_s390x.deb 7dd3148946babededa2ae0ddb3897e84767a0f3859c6288f9935725754c995dd 55020 postgresql-server-dev-17-dbgsym_17.11-0+deb13u1_s390x.deb d18129214370153f98ba01dce4e001b8a20f9b285f8e3a50d40ac1ec8db712d2 1333972 postgresql-server-dev-17_17.11-0+deb13u1_s390x.deb Files: 10e75f6b595c88b8ebd9df6b64202817 16968 debug optional libecpg-compat3-dbgsym_17.11-0+deb13u1_s390x.deb fc0928d8563744a36a316ff638f93a3f 24900 libs optional libecpg-compat3_17.11-0+deb13u1_s390x.deb d65b12eb89e8ca7ec5a700838e37afde 234368 debug optional libecpg-dev-dbgsym_17.11-0+deb13u1_s390x.deb dc90d41ff71554f83013953611e07aa4 308600 libdevel optional libecpg-dev_17.11-0+deb13u1_s390x.deb ccbce5e959aa58b3539a461f59e0ad1c 115876 debug optional libecpg6-dbgsym_17.11-0+deb13u1_s390x.deb e45dd7f1df1ea05a4e930c1da66a2985 70436 libs optional libecpg6_17.11-0+deb13u1_s390x.deb 47132ac0822191212381287ab7a26dcc 92656 debug optional libpgtypes3-dbgsym_17.11-0+deb13u1_s390x.deb 00e7fde06304b39c57120f6b094c18eb 55324 libs optional libpgtypes3_17.11-0+deb13u1_s390x.deb 3ed01e39755b89c7f977f73ac8c841cb 156444 libdevel optional libpq-dev_17.11-0+deb13u1_s390x.deb fc354052f73659c5c97109436e75e361 300256 debug optional libpq5-dbgsym_17.11-0+deb13u1_s390x.deb 0f742b64e405fd5bf70589563553d7de 232188 libs optional libpq5_17.11-0+deb13u1_s390x.deb 33878d721eace40068c46918d3bd38b1 19445344 debug optional postgresql-17-dbgsym_17.11-0+deb13u1_s390x.deb 1c9e9b83ae75926373b64157eef42475 17451 database optional postgresql-17_17.11-0+deb13u1_s390x-buildd.buildinfo dccb552b0f2598cc77ae0a40ae141263 17348172 database optional postgresql-17_17.11-0+deb13u1_s390x.deb f4869bc65ceb9f94a24df9876d9ebdda 2883828 debug optional postgresql-client-17-dbgsym_17.11-0+deb13u1_s390x.deb 5333e3345c1b50eb514a8ca44e71ad09 2035920 database optional postgresql-client-17_17.11-0+deb13u1_s390x.deb 59be7bea751005e2110b6270e1efe649 198068 debug optional postgresql-plperl-17-dbgsym_17.11-0+deb13u1_s390x.deb ecccffc13e9f9223a71c90df147552c4 93404 database optional postgresql-plperl-17_17.11-0+deb13u1_s390x.deb 009f8e08858630225f6f9cd26792891b 198144 debug optional postgresql-plpython3-17-dbgsym_17.11-0+deb13u1_s390x.deb 6cb5d1e66320838ce82891eb2ff4b5d1 117504 database optional postgresql-plpython3-17_17.11-0+deb13u1_s390x.deb 7f921c1b62e8c03d663480af5211e9fe 83880 debug optional postgresql-pltcl-17-dbgsym_17.11-0+deb13u1_s390x.deb 86b9dd92f73c848c0b5223ee915e0807 50152 database optional postgresql-pltcl-17_17.11-0+deb13u1_s390x.deb d2a6560e4593c1d6c803ec5bd5c542e2 55020 debug optional postgresql-server-dev-17-dbgsym_17.11-0+deb13u1_s390x.deb a2e0cf18d744d16cfbdee9894331cd31 1333972 libdevel optional postgresql-server-dev-17_17.11-0+deb13u1_s390x.deb -----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEENly2ANlpa4eeqnluvVOPI7pYNpgFAmp9jgQACgkQvVOPI7pY Nph8QBAAkTFT7mthoX8UYzm3vXxX5IYQOD1I3Wj2NYoOmudPeoijDOnyohRiy3HX 2f7YLeGgJ//PfQW1KAlMyFECLbGRPaURec6/8MX6odc16OFpLz50XEyFimvT9rB3 q52z+xZYtzS8hEAIlXV89wTncnZBYKAQ7wHpCGkTrVERqbLG+cIg085sxkGWvfcT LAo97Ao9u5H4bejW5xUn4q61YOLWJnR1bVAgmuxICjKzn0JOS8BynaKiSz6cD87o avuRgYv57/8U0GLtlYzhW3R4Ta7v6dozMVI3sXVfQVQB2p47sa960wT3Vv3zNM8r 8trOOqXzdXCk7Ai790osFuyxCGkeeqdQI2Yn+CdPztsamA2JFZ/7EesiLZUcLAws kFFjRbLM639y2eMlQyY68kDzy7Q/X1Oa/uoF6awPvwbBHsbOfCbLrLhYh/7yezed v3fg2RJ47hduZqpuV+RwzXk9HQE7+pAqhyj3Ctq9SDLJnUnJq6PJQmzd50Iux3/z qYqWyCmMpt0HrkCLdLKLDWzuwSuP4Pq8+rvRMmSNgBH0Jov8U6p7N7sAqOpmUxsf V701PAS0acmrFn387l/pvtCGeOGr+1xAYubPmWO2oY89+fGXag3GsoIU1GMshXzH FueepVcc9sohFy6X6Pe5uoh6R1849/lkFEgzRkx03MLGYpa5Zt8= =lYLZ -----END PGP SIGNATURE-----