-----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: riscv64 Version: 17.11-0+deb13u1 Distribution: trixie-security Urgency: medium Maintainer: riscv64 Build Daemon (rv-manda-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: c4406bffc6582b23d978c0cec93a1650275adde3 16740 libecpg-compat3-dbgsym_17.11-0+deb13u1_riscv64.deb a2274073503056999255b1a283ae8880cb6f7232 24896 libecpg-compat3_17.11-0+deb13u1_riscv64.deb 4f9572c4fc02f8bdb634d864284f1a74dd8a7997 250528 libecpg-dev-dbgsym_17.11-0+deb13u1_riscv64.deb c6c2896937cf366f6966b3e2007904ad25576be6 392816 libecpg-dev_17.11-0+deb13u1_riscv64.deb 554a21efcc7a57e3ab1ffaacf4e84cbe07ea8fde 107516 libecpg6-dbgsym_17.11-0+deb13u1_riscv64.deb 83e1fe2e6c950ff35952e7f78a9297f53ba12193 68616 libecpg6_17.11-0+deb13u1_riscv64.deb 80699d8be5874614f8a45efdeb8f1ae74293bbdf 86228 libpgtypes3-dbgsym_17.11-0+deb13u1_riscv64.deb 8ccb08cbc0f33427a0a41b0f0700f23db7459df5 54420 libpgtypes3_17.11-0+deb13u1_riscv64.deb 26cdd423815ac71e6d0f6791a7b34c8050950428 273676 libpq-dev_17.11-0+deb13u1_riscv64.deb e410af9cc88abed27b1755625c4f6dcb251a0c45 287416 libpq5-dbgsym_17.11-0+deb13u1_riscv64.deb ff4f0aa3fd527d3e4282d8f0890c299e53242ef6 236748 libpq5_17.11-0+deb13u1_riscv64.deb 0f1cb40f44619cbdf29398a9ef86866df229bf3b 17393376 postgresql-17-dbgsym_17.11-0+deb13u1_riscv64.deb 89e6dc0aa359de4ea628fcbfe720801736ae21f0 16844 postgresql-17_17.11-0+deb13u1_riscv64-buildd.buildinfo f5011e715d9f34f78b77bbc11348cd5d634b48fa 6986916 postgresql-17_17.11-0+deb13u1_riscv64.deb 4633f1d97a6a5ee29b7768d9dcb97aeb4a8635ea 2919268 postgresql-client-17-dbgsym_17.11-0+deb13u1_riscv64.deb c2379d28b4eee7b7068c284e8bfd8726c5d8758f 2054640 postgresql-client-17_17.11-0+deb13u1_riscv64.deb f4db140d487b9d8306a083ae264756381aa4640b 193884 postgresql-plperl-17-dbgsym_17.11-0+deb13u1_riscv64.deb b6ca8592ba34e3c74be2d8145bcc652e300dd26f 77220 postgresql-plperl-17_17.11-0+deb13u1_riscv64.deb 12bfb4449e448873de4b92c256bb34f03f92d5e1 197540 postgresql-plpython3-17-dbgsym_17.11-0+deb13u1_riscv64.deb 7861c7d1b6ba80ab88e92dc6ef88f60e06227d66 98032 postgresql-plpython3-17_17.11-0+deb13u1_riscv64.deb 62b7aa09cf42a9008a151144bac34a662050c11a 83192 postgresql-pltcl-17-dbgsym_17.11-0+deb13u1_riscv64.deb 77fcef4f3ca1071d516a83b82ad988fdacd35203 49412 postgresql-pltcl-17_17.11-0+deb13u1_riscv64.deb 0785e218fa342318da8c9eae01cf60cf53890bd2 53748 postgresql-server-dev-17-dbgsym_17.11-0+deb13u1_riscv64.deb 479cef506b6175c390f99b981d27a68847466e39 1544212 postgresql-server-dev-17_17.11-0+deb13u1_riscv64.deb Checksums-Sha256: a42643d1fb10fd14be8efe3e4aff806447a90774f423ab8f01c3f0da94ecc777 16740 libecpg-compat3-dbgsym_17.11-0+deb13u1_riscv64.deb c973d92e071efd2e15ac57b4623d7105342823c480bf86a9744e7633609a1afc 24896 libecpg-compat3_17.11-0+deb13u1_riscv64.deb 0a172c140f5e2c07311f01aa76fa2ea937f27209cd8b96c3d0912c403402e42a 250528 libecpg-dev-dbgsym_17.11-0+deb13u1_riscv64.deb 3b8ba8240c20ccc3b1e0c32176b14f515bfdb91576bff39acd312ebe1c26ce42 392816 libecpg-dev_17.11-0+deb13u1_riscv64.deb a030bf7d4560d80f857d91950e2d27481289c6f1c1eed3ed6af3267efaa924c7 107516 libecpg6-dbgsym_17.11-0+deb13u1_riscv64.deb 2d80ba5ed947dc1dcaf8fed811262dcbdb541c17683e10db0751aff50ac3819a 68616 libecpg6_17.11-0+deb13u1_riscv64.deb 1a44d1d080687d0b50499c781b8c73f43faae844bf982e481dd43f70f55e214e 86228 libpgtypes3-dbgsym_17.11-0+deb13u1_riscv64.deb ca0cc208b18c9ce56eb708b92ece79745f760390bf9d29938054bb0b6d18fbf2 54420 libpgtypes3_17.11-0+deb13u1_riscv64.deb db7f6cf60e5cbb8855f795bfbdf36e546169707a96917f33a0e757acb57baba3 273676 libpq-dev_17.11-0+deb13u1_riscv64.deb f7cb67f0b12df07a98213f09a8b959e96942cbb0cf9ee840b638199f54cd47a6 287416 libpq5-dbgsym_17.11-0+deb13u1_riscv64.deb 60371cde6a64a4aea085f2e7d97d2852a06ec78f2cc4aabbda1fe3a83ea0a14d 236748 libpq5_17.11-0+deb13u1_riscv64.deb 76b33d4c3d2b321dcacf76afe28d2c66422fbbc917fc18f2c36ed011558af40f 17393376 postgresql-17-dbgsym_17.11-0+deb13u1_riscv64.deb 8ab1e65fa5f463006f2aeb7d4c7c720a3c02d76f956fba701c815840c954fca3 16844 postgresql-17_17.11-0+deb13u1_riscv64-buildd.buildinfo 4bf6c143fbe4e81ae7cc41332b5ad619baa09325053e17d618b8359975796975 6986916 postgresql-17_17.11-0+deb13u1_riscv64.deb e5c5709f17aad6372a8148d7a510ba2cf411a3972c96eed6e174684b876008c8 2919268 postgresql-client-17-dbgsym_17.11-0+deb13u1_riscv64.deb d1697a55700bd6b5f78ad0558b2361fa9127bccd97210a1c213c14f3e9f7e457 2054640 postgresql-client-17_17.11-0+deb13u1_riscv64.deb b989e738555422aa6de44fe6ea853dd6c2d2950d8109ad28c1502f77bad8b012 193884 postgresql-plperl-17-dbgsym_17.11-0+deb13u1_riscv64.deb bd4132845fcd4d06ec612a1147add0b20a841aa5eed63b9bb1f7904366fa2d46 77220 postgresql-plperl-17_17.11-0+deb13u1_riscv64.deb ceb682ba517a726175d7c0cdbe3e0c9aea10b3d33686464bbaba4d5ead6b4e71 197540 postgresql-plpython3-17-dbgsym_17.11-0+deb13u1_riscv64.deb 85ff52295ad947fea57db8ffbf860e31b41784502dd6b0178e9727a196bc2e36 98032 postgresql-plpython3-17_17.11-0+deb13u1_riscv64.deb 09756192110b16c51f5d5906a494ba88d028f8a93b47cb25d8f822699ef3289e 83192 postgresql-pltcl-17-dbgsym_17.11-0+deb13u1_riscv64.deb 0a3bbea9660513ea66afdb4bf192dbd8aab36e0db685ea6ed173d22b9bb82745 49412 postgresql-pltcl-17_17.11-0+deb13u1_riscv64.deb 0d6293881b5d9075854b1a2c7c0586cd80489fce56f74ca450c7d8959f41b22a 53748 postgresql-server-dev-17-dbgsym_17.11-0+deb13u1_riscv64.deb 21ede0ad62b523e68e24e0a6dee468df932ecba2543ae280ba9c0b27d0be2e52 1544212 postgresql-server-dev-17_17.11-0+deb13u1_riscv64.deb Files: a48b3941f2df530868e962262f61a969 16740 debug optional libecpg-compat3-dbgsym_17.11-0+deb13u1_riscv64.deb fd441c0036be1367321422dc042d56fe 24896 libs optional libecpg-compat3_17.11-0+deb13u1_riscv64.deb a460e16d56732190885fc7d108da90b1 250528 debug optional libecpg-dev-dbgsym_17.11-0+deb13u1_riscv64.deb 3e1733ad902d2ddef7e6099ab50fe358 392816 libdevel optional libecpg-dev_17.11-0+deb13u1_riscv64.deb 7b8fd68bdd1cb752114714df1c3ddc06 107516 debug optional libecpg6-dbgsym_17.11-0+deb13u1_riscv64.deb 789f1e84386c5ba6fc01c001187a5fbb 68616 libs optional libecpg6_17.11-0+deb13u1_riscv64.deb d61bd41f565f91bb8c9b28c7ae4eaf14 86228 debug optional libpgtypes3-dbgsym_17.11-0+deb13u1_riscv64.deb 8ba80ed39ab8cc43f2921768c24195ae 54420 libs optional libpgtypes3_17.11-0+deb13u1_riscv64.deb 98382eaf22410b9205014ac2b0048e71 273676 libdevel optional libpq-dev_17.11-0+deb13u1_riscv64.deb 5c4426f5d81ff526d675d0109a5c97c8 287416 debug optional libpq5-dbgsym_17.11-0+deb13u1_riscv64.deb be6f675a32bdf263f40d71e728b30c61 236748 libs optional libpq5_17.11-0+deb13u1_riscv64.deb 5d410d676824f359494184332b471edf 17393376 debug optional postgresql-17-dbgsym_17.11-0+deb13u1_riscv64.deb ba36f10118c0fc5f02af23957897f930 16844 database optional postgresql-17_17.11-0+deb13u1_riscv64-buildd.buildinfo 20692443d5993ed91fc6db01a5287d21 6986916 database optional postgresql-17_17.11-0+deb13u1_riscv64.deb 5148bfe1ea8a071edb5e80da5b3395ba 2919268 debug optional postgresql-client-17-dbgsym_17.11-0+deb13u1_riscv64.deb a7e692c2a116babf8432f948d2255d27 2054640 database optional postgresql-client-17_17.11-0+deb13u1_riscv64.deb 58ffe252a8742b26df485810d040f3d9 193884 debug optional postgresql-plperl-17-dbgsym_17.11-0+deb13u1_riscv64.deb 69386480b80a3fe814fa5a932fbc3e1a 77220 database optional postgresql-plperl-17_17.11-0+deb13u1_riscv64.deb a7e16a555c51eb528abc187028c79b5b 197540 debug optional postgresql-plpython3-17-dbgsym_17.11-0+deb13u1_riscv64.deb 7ca4cb8b0637d81de979bec505982113 98032 database optional postgresql-plpython3-17_17.11-0+deb13u1_riscv64.deb fc9fa2d13e214b800c84e7a73d42ebfe 83192 debug optional postgresql-pltcl-17-dbgsym_17.11-0+deb13u1_riscv64.deb 3b3a077f89cf3b96b8c7823f492997fc 49412 database optional postgresql-pltcl-17_17.11-0+deb13u1_riscv64.deb bda803f7a6db88413bfcc27b83061187 53748 debug optional postgresql-server-dev-17-dbgsym_17.11-0+deb13u1_riscv64.deb 0c9cc174154b51725daedface7aed008 1544212 libdevel optional postgresql-server-dev-17_17.11-0+deb13u1_riscv64.deb -----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEEXZ9jHPkg/vETgMJZlJNduPxUf2oFAmp9s5gACgkQlJNduPxU f2qlExAAlbeoPENhWn+9YdJ8tk1AC70UoPGfD8ehEsKtX2KTQtuK2VAycExxgrWX j8E53hj21rJV+qRVQIe5kDUffjKos++TwojPoZElai/L1eHmdZGfz01m1AQkgK7V jF1aBxo91Yg5q22rDcVw5XCWkz+hS1NB6WAJWHzNGhaE5r6XmDjmJkmgKea/AYXL NO6n5jGegOVKR2fkgSz5Ha6MNnwQb+3yVrhNGyjDcCulfvFWzZSv4sdJ9zOYnfB9 ncEXo6RjbjPKUr6OZRabJAmgW9SuPsl57VYqDbaE5BY2eABPul0w2CSkZfJDO6wO Q6tEZw68dX5phCkLudPd3N0OG/jwDdwXTT0h5GsrxSIr3RWwbKVDpue6P23pBiz3 XTAPUKiAV4487J0LLrUdwPWFrsD5MWv5TSlBkmRCX//GCzEKbd3POn/fB4Mzl9xD GJi0MRS9Gb4IKmQWFm9SI5q12y8KXpdv8EeYqTfVfNFqUkpaqq0S0Zfr7SWn3qS3 3BLi/glM0wRzMt1CJsMQXAOx2N5Q6W20c+NfKyEsLznl4vNBrNAv9zOMWuygyMTd V4aoUdynVO6mHxqeRilgICPGzjnMh1TLdzpbecHPljSpM/Goc2aEu2V5J2PAkSWB RuVRiIgylNdHgJ9T9T8W5eCyncE0+TgruoeTJKAlKoTF7aKcpPY= =FRgu -----END PGP SIGNATURE-----