-----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: armhf Version: 17.11-0+deb13u1 Distribution: trixie-security Urgency: medium Maintainer: armhf Build Daemon (arm-conova-02) 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: 11e1becf1929cd8c1ed4be8a4b76781d9f68a7bc 16912 libecpg-compat3-dbgsym_17.11-0+deb13u1_armhf.deb 2cf9ed44079f6972297e367392bfe41cf2577752 23624 libecpg-compat3_17.11-0+deb13u1_armhf.deb fcfb80cc6ca08da06eccf769ed2db66a205ec032 251536 libecpg-dev-dbgsym_17.11-0+deb13u1_armhf.deb 23fa32824156be55f9e5fcf917bb733d8d249f36 290156 libecpg-dev_17.11-0+deb13u1_armhf.deb dbc3c8c386c1b82050a758ddf7d925dc65733c11 114284 libecpg6-dbgsym_17.11-0+deb13u1_armhf.deb e4a4fe5168da622e15f7cbd281b114ea4a775a3a 62320 libecpg6_17.11-0+deb13u1_armhf.deb 575171f3f9dde8fe975ea80095af68aab2fde402 91328 libpgtypes3-dbgsym_17.11-0+deb13u1_armhf.deb b287c3323f272935c57536fba199584741d0bd18 48740 libpgtypes3_17.11-0+deb13u1_armhf.deb 65d7ef7ec27c81d905757818a556e51ffa11aff0 147124 libpq-dev_17.11-0+deb13u1_armhf.deb db408fa45813f4c86c91885888bf1ad5b433f236 298028 libpq5-dbgsym_17.11-0+deb13u1_armhf.deb 00f47a5d6b79b1febdb03940b6be87fbcbee9c82 220104 libpq5_17.11-0+deb13u1_armhf.deb 0c1a8a4d1075b52ac9b9b1bdcb610ca0b02f3aa7 18956460 postgresql-17-dbgsym_17.11-0+deb13u1_armhf.deb 3d86922f53503bccbf7ea3d36e8c08e45c92d30e 17455 postgresql-17_17.11-0+deb13u1_armhf-buildd.buildinfo 259773c365c85299cf34f91318a6b593d96f1497 16000632 postgresql-17_17.11-0+deb13u1_armhf.deb cbe4036f53a16d48725e3306cff29a58c8ff1058 2867668 postgresql-client-17-dbgsym_17.11-0+deb13u1_armhf.deb ad52bc128b6de8323b365f517d86e2addbeb07ba 1963472 postgresql-client-17_17.11-0+deb13u1_armhf.deb a252668a47f848b2fd47ee9b0bfaaf5847fd6427 197256 postgresql-plperl-17-dbgsym_17.11-0+deb13u1_armhf.deb 1e45285c75278b321dc36983b8b3753b98fb1db1 90132 postgresql-plperl-17_17.11-0+deb13u1_armhf.deb 9c27cb7a7b93dd7436c41dbde502ee58b89e30bd 199036 postgresql-plpython3-17-dbgsym_17.11-0+deb13u1_armhf.deb 0658ae302c07569a2311bd2a99b243562219ef7c 113188 postgresql-plpython3-17_17.11-0+deb13u1_armhf.deb 5771cca401baaa9ae6be3913c83177a85587582b 82580 postgresql-pltcl-17-dbgsym_17.11-0+deb13u1_armhf.deb 2bea045fabd29279188de6fce118c01b29a24d47 48020 postgresql-pltcl-17_17.11-0+deb13u1_armhf.deb 565df95401ea7cec07d05e328f21995a589092f2 55804 postgresql-server-dev-17-dbgsym_17.11-0+deb13u1_armhf.deb 3c7e48375114e3fe85ce82ce23494455fcf28e5b 1310084 postgresql-server-dev-17_17.11-0+deb13u1_armhf.deb Checksums-Sha256: 14502a28067cce5256fb430346a396b2ca06023ae69073bb1d844ccb44df8095 16912 libecpg-compat3-dbgsym_17.11-0+deb13u1_armhf.deb 91137a75a4538613dd42f18a0ea630c7f637432d648d8aca74e58f3479618fd1 23624 libecpg-compat3_17.11-0+deb13u1_armhf.deb e07a0b71072a5db5d30b235b2b28ade043205f686d19774b3f27da67b148339f 251536 libecpg-dev-dbgsym_17.11-0+deb13u1_armhf.deb 863114c1519314993d5058cce35c86d700bc20654642ba7f2c3878fb5e4ca952 290156 libecpg-dev_17.11-0+deb13u1_armhf.deb 79873580f5dd939a65c4c2bddd90f1a601f3aa3aff37ed2c6259df1e58423160 114284 libecpg6-dbgsym_17.11-0+deb13u1_armhf.deb ed59e823a652f8b7673f7e816bb24df9a44ac560e755b992a581703bf95a3165 62320 libecpg6_17.11-0+deb13u1_armhf.deb dafc1ca59c2a4bb89e552b9a5c95649346047f347d7d557f2bc9cbf25f468809 91328 libpgtypes3-dbgsym_17.11-0+deb13u1_armhf.deb 4bfcd1834c64dfefef596563ab80aee3bbb4e6abbc3b922bf6cc445373cc0bc8 48740 libpgtypes3_17.11-0+deb13u1_armhf.deb ccb88f331ec235d2c79b01992cf15b47c12e74948b72c808d06480f3458dc000 147124 libpq-dev_17.11-0+deb13u1_armhf.deb 5c13ed95f9074887d20b119f21c6bc1957c3a4b5ab55f6439df132fb18c38188 298028 libpq5-dbgsym_17.11-0+deb13u1_armhf.deb 1a6575afff62b1780799b45fe21383811758128bfc853cbe8abbe616ad946e98 220104 libpq5_17.11-0+deb13u1_armhf.deb 0d5e5b36a85ea9eed7fb7226cfcd9c508c82520212b2cb698439c78a24d8d3f1 18956460 postgresql-17-dbgsym_17.11-0+deb13u1_armhf.deb 51e78bb3ae4a897b1c3eb8d07a81f4f05273f6fcd80bfb8740826a4a2f3eaf16 17455 postgresql-17_17.11-0+deb13u1_armhf-buildd.buildinfo 4da389857733dc332d3a0e93a8a585172fbad9516e7358daf3a1c5015a937b13 16000632 postgresql-17_17.11-0+deb13u1_armhf.deb 5b1831dc73fb074ceeb38a61bffdfdc949716e3d37a7eb49eae1ef5f8613ff01 2867668 postgresql-client-17-dbgsym_17.11-0+deb13u1_armhf.deb 1b85bfc64e8605233c6ec2a87505495b8869ddc49b16d2d72b878386f0b8bbba 1963472 postgresql-client-17_17.11-0+deb13u1_armhf.deb bf117e494931c93a5d076106cec0f5648962b522c763b652dd989a7b7742fc0b 197256 postgresql-plperl-17-dbgsym_17.11-0+deb13u1_armhf.deb f50d995390c5c201e255af1ede775b5324d6c388a209ef947165cbac48ce4675 90132 postgresql-plperl-17_17.11-0+deb13u1_armhf.deb aaa9427f5e8e33e293b9dabfede1364d2fcb37e2e838eb0824c498b1d4db4209 199036 postgresql-plpython3-17-dbgsym_17.11-0+deb13u1_armhf.deb 2c9b639103838bfa850003abf4cf9ac944c4c9a411bba678297e4654ada25a6d 113188 postgresql-plpython3-17_17.11-0+deb13u1_armhf.deb d148bb8f74883e4712f6bacff032d44158da9e95f9b99a7ca81e13d49c064985 82580 postgresql-pltcl-17-dbgsym_17.11-0+deb13u1_armhf.deb 2ff76da4e184ce87778ca9f049fb9c0f9b8e6b4064240454adbdf5111ffc8abd 48020 postgresql-pltcl-17_17.11-0+deb13u1_armhf.deb 8ad9854ea486df3b2a91459bbefa20e579b3ad8248c17d719201733dd7f3c231 55804 postgresql-server-dev-17-dbgsym_17.11-0+deb13u1_armhf.deb 03f562b41bd010ac50ccc1b95ee0be9656807dfe8450c37beedb71902260e9a7 1310084 postgresql-server-dev-17_17.11-0+deb13u1_armhf.deb Files: 87f7d30761357eaf7b3de7e6145ad30d 16912 debug optional libecpg-compat3-dbgsym_17.11-0+deb13u1_armhf.deb 04159440fe038e8c1e1687acfd356212 23624 libs optional libecpg-compat3_17.11-0+deb13u1_armhf.deb 367b0c0a4f1553946cb29869535b9778 251536 debug optional libecpg-dev-dbgsym_17.11-0+deb13u1_armhf.deb 76c3a8c5e6177c5e46a86b30c684cd2d 290156 libdevel optional libecpg-dev_17.11-0+deb13u1_armhf.deb aff7180ec0058fcf306600ab7917f645 114284 debug optional libecpg6-dbgsym_17.11-0+deb13u1_armhf.deb 8afffe63b36d409c80329e112f3a4d10 62320 libs optional libecpg6_17.11-0+deb13u1_armhf.deb 08d3b752654de1a7bd3b3b85ec7b4c0f 91328 debug optional libpgtypes3-dbgsym_17.11-0+deb13u1_armhf.deb e01fb844da3c78b0def2e1b9aa2aeca7 48740 libs optional libpgtypes3_17.11-0+deb13u1_armhf.deb 83101a98163cc5058af01a063d227684 147124 libdevel optional libpq-dev_17.11-0+deb13u1_armhf.deb c073f6be92220b63b3554aabe484acc0 298028 debug optional libpq5-dbgsym_17.11-0+deb13u1_armhf.deb 02f737fe7e401b6ad7c911d6a295900d 220104 libs optional libpq5_17.11-0+deb13u1_armhf.deb 30625136fc72097406dde74ac2863b34 18956460 debug optional postgresql-17-dbgsym_17.11-0+deb13u1_armhf.deb 0d460df21f901cc600d9ae8e92adf66d 17455 database optional postgresql-17_17.11-0+deb13u1_armhf-buildd.buildinfo a0c741e81595154ee16d4a8224887fd6 16000632 database optional postgresql-17_17.11-0+deb13u1_armhf.deb cf9964d2453345ca19cfa09d36e5184f 2867668 debug optional postgresql-client-17-dbgsym_17.11-0+deb13u1_armhf.deb d6d782cf39d9ccc8342537e3c917e29c 1963472 database optional postgresql-client-17_17.11-0+deb13u1_armhf.deb 4f0c7e471d9790dc5fd4a892439fe377 197256 debug optional postgresql-plperl-17-dbgsym_17.11-0+deb13u1_armhf.deb 0f8773e8c6ceb71203c12819b0936017 90132 database optional postgresql-plperl-17_17.11-0+deb13u1_armhf.deb 426c0f2fa504fdab917171705848bd0c 199036 debug optional postgresql-plpython3-17-dbgsym_17.11-0+deb13u1_armhf.deb 44a44283a9b835d06f126497052771a5 113188 database optional postgresql-plpython3-17_17.11-0+deb13u1_armhf.deb 71026747fb5302b6da4ba09c34f63716 82580 debug optional postgresql-pltcl-17-dbgsym_17.11-0+deb13u1_armhf.deb d1f5dc8a02ebf33eed73e6d57577f259 48020 database optional postgresql-pltcl-17_17.11-0+deb13u1_armhf.deb 3b99d7a2603c05b1382928a202b14a43 55804 debug optional postgresql-server-dev-17-dbgsym_17.11-0+deb13u1_armhf.deb 4f8aa3408044905a5544bdd098d908d1 1310084 libdevel optional postgresql-server-dev-17_17.11-0+deb13u1_armhf.deb -----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEEa5s+5E+WDkV2pQjwIyDMsRzdi8EFAmp9kcsACgkQIyDMsRzd i8FBUBAAop8ATq1tBlSPtQ0sR2T3GYFEE3yj/9BmAMjuVj/NeG/8c5sidGdf4+Ac FMfWwyh3VUh2iwTtC4RvfRPRnWVqEyntc0ISNlaptB5Ya6dE1040K/rWR4Y5kSB/ kceFddWcrLrtY8qEPQPPfSUwrrlOSz7QiBGXupGti2KJNuFcgBiikrezTWyUZC1G kfBdLXd5aLqI2LFiBe1AtXJxa+W8M6mQB2n6nLXp805Vsf6fE18jewh7mqoZd4/l eBRZGsBYnheEZCqgp/RTESaZiL/8W+lPN5T41OK0mCkMgwWet0Mc2FR4ipo4798B 69nMSGRCooxC6ATcuZ8KHncy0GTajt1DzPhGhyWRgazgWu19MiAoYUxzqkRDJsk+ bWbqV5BA6VxCyA4cy9C6WBoKxpVP/uVm3vCkPmQs0Wbdbt2YWlLAGVyYbz8ep5AO nqJktnsDVlMFv7PskCJgDcPdxnKYAQgKXZVxI36xFOyfj9sasUyWCM2F/IReJhx6 iySpPBNED4mId3etn89X++BZi36lX5JaC26cQLhpS7IAuE6zt5Id0IK0BXX7crX9 N5gNYvr5A0gv2Yc0Zs1KPTeWyRm+xdTflLMxqU0DdsNTkG0TZHTyLiv4j+81e2bu 7m0QDEuBkeDzKPj2bMQyF0vdm7iSyLnUrF9ODWqAHUtqUKFUKuY= =Pgq5 -----END PGP SIGNATURE-----