postgresql:18 security update
エラータID: AXSA:2026-1927:01
PostgreSQL is an advanced object-relational database management system (DBMS).
Security Fix(es):
* postgresql: PostgreSQL: SQL injection in pg_createsubscriber allows arbitrary SQL execution as superuser (CVE-2026-6476)
* postgresql: PostgreSQL: Arbitrary code execution via integer wraparound in tsvector and tsquery functions (CVE-2026-14662)
* postgresql: PostgreSQL: Arbitrary code execution via untrusted data inclusion in pg_dump (CVE-2026-18408)
* postgresql: PostgreSQL psql: Arbitrary command execution via untrusted data in COPY FROM STDIN (CVE-2026-6464)
* postgresql: PostgreSQL: Arbitrary code execution via logical decoding plugin (CVE-2026-6471)
* postgresql: PostgreSQL: Arbitrary code execution via type confusion with "internal" arguments (CVE-2026-14680)
* postgresql: PostgreSQL: Arbitrary code execution via heap buffer overflow in regexp (CVE-2026-14664)
* postgresql: pltcl: plperl: PostgreSQL: Arbitrary code execution in 32-bit pltcl and plperl (CVE-2026-14677)
* postgresql-fuzzystrmatch: PostgreSQL fuzzystrmatch: Arbitrary code execution via integer wraparound (CVE-2026-15742)
* postgresql: PostgreSQL: Arbitrary code execution via type confusion in cursor lifecycle (CVE-2026-16239)
* postgresql: PostgreSQL: Arbitrary code execution via long POSIX timezone abbreviation (CVE-2026-14669)
* postgresql: PostgreSQL: Arbitrary code execution via type confusion in pg_restore_attribute_stats() (CVE-2026-16238)
* postgresql: PostgreSQL: Stack buffer overflow via OUT parameter count manipulation (CVE-2026-14679)
* postgresql: PostgreSQL: Arbitrary code execution via type confusion in 'refint' module (CVE-2026-14671)
* postgresql: PostgreSQL pg_stat_statements: Arbitrary code execution via heap buffer overflow (CVE-2026-14676)
* postgresql: PostgreSQL: Arbitrary code execution via plperl tied hash heap buffer overflow (CVE-2026-14670)
* postgresql: PostgreSQL: Information disclosure via type confusion in ctid selectivity estimator (CVE-2026-14668)
* postgresql: PostgreSQL pg_dump: Arbitrary code execution via crafted transform lists (CVE-2026-19385)
* postgresql: PostgreSQL: Privilege escalation via SQL injection in EXTRACT() deparse (CVE-2026-15741)
* postgis: PostGIS: Memory Disclosure and Denial of Service via Malformed FlatGeobuf Buffer (CVE-2026-73515)
For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.
CVE-2026-14662
Integer wraparound in PostgreSQL tsvector and tsquery data type functions allows an unprivileged database user to cause the server to undersize an allocation and write out-of-bounds, via crafted large inputs. This may execute arbitrary code as the operating system user running the database. These types are typically sourced from application logic, not taken from the application's user. Hence, application users attacking the database, through the application as a conduit, are unlikely. CVE-2026-6473 had fixed similar problems. Versions before PostgreSQL 18.6, 17.11, 16.15, 15.19, and 14.24 are affected.
CVE-2026-14664
Heap buffer overflow in PostgreSQL regexp allows the query author to execute arbitrary code as the operating system user running the database, via text that would not pass encoding validation. This shares heritage with CVE-2026-2006, but this case involved unanticipated data growth when round-tripped through pg_wchar. Versions before PostgreSQL 18.6, 17.11, 16.15, 15.19, and 14.24 are affected.
CVE-2026-14668
Type confusion regarding input of PostgreSQL ctid data type selectivity estimator allows an object creator to view a calculation derived from the value of an arbitrary 4-byte span of memory, via a chosen non-ctid input. While the calculation loses precision, substantial memory value recovery appears possible. Versions before PostgreSQL 18.6, 17.11, 16.15, 15.19, and 14.24 are affected.
CVE-2026-14669
Heap buffer overflow in PostgreSQL to_char(timestamptz) allows the party choosing the timezone to execute arbitrary code as the operating system user running the database, via a long POSIX timezone abbreviation. Versions before PostgreSQL 18.6, 17.11, 16.15, 15.19, and 14.24 are affected.
CVE-2026-14670
Heap buffer overflow in PostgreSQL plperl return of a tied hash allows the function owner to execute arbitrary code as the operating system user running the database, via a crafted function body. Versions before PostgreSQL 18.6, 17.11, 16.15, 15.19, and 14.24 are affected.
CVE-2026-14671
Type confusion in PostgreSQL module "refint" allows an object creator to execute arbitrary code as the operating system user running the database. The fix for this emerged as a non-security bug report, and the fix appear in the git repository with subject "refint: Remove plan cache.", without a CVE number. Versions before PostgreSQL 18.6, 17.11, 16.15, 15.19, and 14.24 are affected.
CVE-2026-14676
Heap buffer overflow in PostgreSQL pg_stat_statements allows the query author to execute arbitrary code as the operating system user running the database, via crafted queries containing array constants. Within major version 18, minor versions before PostgreSQL 18.6 are affected. Versions before PostgreSQL 18 are unaffected.
CVE-2026-14677
Integer wraparound in PostgreSQL 32-bit builds of pltcl and plperl allows an object creator to cause the server to undersize an allocation and write out-of-bounds via crafted function bodies. This may execute arbitrary code as the operating system user running the database. CVE-2026-6473 had fixed similar problems. Versions before PostgreSQL 18.6, 17.11, 16.15, 15.19, and 14.24 are affected.
CVE-2026-14679
Stack buffer overflow in PostgreSQL argument name matching allows an object creator to achieve unknown impacts via OUT parameter count. The attack can write only 0x0 and 0x1 bytes. Versions before PostgreSQL 18.6, 17.11, 16.15, 15.19, and 14.24 are affected.
CVE-2026-14680
Type confusion with PostgreSQL "internal" data type arguments allows any user to execute arbitrary code as the operating system user running the database, via calls to functions with that argument type. Type "internal" represents a class of mutually-incompatible data structures not intended for access from SQL. The system intended to prevent such function calls, but this prevention had gaps. Versions before PostgreSQL 18.6, 17.11, 16.15, 15.19, and 14.24 are affected.
CVE-2026-15741
SQL injection in PostgreSQL EXTRACT() deparse allows an object owner to execute arbitrary SQL as a superuser via a hostile object definition. Attacks affect expression deparse consumers broadly, including pg_dump, psql commands like \sf, and any similar usage in non-core tools. Versions before PostgreSQL 18.6, 17.11, 16.15, 15.19, and 14.24 are affected.
CVE-2026-15742
Integer wraparound in PostgreSQL fuzzystrmatch allows a user to direct writes to a huge range of addresses, executing arbitrary code as the operating system user running the database, via extreme inputs to SQL function levenshtein() or levenshtein_less_equal(). Versions before PostgreSQL 18.6, 17.11, 16.15, 15.19, and 14.24 are affected.
CVE-2026-16238
Type confusion in PostgreSQL pg_restore_attribute_stats() allows an object creator to execute arbitrary code as the operating system user running the database, via conflation of range and multirange values. Within major version 18, minor versions before PostgreSQL 18.6 are affected. Versions before PostgreSQL 18 are unaffected.
CVE-2026-16239
Type confusion in PostgreSQL "portal"/cursor lifecycle allows a user to execute arbitrary code as the operating system user running the database, via re-creation of a cursor or other portal with different types. Versions before PostgreSQL 18.6, 17.11, 16.15, 15.19, and 14.24 are affected.
CVE-2026-18408
Untrusted data inclusion in pg_dump in PostgreSQL allows a malicious superuser of the origin server to inject arbitrary code for restore-time execution as the client operating system account running psql to restore the dump, via psql \restrict meta-command input expansion. The fix for CVE-2025-8714 introduced \restrict and \unrestrict to block this attack, but \unrestrict itself was sufficient for an attack. pg_dumpall is also affected. pg_restore is affected when used to generate a plain-format dump. Non-core use of \restrict would be affected, but we've not identified non-core use. Versions before PostgreSQL 18.6, 17.11, 16.15, 15.19, and 14.24 are affected.
CVE-2026-19385
Heap buffer overflow in PostgreSQL pg_dump of long function transform lists allows an object creator to execute arbitrary code as the operating system user running pg_dump, via a crafted transform list. Versions before PostgreSQL 18.6, 17.11, 16.15, 15.19, and 14.24 are affected.
CVE-2026-6464
Untrusted data inclusion in PostgreSQL psql COPY may allow a server administrator to elicit execution of data lines as psql commands, via error injection. If the "COPY FROM STDIN" or "\copy FROM STDIN" command fails before the server indicates that it awaits input rows, psql processes the in-line data rows as psql commands. "COPY FROM" with a filename is unaffected. The server administrator has no inherent control over the data rows, so a complete attack requires the attacker to separately acquire control of both the server and the data rows. Alternatively, an attacker controlling data rows alone might complete an attack through a coincidental error that they don't control. Versions before PostgreSQL 18.6, 17.11, 16.15, 15.19, and 14.24 are affected.
CVE-2026-6471
Missing authorization in PostgreSQL logical decoding allows a non-superuser holding REPLICATION privilege to dlopen any file visible to the operating system account running the server, via the choice of logical decoding plugin. This in turn runs arbitrary code as that account. Versions before PostgreSQL 18.6, 17.11, 16.15, 15.19, and 14.24 are affected.
CVE-2026-6476
SQL injection in PostgreSQL pg_createsubscriber allows an attacker with pg_create_subscription rights to execute arbitrary SQL as a superuser. The attack takes effect when pg_createsubscriber next runs. Within major versions 17 and 18, minor versions before PostgreSQL 18.4 and 17.10 are affected. Versions before PostgreSQL 17 are unaffected.
CVE-2026-73515
PostGIS before 3.7.0beta2 contains an out-of-bounds read vulnerability that allows attackers to cause memory disclosure or a server crash by supplying a malformed FlatGeobuf buffer. The FlatGeobuf property metadata decoder verifies that a string length field is present but fails to verify that the subsequent string body is contained within the supplied buffer before materializing it into a SQL-visible value, enabling memory disclosure or denial of service.
Modularity name: "postgresql"
Stream name: "18"
Update packages.
Integer wraparound in PostgreSQL tsvector and tsquery data type functions allows an unprivileged database user to cause the server to undersize an allocation and write out-of-bounds, via crafted large inputs. This may execute arbitrary code as the operating system user running the database. These types are typically sourced from application logic, not taken from the application's user. Hence, application users attacking the database, through the application as a conduit, are unlikely. CVE-2026-6473 had fixed similar problems. Versions before PostgreSQL 18.6, 17.11, 16.15, 15.19, and 14.24 are affected.
Heap buffer overflow in PostgreSQL regexp allows the query author to execute arbitrary code as the operating system user running the database, via text that would not pass encoding validation. This shares heritage with CVE-2026-2006, but this case involved unanticipated data growth when round-tripped through pg_wchar. Versions before PostgreSQL 18.6, 17.11, 16.15, 15.19, and 14.24 are affected.
Type confusion regarding input of PostgreSQL ctid data type selectivity estimator allows an object creator to view a calculation derived from the value of an arbitrary 4-byte span of memory, via a chosen non-ctid input. While the calculation loses precision, substantial memory value recovery appears possible. Versions before PostgreSQL 18.6, 17.11, 16.15, 15.19, and 14.24 are affected.
Heap buffer overflow in PostgreSQL to_char(timestamptz) allows the party choosing the timezone to execute arbitrary code as the operating system user running the database, via a long POSIX timezone abbreviation. Versions before PostgreSQL 18.6, 17.11, 16.15, 15.19, and 14.24 are affected.
Heap buffer overflow in PostgreSQL plperl return of a tied hash allows the function owner to execute arbitrary code as the operating system user running the database, via a crafted function body. Versions before PostgreSQL 18.6, 17.11, 16.15, 15.19, and 14.24 are affected.
Type confusion in PostgreSQL module "refint" allows an object creator to execute arbitrary code as the operating system user running the database. The fix for this emerged as a non-security bug report, and the fix appear in the git repository with subject "refint: Remove plan cache.", without a CVE number. Versions before PostgreSQL 18.6, 17.11, 16.15, 15.19, and 14.24 are affected.
Heap buffer overflow in PostgreSQL pg_stat_statements allows the query author to execute arbitrary code as the operating system user running the database, via crafted queries containing array constants. Within major version 18, minor versions before PostgreSQL 18.6 are affected. Versions before PostgreSQL 18 are unaffected.
Integer wraparound in PostgreSQL 32-bit builds of pltcl and plperl allows an object creator to cause the server to undersize an allocation and write out-of-bounds via crafted function bodies. This may execute arbitrary code as the operating system user running the database. CVE-2026-6473 had fixed similar problems. Versions before PostgreSQL 18.6, 17.11, 16.15, 15.19, and 14.24 are affected.
Stack buffer overflow in PostgreSQL argument name matching allows an object creator to achieve unknown impacts via OUT parameter count. The attack can write only 0x0 and 0x1 bytes. Versions before PostgreSQL 18.6, 17.11, 16.15, 15.19, and 14.24 are affected.
Type confusion with PostgreSQL "internal" data type arguments allows any user to execute arbitrary code as the operating system user running the database, via calls to functions with that argument type. Type "internal" represents a class of mutually-incompatible data structures not intended for access from SQL. The system intended to prevent such function calls, but this prevention had gaps. Versions before PostgreSQL 18.6, 17.11, 16.15, 15.19, and 14.24 are affected.
SQL injection in PostgreSQL EXTRACT() deparse allows an object owner to execute arbitrary SQL as a superuser via a hostile object definition. Attacks affect expression deparse consumers broadly, including pg_dump, psql commands like \sf, and any similar usage in non-core tools. Versions before PostgreSQL 18.6, 17.11, 16.15, 15.19, and 14.24 are affected.
Integer wraparound in PostgreSQL fuzzystrmatch allows a user to direct writes to a huge range of addresses, executing arbitrary code as the operating system user running the database, via extreme inputs to SQL function levenshtein() or levenshtein_less_equal(). Versions before PostgreSQL 18.6, 17.11, 16.15, 15.19, and 14.24 are affected.
Type confusion in PostgreSQL pg_restore_attribute_stats() allows an object creator to execute arbitrary code as the operating system user running the database, via conflation of range and multirange values. Within major version 18, minor versions before PostgreSQL 18.6 are affected. Versions before PostgreSQL 18 are unaffected.
Type confusion in PostgreSQL "portal"/cursor lifecycle allows a user to execute arbitrary code as the operating system user running the database, via re-creation of a cursor or other portal with different types. Versions before PostgreSQL 18.6, 17.11, 16.15, 15.19, and 14.24 are affected.
Untrusted data inclusion in pg_dump in PostgreSQL allows a malicious superuser of the origin server to inject arbitrary code for restore-time execution as the client operating system account running psql to restore the dump, via psql \restrict meta-command input expansion. The fix for CVE-2025-8714 introduced \restrict and \unrestrict to block this attack, but \unrestrict itself was sufficient for an attack. pg_dumpall is also affected. pg_restore is affected when used to generate a plain-format dump. Non-core use of \restrict would be affected, but we've not identified non-core use. Versions before PostgreSQL 18.6, 17.11, 16.15, 15.19, and 14.24 are affected.
Heap buffer overflow in PostgreSQL pg_dump of long function transform lists allows an object creator to execute arbitrary code as the operating system user running pg_dump, via a crafted transform list. Versions before PostgreSQL 18.6, 17.11, 16.15, 15.19, and 14.24 are affected.
Untrusted data inclusion in PostgreSQL psql COPY may allow a server administrator to elicit execution of data lines as psql commands, via error injection. If the "COPY FROM STDIN" or "\copy FROM STDIN" command fails before the server indicates that it awaits input rows, psql processes the in-line data rows as psql commands. "COPY FROM" with a filename is unaffected. The server administrator has no inherent control over the data rows, so a complete attack requires the attacker to separately acquire control of both the server and the data rows. Alternatively, an attacker controlling data rows alone might complete an attack through a coincidental error that they don't control. Versions before PostgreSQL 18.6, 17.11, 16.15, 15.19, and 14.24 are affected.
Missing authorization in PostgreSQL logical decoding allows a non-superuser holding REPLICATION privilege to dlopen any file visible to the operating system account running the server, via the choice of logical decoding plugin. This in turn runs arbitrary code as that account. Versions before PostgreSQL 18.6, 17.11, 16.15, 15.19, and 14.24 are affected.
SQL injection in PostgreSQL pg_createsubscriber allows an attacker with pg_create_subscription rights to execute arbitrary SQL as a superuser. The attack takes effect when pg_createsubscriber next runs. Within major versions 17 and 18, minor versions before PostgreSQL 18.4 and 17.10 are affected. Versions before PostgreSQL 17 are unaffected.
PostGIS before 3.7.0beta2 contains an out-of-bounds read vulnerability that allows attackers to cause memory disclosure or a server crash by supplying a malformed FlatGeobuf buffer. The FlatGeobuf property metadata decoder verifies that a string length field is present but fails to verify that the subsequent string body is contained within the supplied buffer before materializing it into a SQL-visible value, enabling memory disclosure or denial of service.
N/A
SRPMS
- pgaudit-18.0-1.module+el9+1199+27d9b1d1.src.rpm
MD5: 6d93ad9c4d51f618eaf9c916b4ae974a
SHA-256: 38c0b78e1ccc8c3187f9a925249e02c73afefa37b2a5cff7709dadedd582f7b7
Size: 54.32 kB - pg_repack-1.5.3-1.module+el9+1199+27d9b1d1.src.rpm
MD5: 0b45b3e826e4ae80507885dba2ce9e16
SHA-256: e2e5f5ac416a3ff6a552d7d58ef0bf4b2394bb57ca0ec28a5e63e167bd411f85
Size: 106.63 kB - pgvector-0.8.1-1.module+el9+1199+27d9b1d1.src.rpm
MD5: 699763da04488c6e2a23ab52bdcef72f
SHA-256: 17155195ac0344f5d9ffdf3da4987a1211495638816d92b67af5180184d232de
Size: 127.79 kB - postgis-3.6.1-4.module+el9+1199+27d9b1d1.src.rpm
MD5: 08cad9aa33617e3d6b9c31ab900f89db
SHA-256: e572335088109013fbea55ca3816751171fb425857fe7e443832f6b780b1fd86
Size: 15.48 MB - postgres-decoderbufs-3.3.1-1.Final.module+el9+1199+27d9b1d1.src.rpm
MD5: 2f20354b2f54ebe7ed5f03e2f46ed9bd
SHA-256: 91e199c788d476f0a5d478d7eec3aadffbc1988289614da5c4d66dcca906af22
Size: 21.53 kB - postgresql-18.6-1.module+el9+1199+27d9b1d1.src.rpm
MD5: 85994ee6a375c8c49e21c489506449e1
SHA-256: 7a4e68eeeee410a2fcb5653fea502767ea6f31bb8b658b9425d689b6555c4bfc
Size: 45.57 MB
Asianux Server 9 for x86_64
- pgaudit-18.0-1.module+el9+1199+27d9b1d1.x86_64.rpm
MD5: 7bec5d177123b3339dfdb63b9c7686c1
SHA-256: 776ef12a448431b1cb3b5e98effb2f9597bd31815fdf104bb351dbbf6fb94bb6
Size: 28.36 kB - pgaudit-debugsource-18.0-1.module+el9+1199+27d9b1d1.x86_64.rpm
MD5: 44e2545da3561152c7351c834bfcabdc
SHA-256: 22c0e1471dd1b6f8aaed4467c80502dfb955b6e227f929594c7fd523469190f3
Size: 23.51 kB - pg_repack-1.5.3-1.module+el9+1199+27d9b1d1.x86_64.rpm
MD5: 59e0b687d3a0f9ab89f78d7e339e9275
SHA-256: de995a5ea4029f55688d1caed58dabc0549aea39cd48e665238cb6103cfc53cb
Size: 93.02 kB - pg_repack-debugsource-1.5.3-1.module+el9+1199+27d9b1d1.x86_64.rpm
MD5: d375685d62b7615dcdf33c7fbd113b24
SHA-256: c05e11971c97260e988bf216ed6756b8265f5b67ea3f65769503f78e35e59ba7
Size: 49.40 kB - pgvector-0.8.1-1.module+el9+1199+27d9b1d1.x86_64.rpm
MD5: 8457b28259493dad458c60d246e544db
SHA-256: af743a55e4c995a73455e7e4e3d8452febe18563c16348c7385f44d7c2aa9b3e
Size: 115.35 kB - pgvector-debugsource-0.8.1-1.module+el9+1199+27d9b1d1.x86_64.rpm
MD5: 567092d5a999a64f2c342711fa265656
SHA-256: ca2c12a8da7519ee80fc7cd625b74eeb98fc7aabe8f1cb2618f772a7a551ce34
Size: 70.96 kB - postgis-3.6.1-4.module+el9+1199+27d9b1d1.x86_64.rpm
MD5: 91e94c828388461ebc4a7f3ab123317b
SHA-256: 7cbafd927ea5e26182652863f67d2db4ded2b9d8c40d285b6d9ed0118ef31b07
Size: 1.79 MB - postgis-client-3.6.1-4.module+el9+1199+27d9b1d1.x86_64.rpm
MD5: b5e58e1de8a435805a0b72110abc6387
SHA-256: 66d4f998374a11ce2bc5af9cdb5cd9473d77dbd8775e1be0f797dae6edf4b3d6
Size: 115.68 kB - postgis-debugsource-3.6.1-4.module+el9+1199+27d9b1d1.x86_64.rpm
MD5: 820f31bc0821f6dfd4d47cf7339207f9
SHA-256: fcdea15520fd25b2f756c4749df91134cbc1ec7e3565d1dfff9a729a42284dc7
Size: 1.07 MB - postgis-docs-3.6.1-4.module+el9+1199+27d9b1d1.x86_64.rpm
MD5: c2ea1c3a5b59c22f8096d0e27614e641
SHA-256: ac79dd5e60d994608cbdacaa3f93a09ee76a6a0f7a0c1eebc7cb6f73a1cda14d
Size: 7.37 kB - postgis-upgrade-3.6.1-4.module+el9+1199+27d9b1d1.x86_64.rpm
MD5: a9e59a0f3dadfce85203f8eb8b755b93
SHA-256: bc030ca47715bfae5c3c4d744e69bb3c01f6c97d0819ffb0db1e7345076784c9
Size: 791.31 kB - postgis-utils-3.6.1-4.module+el9+1199+27d9b1d1.x86_64.rpm
MD5: cb44c306c860455a38736efef07e4619
SHA-256: 3ff743132434642328d3463f2749282ebeb18e2d87a24336cb4d18bb755dda2d
Size: 35.92 kB - postgres-decoderbufs-3.3.1-1.Final.module+el9+1199+27d9b1d1.x86_64.rpm
MD5: db8fb3c5c33c03355434c9eeea5a3f82
SHA-256: a85101b010d9c6e614002c06e9ead375f3be14f3e764329de955c4ddf083d606
Size: 21.86 kB - postgres-decoderbufs-debugsource-3.3.1-1.Final.module+el9+1199+27d9b1d1.x86_64.rpm
MD5: 79a1b66fb165b3ddda8f3f7ea5c98b7b
SHA-256: cb305679b82f81fbcb408d9ef2da1f811ef2efdaace93e7b882ac8706974f2f1
Size: 16.58 kB - postgresql-18.6-1.module+el9+1199+27d9b1d1.x86_64.rpm
MD5: 0bf7570717b1a29d3b4e9a5e60bacaf4
SHA-256: d7ac80d5e782490c3d8348b0b66b0fa0d5be4852cc898b3a3890493d44a60bae
Size: 2.06 MB - postgresql-contrib-18.6-1.module+el9+1199+27d9b1d1.x86_64.rpm
MD5: df1fadcff29a3dddce3b1edf3ea1ee97
SHA-256: 7deff1111179417db503bf691a4b9c27f176afacd65e316ec68ca0c474885ef1
Size: 1.09 MB - postgresql-debugsource-18.6-1.module+el9+1199+27d9b1d1.x86_64.rpm
MD5: 539f3376f28e5434c5381597f5b135f3
SHA-256: e0dd33a83d4634e6c9e87da77bd1f9d099d990ec8137652ddd90d621c7f8ca7e
Size: 17.99 MB - postgresql-docs-18.6-1.module+el9+1199+27d9b1d1.x86_64.rpm
MD5: b1cd3fdde25d4ae663009cca384ec666
SHA-256: 5fc7d062b072f9298b665269e0435780e785c21490d4b25114b657e015bfac84
Size: 2.43 MB - postgresql-plperl-18.6-1.module+el9+1199+27d9b1d1.x86_64.rpm
MD5: 110597d10b5da16e4faaf63e1c136a53
SHA-256: f9955a3a8a39ffce813ef0c58820819bfcd616b859d310f06d690c4c38c09a87
Size: 79.85 kB - postgresql-plpython3-18.6-1.module+el9+1199+27d9b1d1.x86_64.rpm
MD5: b39b9c96a22ae3663283f1fd89a0294f
SHA-256: 41aa33b07dde7719dcfcc718820f134f90a99b679a80e48e3e2d5027092fdcb8
Size: 101.71 kB - postgresql-pltcl-18.6-1.module+el9+1199+27d9b1d1.x86_64.rpm
MD5: 3159e75d90713ba8e85b686577db9921
SHA-256: 497ecd9ec5bdaa6717d4dcb4d1be3cb7e4b31e28f959888ba4e03c9db770e3cc
Size: 53.56 kB - postgresql-private-devel-18.6-1.module+el9+1199+27d9b1d1.x86_64.rpm
MD5: 70184af56736b79aecd70508d1f9fdd0
SHA-256: 2bd373a240d3601ea75961df51e1e3f93ab436de39edede3702da06b33fe3d21
Size: 68.32 kB - postgresql-private-libs-18.6-1.module+el9+1199+27d9b1d1.x86_64.rpm
MD5: f4ecc5c6c23affd910ef4411655d3f55
SHA-256: eb266f1e0473805ab3bca504722ed9ac121864f65db38c32aad45a80db66faf3
Size: 157.91 kB - postgresql-server-18.6-1.module+el9+1199+27d9b1d1.x86_64.rpm
MD5: ac72bd88490afbc2054f89e75f6e39f9
SHA-256: cb3b312190aeed26820ece975face9811f7348cd880b9f754a6565e147eb64f0
Size: 7.54 MB - postgresql-server-devel-18.6-1.module+el9+1199+27d9b1d1.x86_64.rpm
MD5: 66f5fa8d08e0cfc2ac9f7871847325a5
SHA-256: c1e2b004c644b80539f74b78648cd9b8f0ae6d8a7785f0d8da3933d178c95d99
Size: 1.63 MB - postgresql-static-18.6-1.module+el9+1199+27d9b1d1.x86_64.rpm
MD5: 3ce1b9193987598e8b457c9ef263af0f
SHA-256: 92f1b5e1693b6e33711bdbe931e7bae4e93c51a35b15fa5a94f5cb5c78737909
Size: 188.43 kB - postgresql-test-18.6-1.module+el9+1199+27d9b1d1.x86_64.rpm
MD5: 9ebb22000ea327eb2d3140bfb724f126
SHA-256: 501137bf88b503d4ca134e6646fd8c7ae0d64546fbb333d2b4ae4b7b29e25fd7
Size: 2.01 MB - postgresql-test-rpm-macros-18.6-1.module+el9+1199+27d9b1d1.noarch.rpm
MD5: bdf4804533646022336d7b38a09479f9
SHA-256: a3386637c7de7ae9aae8d6981fce0436958b1ae6baaa0c76fd0d1d1a27aed280
Size: 9.31 kB - postgresql-upgrade-18.6-1.module+el9+1199+27d9b1d1.x86_64.rpm
MD5: b70caaa0771edda22c7c0558793cc68c
SHA-256: 2470bd07257aafa1e3be25489a6f51fb9c6934c297333ca483a22269298ec18c
Size: 5.33 MB - postgresql-upgrade-devel-18.6-1.module+el9+1199+27d9b1d1.x86_64.rpm
MD5: bc7788194b81bdc1a770e825f4f9a05b
SHA-256: 7802e53bb50a1243da2881a935be538fbe2493db386bbb524ae1c60ab0b9873f
Size: 1.41 MB