<?xml version="1.0" encoding="UTF-8"?>
<otherdata xmlns="http://linux.duke.edu/metadata/other" packages="301">
<package pkgid="d13edde8f2a73aee44ca335f007ec650fa22b720561bca433efe63fbcf19a8ce94e0681764579ec2a137743daffb7cab44b3023026b18fd5b147f675f091f232" name="libecpg6" arch="s390x">
  <version epoch="0" ver="18.3" rel="2.3"/>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="JS &lt;obs.coke518@passinbox.com&gt;" date="1738152000">- Apply postgresql-tzdata2025a.patch regardless of
  whether LLVM JIT is enabled</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 17.3:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/17.3/
  * https://www.postgresql.org/about/news/-3015/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 17.4:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/17.4/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 17.5:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/17.5/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to Fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1746792001">- Fork package for postgresql 18
  https://www.postgresql.org/about/news/p-3070/</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1753272000">- Update to 18~beta2
  https://www.postgresql.org/about/news/p-3103/</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Update to 18~beta3
  * https://www.postgresql.org/about/news/p-3118/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755518400">- enable liburing and libnuma support
- prepare oauth support. but it creates broken symlinks at the
  moment</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755518401">- In the symlinking loop for *.so files only handle symlinks and
  not also files.
  This allows us to enable oauth support</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755604800">- move libpq-oauth into the libpq5  package. it is a plugin that
  will be loaded via dlopen() if libpq encounters an oauth workflow
  during a connection.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1756987200">- Update to 18 RC1.
  * https://www.postgresql.org/about/news/p-3130/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1758628800">- Update to 18.0.
  * https://www.postgresql.org/about/news/p-3142/
  * https://www.postgresql.org/docs/18/release-18.html</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1758801600">- pg_config --libs returns -lnuma so we need to require it.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Update to 18.1:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/18.1/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 18.2:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/18.2/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * bsc#1258012, CVE-2026-2007: Harden contrib/pg_trgm against
    changes in string lowercasing behavior.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 18.3 to fix two regressions in 18.2:
  * https://www.postgresql.org/docs/release/18.3/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
</package>
<package pkgid="892a87afcd9183c1b3987658661b7e5c78b304c4ef1e23c72e5f456935a17d29a5b7e4b2e73113766eefcb91e523249beb09ffd936d8c21ca13a5edc4bf8690b" name="libecpg6" arch="aarch64">
  <version epoch="0" ver="18.3" rel="3.1"/>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="JS &lt;obs.coke518@passinbox.com&gt;" date="1738152000">- Apply postgresql-tzdata2025a.patch regardless of
  whether LLVM JIT is enabled</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 17.3:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/17.3/
  * https://www.postgresql.org/about/news/-3015/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 17.4:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/17.4/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 17.5:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/17.5/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to Fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1746792001">- Fork package for postgresql 18
  https://www.postgresql.org/about/news/p-3070/</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1753272000">- Update to 18~beta2
  https://www.postgresql.org/about/news/p-3103/</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Update to 18~beta3
  * https://www.postgresql.org/about/news/p-3118/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755518400">- enable liburing and libnuma support
- prepare oauth support. but it creates broken symlinks at the
  moment</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755518401">- In the symlinking loop for *.so files only handle symlinks and
  not also files.
  This allows us to enable oauth support</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755604800">- move libpq-oauth into the libpq5  package. it is a plugin that
  will be loaded via dlopen() if libpq encounters an oauth workflow
  during a connection.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1756987200">- Update to 18 RC1.
  * https://www.postgresql.org/about/news/p-3130/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1758628800">- Update to 18.0.
  * https://www.postgresql.org/about/news/p-3142/
  * https://www.postgresql.org/docs/18/release-18.html</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1758801600">- pg_config --libs returns -lnuma so we need to require it.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Update to 18.1:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/18.1/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 18.2:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/18.2/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * bsc#1258012, CVE-2026-2007: Harden contrib/pg_trgm against
    changes in string lowercasing behavior.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 18.3 to fix two regressions in 18.2:
  * https://www.postgresql.org/docs/release/18.3/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
</package>
<package pkgid="9f61c6ab5a15924aa47ab21267f3ac65fcf0ade894f70e62b8ef80742e47e32d1a552005633a3768b760e0b8e425b677fd1ea18ee07c4ad84dd55134ab937ee7" name="libecpg6" arch="ppc64le">
  <version epoch="0" ver="18.3" rel="3.1"/>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="JS &lt;obs.coke518@passinbox.com&gt;" date="1738152000">- Apply postgresql-tzdata2025a.patch regardless of
  whether LLVM JIT is enabled</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 17.3:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/17.3/
  * https://www.postgresql.org/about/news/-3015/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 17.4:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/17.4/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 17.5:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/17.5/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to Fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1746792001">- Fork package for postgresql 18
  https://www.postgresql.org/about/news/p-3070/</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1753272000">- Update to 18~beta2
  https://www.postgresql.org/about/news/p-3103/</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Update to 18~beta3
  * https://www.postgresql.org/about/news/p-3118/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755518400">- enable liburing and libnuma support
- prepare oauth support. but it creates broken symlinks at the
  moment</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755518401">- In the symlinking loop for *.so files only handle symlinks and
  not also files.
  This allows us to enable oauth support</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755604800">- move libpq-oauth into the libpq5  package. it is a plugin that
  will be loaded via dlopen() if libpq encounters an oauth workflow
  during a connection.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1756987200">- Update to 18 RC1.
  * https://www.postgresql.org/about/news/p-3130/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1758628800">- Update to 18.0.
  * https://www.postgresql.org/about/news/p-3142/
  * https://www.postgresql.org/docs/18/release-18.html</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1758801600">- pg_config --libs returns -lnuma so we need to require it.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Update to 18.1:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/18.1/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 18.2:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/18.2/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * bsc#1258012, CVE-2026-2007: Harden contrib/pg_trgm against
    changes in string lowercasing behavior.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 18.3 to fix two regressions in 18.2:
  * https://www.postgresql.org/docs/release/18.3/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
</package>
<package pkgid="89544c1551a4abf584959dabbe294b14b70cc97ad60f206d971710ebd063d08cfe7c6fb88152f4b252b189d3152901bb7f105e744211112f1acba85705dd3ee9" name="libecpg6" arch="x86_64">
  <version epoch="0" ver="18.4" rel="18.3"/>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 17.4:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/17.4/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 17.5:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/17.5/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to Fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1746792001">- Fork package for postgresql 18
  https://www.postgresql.org/about/news/p-3070/</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1753272000">- Update to 18~beta2
  https://www.postgresql.org/about/news/p-3103/</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Update to 18~beta3
  * https://www.postgresql.org/about/news/p-3118/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755518400">- enable liburing and libnuma support
- prepare oauth support. but it creates broken symlinks at the
  moment</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755518401">- In the symlinking loop for *.so files only handle symlinks and
  not also files.
  This allows us to enable oauth support</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755604800">- move libpq-oauth into the libpq5  package. it is a plugin that
  will be loaded via dlopen() if libpq encounters an oauth workflow
  during a connection.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1756987200">- Update to 18 RC1.
  * https://www.postgresql.org/about/news/p-3130/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1758628800">- Update to 18.0.
  * https://www.postgresql.org/about/news/p-3142/
  * https://www.postgresql.org/docs/18/release-18.html</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1758801600">- pg_config --libs returns -lnuma so we need to require it.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Update to 18.1:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/18.1/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 18.2:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/18.2/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * bsc#1258012, CVE-2026-2007: Harden contrib/pg_trgm against
    changes in string lowercasing behavior.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 18.3 to fix two regressions in 18.2:
  * https://www.postgresql.org/docs/release/18.3/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1774526400">- Get rid of update-alternatives for openSUSE/SLE 16.0 and newer
  to support immutable systems and transactional updates.
  (jsc#PED-14820)</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1777550400">- bsc#1263804: After dropping update-alternatives we have to
  package /usr/bin/pg_config as an actual symlink, not %ghost.
- Fix spelling of build conditionals.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1778673600">- Update to version 18.4:
  * bsc#1265172, CVE-2026-6472: ensure the user has CREATE
    privilege on the schema specified
  * bsc#1265173, CVE-2026-6473: integer overflows in
    memory-allocation calculations
  * bsc#1265174, CVE-2026-6474: Guard against malicious time zone
    names
  * bsc#1265175, CVE-2026-6475: Prevent path traversal in
    pg_basebackup and pg_rewind
  * bsc#1265176, CVE-2026-6476: Properly quote subscription names
    in pg_createsubscriber
  * bsc#1265177, CVE-2026-6477: Mark PQfn() as unsafe, and avoid
    using it within libpq
  * bsc#1265178, CVE-2026-6478: Use timing-safe string comparisons
    in authentication code
  * bsc#1265179, CVE-2026-6479: Prevent unbounded recursion while
    processing startup packets
  * bsc#1265180, CVE-2026-6575: Detect faulty input when restoring
    attribute MCV statistics
  * bsc#1265181, CVE-2026-6637: Prevent SQL injection and buffer
    overruns in contrib/spi
  * bsc#1265182, CVE-2026-6638: Properly quote object names in
    logical replication origin checks
  * https://www.postgresql.org/docs/release/18.4/</changelog>
</package>
<package pkgid="e1dbd99a4aa371dfcda911fc0b4d5fa6e5c28208cd103960f110dd92dd1a8a2607c3a5d28aba532dbf29905e3d35df7bd1f77cb2d7925d63f89eb0d218f1c4b7" name="libpq5" arch="s390x">
  <version epoch="0" ver="18.3" rel="2.3"/>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="JS &lt;obs.coke518@passinbox.com&gt;" date="1738152000">- Apply postgresql-tzdata2025a.patch regardless of
  whether LLVM JIT is enabled</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 17.3:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/17.3/
  * https://www.postgresql.org/about/news/-3015/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 17.4:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/17.4/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 17.5:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/17.5/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to Fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1746792001">- Fork package for postgresql 18
  https://www.postgresql.org/about/news/p-3070/</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1753272000">- Update to 18~beta2
  https://www.postgresql.org/about/news/p-3103/</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Update to 18~beta3
  * https://www.postgresql.org/about/news/p-3118/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755518400">- enable liburing and libnuma support
- prepare oauth support. but it creates broken symlinks at the
  moment</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755518401">- In the symlinking loop for *.so files only handle symlinks and
  not also files.
  This allows us to enable oauth support</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755604800">- move libpq-oauth into the libpq5  package. it is a plugin that
  will be loaded via dlopen() if libpq encounters an oauth workflow
  during a connection.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1756987200">- Update to 18 RC1.
  * https://www.postgresql.org/about/news/p-3130/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1758628800">- Update to 18.0.
  * https://www.postgresql.org/about/news/p-3142/
  * https://www.postgresql.org/docs/18/release-18.html</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1758801600">- pg_config --libs returns -lnuma so we need to require it.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Update to 18.1:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/18.1/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 18.2:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/18.2/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * bsc#1258012, CVE-2026-2007: Harden contrib/pg_trgm against
    changes in string lowercasing behavior.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 18.3 to fix two regressions in 18.2:
  * https://www.postgresql.org/docs/release/18.3/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
</package>
<package pkgid="afe93645c3a09e66a433e568356c7d57d7ba4f581b64a02161d61d788397f8e6a321436c9b507ee0937d94a923b8f338c4e984f9295a46c9f4227832b4717c67" name="libpq5" arch="aarch64">
  <version epoch="0" ver="18.3" rel="3.1"/>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="JS &lt;obs.coke518@passinbox.com&gt;" date="1738152000">- Apply postgresql-tzdata2025a.patch regardless of
  whether LLVM JIT is enabled</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 17.3:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/17.3/
  * https://www.postgresql.org/about/news/-3015/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 17.4:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/17.4/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 17.5:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/17.5/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to Fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1746792001">- Fork package for postgresql 18
  https://www.postgresql.org/about/news/p-3070/</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1753272000">- Update to 18~beta2
  https://www.postgresql.org/about/news/p-3103/</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Update to 18~beta3
  * https://www.postgresql.org/about/news/p-3118/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755518400">- enable liburing and libnuma support
- prepare oauth support. but it creates broken symlinks at the
  moment</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755518401">- In the symlinking loop for *.so files only handle symlinks and
  not also files.
  This allows us to enable oauth support</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755604800">- move libpq-oauth into the libpq5  package. it is a plugin that
  will be loaded via dlopen() if libpq encounters an oauth workflow
  during a connection.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1756987200">- Update to 18 RC1.
  * https://www.postgresql.org/about/news/p-3130/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1758628800">- Update to 18.0.
  * https://www.postgresql.org/about/news/p-3142/
  * https://www.postgresql.org/docs/18/release-18.html</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1758801600">- pg_config --libs returns -lnuma so we need to require it.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Update to 18.1:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/18.1/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 18.2:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/18.2/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * bsc#1258012, CVE-2026-2007: Harden contrib/pg_trgm against
    changes in string lowercasing behavior.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 18.3 to fix two regressions in 18.2:
  * https://www.postgresql.org/docs/release/18.3/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
</package>
<package pkgid="43a13321c7ee0aadede176476e36813642d8b7ea2b954a7eb91f66496fb8c5561360e53c53ee78d8d42f8c6dd0d9ed857e81f783fa5874698d70bfff18b95fff" name="libpq5" arch="ppc64le">
  <version epoch="0" ver="18.3" rel="3.1"/>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="JS &lt;obs.coke518@passinbox.com&gt;" date="1738152000">- Apply postgresql-tzdata2025a.patch regardless of
  whether LLVM JIT is enabled</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 17.3:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/17.3/
  * https://www.postgresql.org/about/news/-3015/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 17.4:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/17.4/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 17.5:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/17.5/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to Fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1746792001">- Fork package for postgresql 18
  https://www.postgresql.org/about/news/p-3070/</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1753272000">- Update to 18~beta2
  https://www.postgresql.org/about/news/p-3103/</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Update to 18~beta3
  * https://www.postgresql.org/about/news/p-3118/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755518400">- enable liburing and libnuma support
- prepare oauth support. but it creates broken symlinks at the
  moment</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755518401">- In the symlinking loop for *.so files only handle symlinks and
  not also files.
  This allows us to enable oauth support</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755604800">- move libpq-oauth into the libpq5  package. it is a plugin that
  will be loaded via dlopen() if libpq encounters an oauth workflow
  during a connection.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1756987200">- Update to 18 RC1.
  * https://www.postgresql.org/about/news/p-3130/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1758628800">- Update to 18.0.
  * https://www.postgresql.org/about/news/p-3142/
  * https://www.postgresql.org/docs/18/release-18.html</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1758801600">- pg_config --libs returns -lnuma so we need to require it.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Update to 18.1:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/18.1/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 18.2:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/18.2/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * bsc#1258012, CVE-2026-2007: Harden contrib/pg_trgm against
    changes in string lowercasing behavior.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 18.3 to fix two regressions in 18.2:
  * https://www.postgresql.org/docs/release/18.3/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
</package>
<package pkgid="cbb0ea083c0bd9cf0e8582335adbb57a94b47ea15de332d9a4aa0a0cec1778f240948f99199c62132bfb49a808cdb82c5e4f791587c3196f59dd26663225d42c" name="libpq5" arch="x86_64">
  <version epoch="0" ver="18.4" rel="18.3"/>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 17.4:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/17.4/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 17.5:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/17.5/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to Fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1746792001">- Fork package for postgresql 18
  https://www.postgresql.org/about/news/p-3070/</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1753272000">- Update to 18~beta2
  https://www.postgresql.org/about/news/p-3103/</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Update to 18~beta3
  * https://www.postgresql.org/about/news/p-3118/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755518400">- enable liburing and libnuma support
- prepare oauth support. but it creates broken symlinks at the
  moment</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755518401">- In the symlinking loop for *.so files only handle symlinks and
  not also files.
  This allows us to enable oauth support</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755604800">- move libpq-oauth into the libpq5  package. it is a plugin that
  will be loaded via dlopen() if libpq encounters an oauth workflow
  during a connection.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1756987200">- Update to 18 RC1.
  * https://www.postgresql.org/about/news/p-3130/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1758628800">- Update to 18.0.
  * https://www.postgresql.org/about/news/p-3142/
  * https://www.postgresql.org/docs/18/release-18.html</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1758801600">- pg_config --libs returns -lnuma so we need to require it.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Update to 18.1:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/18.1/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 18.2:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/18.2/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * bsc#1258012, CVE-2026-2007: Harden contrib/pg_trgm against
    changes in string lowercasing behavior.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 18.3 to fix two regressions in 18.2:
  * https://www.postgresql.org/docs/release/18.3/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1774526400">- Get rid of update-alternatives for openSUSE/SLE 16.0 and newer
  to support immutable systems and transactional updates.
  (jsc#PED-14820)</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1777550400">- bsc#1263804: After dropping update-alternatives we have to
  package /usr/bin/pg_config as an actual symlink, not %ghost.
- Fix spelling of build conditionals.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1778673600">- Update to version 18.4:
  * bsc#1265172, CVE-2026-6472: ensure the user has CREATE
    privilege on the schema specified
  * bsc#1265173, CVE-2026-6473: integer overflows in
    memory-allocation calculations
  * bsc#1265174, CVE-2026-6474: Guard against malicious time zone
    names
  * bsc#1265175, CVE-2026-6475: Prevent path traversal in
    pg_basebackup and pg_rewind
  * bsc#1265176, CVE-2026-6476: Properly quote subscription names
    in pg_createsubscriber
  * bsc#1265177, CVE-2026-6477: Mark PQfn() as unsafe, and avoid
    using it within libpq
  * bsc#1265178, CVE-2026-6478: Use timing-safe string comparisons
    in authentication code
  * bsc#1265179, CVE-2026-6479: Prevent unbounded recursion while
    processing startup packets
  * bsc#1265180, CVE-2026-6575: Detect faulty input when restoring
    attribute MCV statistics
  * bsc#1265181, CVE-2026-6637: Prevent SQL injection and buffer
    overruns in contrib/spi
  * bsc#1265182, CVE-2026-6638: Properly quote object names in
    logical replication origin checks
  * https://www.postgresql.org/docs/release/18.4/</changelog>
</package>
<package pkgid="ad6b6a4ac435f50a762c346f17afac3e36db2ddb6e5d0787090c3ba4a5ecbc58e6a1b0ef7e1d1219a52e7a6a0fa0cd822da849d5038a2960d1f5703f60a40767" name="postgresql" arch="noarch">
  <version epoch="0" ver="18" rel="24.3"/>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1673265600">- bsc#1206796: Refine the distinction of where to use sysusers and
  use bcond to have the expression only in one place.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1679918400">- bsc#1209208: Drop hard dependency on systemd</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1684152000">- Overhaul postgresql-README.SUSE and move it from the binary
  package to the noarch wrapper package.
- bsc#1179231: Add an explanation for the /tmp -&gt; /run/postgresql
  move and permission change.
- Add postgresql-README as a separate source file.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1684843200">- boo#1122892: Add a sysconfig variable for initdb.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1691409600">- Bump major version to prepare for PostgreSQL 16, but keep
  default at 15 for now on Factory.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1694692800">- Bump default to 16 on Factory.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1697198400">- Interlock version and release of all noarch packages except for
  the postgresql-docs.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1707393600">- bsc#1219340: Require fillup.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1709035200">- bsc#1219340: The last fix was not correct. Improve it by removing
  the dependency again and call fillup only if it is installed.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1726142400">- bsc#1230423: Relax the dependency of extensions on the server
  version from exact major.minor to greater or equal, after Tom
  Lane confirmed on the PostgreSQL packagers list that ABI
  stability is being taken care of between minor releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1726747200">- Bump major and default to 17 for Factory and TW.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1731499200">- Bump major to 17 for SLE.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1733918400">- Bump default to 17 for SLE-15-SP7.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1746792000">- Bump major and default to 18 for Factory and TW.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1764331200">- Bump major to 18 on SLE.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1775822400">- Get rid of update-alternatives and support immutable mode.
  See README.SUSE for details. (bsc#1245862, jsc#PED-14820)
- Merge the spec files from different products and use the product
  versions to decide about the default PostgreSQL version.</changelog>
</package>
<package pkgid="f5d347b2f53bad13357ad7257b82d295fa4ee4018b22ed305c4cc0e9a8873d1dc6a3079bf78ee778db759cb54faa5fa0e2a62021c1bf9954f21f03aa7b9ad6f6" name="postgresql" arch="src">
  <version epoch="0" ver="18" rel="24.3"/>
  <changelog author="Callum Farmer &lt;gmbr3@opensuse.org&gt;" date="1647432000">- Change to systemd-sysusers</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1653134400">- Bump to postgresql 15</changelog>
  <changelog author="Dirk M&#xFC;ller &lt;dmueller@suse.com&gt;" date="1662379200">- avoid bashisms in /bin/sh based startup script</changelog>
  <changelog author="Andreas Schwab &lt;schwab@suse.de&gt;" date="1663848000">- riscv64 does not have llvm support yet,
  adapt the %postgresql_has_llvm macro accordingly.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1673265600">- bsc#1206796: Refine the distinction of where to use sysusers and
  use bcond to have the expression only in one place.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1679918400">- bsc#1209208: Drop hard dependency on systemd</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1684152000">- Overhaul postgresql-README.SUSE and move it from the binary
  package to the noarch wrapper package.
- bsc#1179231: Add an explanation for the /tmp -&gt; /run/postgresql
  move and permission change.
- Add postgresql-README as a separate source file.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1684843200">- boo#1122892: Add a sysconfig variable for initdb.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1691409600">- Bump major version to prepare for PostgreSQL 16, but keep
  default at 15 for now on Factory.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1694692800">- Bump default to 16 on Factory.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1697198400">- Interlock version and release of all noarch packages except for
  the postgresql-docs.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1707393600">- bsc#1219340: Require fillup.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1709035200">- bsc#1219340: The last fix was not correct. Improve it by removing
  the dependency again and call fillup only if it is installed.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1726142400">- bsc#1230423: Relax the dependency of extensions on the server
  version from exact major.minor to greater or equal, after Tom
  Lane confirmed on the PostgreSQL packagers list that ABI
  stability is being taken care of between minor releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1726747200">- Bump major and default to 17 for Factory and TW.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1731499200">- Bump major to 17 for SLE.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1733918400">- Bump default to 17 for SLE-15-SP7.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1746792000">- Bump major and default to 18 for Factory and TW.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1764331200">- Bump major to 18 on SLE.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1775822400">- Get rid of update-alternatives and support immutable mode.
  See README.SUSE for details. (bsc#1245862, jsc#PED-14820)
- Merge the spec files from different products and use the product
  versions to decide about the default PostgreSQL version.</changelog>
</package>
<package pkgid="dcd1093001fed05eb355c2334d7e7717fe2b1df8f61b44e09d7a15f59a9158afb4faf3e8316f2947c467ec40d4779fe6e4ff8b6621638cae6957900ce58782d2" name="postgresql" arch="noarch">
  <version epoch="0" ver="18" rel="8.1"/>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1643371200">- Avoid a dependency on awk in postgresql-script.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1644494400">- Fix the pg_server_requires macro on older rpm versions (SLE-12).</changelog>
  <changelog author="Callum Farmer &lt;gmbr3@opensuse.org&gt;" date="1647432000">- Change to systemd-sysusers</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1653134400">- Bump to postgresql 15</changelog>
  <changelog author="Dirk M&#xFC;ller &lt;dmueller@suse.com&gt;" date="1662379200">- avoid bashisms in /bin/sh based startup script</changelog>
  <changelog author="Andreas Schwab &lt;schwab@suse.de&gt;" date="1663848000">- riscv64 does not have llvm support yet,
  adapt the %postgresql_has_llvm macro accordingly.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1673265600">- bsc#1206796: Refine the distinction of where to use sysusers and
  use bcond to have the expression only in one place.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1679918400">- bsc#1209208: Drop hard dependency on systemd</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1684152000">- Overhaul postgresql-README.SUSE and move it from the binary
  package to the noarch wrapper package.
- bsc#1179231: Add an explanation for the /tmp -&gt; /run/postgresql
  move and permission change.
- Add postgresql-README as a separate source file.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1684843200">- boo#1122892: Add a sysconfig variable for initdb.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1691409600">- Bump major version to prepare for PostgreSQL 16, but keep
  default at 15 for now on Factory.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1694692800">- Bump default to 16 on Factory.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1697198400">- Interlock version and release of all noarch packages except for
  the postgresql-docs.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1707393600">- bsc#1219340: Require fillup.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1709035200">- bsc#1219340: The last fix was not correct. Improve it by removing
  the dependency again and call fillup only if it is installed.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1726142400">- bsc#1230423: Relax the dependency of extensions on the server
  version from exact major.minor to greater or equal, after Tom
  Lane confirmed on the PostgreSQL packagers list that ABI
  stability is being taken care of between minor releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1726747200">- Bump major and default to 17 for Factory and TW.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1731499200">- Bump major to 17 for SLE.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1733918400">- Bump default to 17 for SLE-15-SP7.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1746792000">- Bump major and default to 18 for Factory and TW.</changelog>
</package>
<package pkgid="dd0a1d15c8d0a2fc991c5d7f3e6b2946594cea388e37c0dc3c05372d0337c31c4ec837a5d71d8bf1ac147262fb7fedb156821e4639c534e1c29783006585fb14" name="postgresql" arch="src">
  <version epoch="0" ver="18" rel="8.1"/>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1643371200">- Avoid a dependency on awk in postgresql-script.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1644494400">- Fix the pg_server_requires macro on older rpm versions (SLE-12).</changelog>
  <changelog author="Callum Farmer &lt;gmbr3@opensuse.org&gt;" date="1647432000">- Change to systemd-sysusers</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1653134400">- Bump to postgresql 15</changelog>
  <changelog author="Dirk M&#xFC;ller &lt;dmueller@suse.com&gt;" date="1662379200">- avoid bashisms in /bin/sh based startup script</changelog>
  <changelog author="Andreas Schwab &lt;schwab@suse.de&gt;" date="1663848000">- riscv64 does not have llvm support yet,
  adapt the %postgresql_has_llvm macro accordingly.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1673265600">- bsc#1206796: Refine the distinction of where to use sysusers and
  use bcond to have the expression only in one place.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1679918400">- bsc#1209208: Drop hard dependency on systemd</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1684152000">- Overhaul postgresql-README.SUSE and move it from the binary
  package to the noarch wrapper package.
- bsc#1179231: Add an explanation for the /tmp -&gt; /run/postgresql
  move and permission change.
- Add postgresql-README as a separate source file.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1684843200">- boo#1122892: Add a sysconfig variable for initdb.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1691409600">- Bump major version to prepare for PostgreSQL 16, but keep
  default at 15 for now on Factory.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1694692800">- Bump default to 16 on Factory.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1697198400">- Interlock version and release of all noarch packages except for
  the postgresql-docs.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1707393600">- bsc#1219340: Require fillup.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1709035200">- bsc#1219340: The last fix was not correct. Improve it by removing
  the dependency again and call fillup only if it is installed.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1726142400">- bsc#1230423: Relax the dependency of extensions on the server
  version from exact major.minor to greater or equal, after Tom
  Lane confirmed on the PostgreSQL packagers list that ABI
  stability is being taken care of between minor releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1726747200">- Bump major and default to 17 for Factory and TW.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1731499200">- Bump major to 17 for SLE.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1733918400">- Bump default to 17 for SLE-15-SP7.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1746792000">- Bump major and default to 18 for Factory and TW.</changelog>
</package>
<package pkgid="d1d4e1ca6e163565705f098c241ca6e820b9f2be91ef08987b1cdd3bcccfb935add1a34d1abf978cf2bb8cf2df49e628f65008eb7b92023c7205538fa84575a2" name="postgresql-contrib" arch="noarch">
  <version epoch="0" ver="18" rel="24.3"/>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1673265600">- bsc#1206796: Refine the distinction of where to use sysusers and
  use bcond to have the expression only in one place.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1679918400">- bsc#1209208: Drop hard dependency on systemd</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1684152000">- Overhaul postgresql-README.SUSE and move it from the binary
  package to the noarch wrapper package.
- bsc#1179231: Add an explanation for the /tmp -&gt; /run/postgresql
  move and permission change.
- Add postgresql-README as a separate source file.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1684843200">- boo#1122892: Add a sysconfig variable for initdb.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1691409600">- Bump major version to prepare for PostgreSQL 16, but keep
  default at 15 for now on Factory.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1694692800">- Bump default to 16 on Factory.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1697198400">- Interlock version and release of all noarch packages except for
  the postgresql-docs.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1707393600">- bsc#1219340: Require fillup.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1709035200">- bsc#1219340: The last fix was not correct. Improve it by removing
  the dependency again and call fillup only if it is installed.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1726142400">- bsc#1230423: Relax the dependency of extensions on the server
  version from exact major.minor to greater or equal, after Tom
  Lane confirmed on the PostgreSQL packagers list that ABI
  stability is being taken care of between minor releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1726747200">- Bump major and default to 17 for Factory and TW.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1731499200">- Bump major to 17 for SLE.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1733918400">- Bump default to 17 for SLE-15-SP7.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1746792000">- Bump major and default to 18 for Factory and TW.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1764331200">- Bump major to 18 on SLE.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1775822400">- Get rid of update-alternatives and support immutable mode.
  See README.SUSE for details. (bsc#1245862, jsc#PED-14820)
- Merge the spec files from different products and use the product
  versions to decide about the default PostgreSQL version.</changelog>
</package>
<package pkgid="8cd50d4edc3ec52da2948efd0dfa767e378be843aa878ac0c558c706347762b0c251dae693c16eb156f31b585bf2bd29dd2c517930d97909019195845e855afa" name="postgresql-contrib" arch="noarch">
  <version epoch="0" ver="18" rel="8.1"/>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1643371200">- Avoid a dependency on awk in postgresql-script.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1644494400">- Fix the pg_server_requires macro on older rpm versions (SLE-12).</changelog>
  <changelog author="Callum Farmer &lt;gmbr3@opensuse.org&gt;" date="1647432000">- Change to systemd-sysusers</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1653134400">- Bump to postgresql 15</changelog>
  <changelog author="Dirk M&#xFC;ller &lt;dmueller@suse.com&gt;" date="1662379200">- avoid bashisms in /bin/sh based startup script</changelog>
  <changelog author="Andreas Schwab &lt;schwab@suse.de&gt;" date="1663848000">- riscv64 does not have llvm support yet,
  adapt the %postgresql_has_llvm macro accordingly.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1673265600">- bsc#1206796: Refine the distinction of where to use sysusers and
  use bcond to have the expression only in one place.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1679918400">- bsc#1209208: Drop hard dependency on systemd</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1684152000">- Overhaul postgresql-README.SUSE and move it from the binary
  package to the noarch wrapper package.
- bsc#1179231: Add an explanation for the /tmp -&gt; /run/postgresql
  move and permission change.
- Add postgresql-README as a separate source file.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1684843200">- boo#1122892: Add a sysconfig variable for initdb.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1691409600">- Bump major version to prepare for PostgreSQL 16, but keep
  default at 15 for now on Factory.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1694692800">- Bump default to 16 on Factory.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1697198400">- Interlock version and release of all noarch packages except for
  the postgresql-docs.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1707393600">- bsc#1219340: Require fillup.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1709035200">- bsc#1219340: The last fix was not correct. Improve it by removing
  the dependency again and call fillup only if it is installed.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1726142400">- bsc#1230423: Relax the dependency of extensions on the server
  version from exact major.minor to greater or equal, after Tom
  Lane confirmed on the PostgreSQL packagers list that ABI
  stability is being taken care of between minor releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1726747200">- Bump major and default to 17 for Factory and TW.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1731499200">- Bump major to 17 for SLE.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1733918400">- Bump default to 17 for SLE-15-SP7.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1746792000">- Bump major and default to 18 for Factory and TW.</changelog>
</package>
<package pkgid="67e7babc293c9271fd3e152bb9ef0edc75a28fa97fe5e062a5d2f63cde39618cf8910edbe34e826b965101ed1def6ed5d73c46f48444a384c45711550dee606c" name="postgresql-devel" arch="noarch">
  <version epoch="0" ver="18" rel="24.3"/>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1673265600">- bsc#1206796: Refine the distinction of where to use sysusers and
  use bcond to have the expression only in one place.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1679918400">- bsc#1209208: Drop hard dependency on systemd</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1684152000">- Overhaul postgresql-README.SUSE and move it from the binary
  package to the noarch wrapper package.
- bsc#1179231: Add an explanation for the /tmp -&gt; /run/postgresql
  move and permission change.
- Add postgresql-README as a separate source file.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1684843200">- boo#1122892: Add a sysconfig variable for initdb.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1691409600">- Bump major version to prepare for PostgreSQL 16, but keep
  default at 15 for now on Factory.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1694692800">- Bump default to 16 on Factory.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1697198400">- Interlock version and release of all noarch packages except for
  the postgresql-docs.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1707393600">- bsc#1219340: Require fillup.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1709035200">- bsc#1219340: The last fix was not correct. Improve it by removing
  the dependency again and call fillup only if it is installed.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1726142400">- bsc#1230423: Relax the dependency of extensions on the server
  version from exact major.minor to greater or equal, after Tom
  Lane confirmed on the PostgreSQL packagers list that ABI
  stability is being taken care of between minor releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1726747200">- Bump major and default to 17 for Factory and TW.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1731499200">- Bump major to 17 for SLE.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1733918400">- Bump default to 17 for SLE-15-SP7.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1746792000">- Bump major and default to 18 for Factory and TW.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1764331200">- Bump major to 18 on SLE.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1775822400">- Get rid of update-alternatives and support immutable mode.
  See README.SUSE for details. (bsc#1245862, jsc#PED-14820)
- Merge the spec files from different products and use the product
  versions to decide about the default PostgreSQL version.</changelog>
</package>
<package pkgid="61a1f6dd8549f8107f75c64b0dc199c0ea7f55f7eebc0021d2fcf02d8e168a5c4b9425e39ef8d79f2bd200934e70836d608f92d1c07b476b637b0ca60cddf0c5" name="postgresql-devel" arch="noarch">
  <version epoch="0" ver="18" rel="8.1"/>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1643371200">- Avoid a dependency on awk in postgresql-script.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1644494400">- Fix the pg_server_requires macro on older rpm versions (SLE-12).</changelog>
  <changelog author="Callum Farmer &lt;gmbr3@opensuse.org&gt;" date="1647432000">- Change to systemd-sysusers</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1653134400">- Bump to postgresql 15</changelog>
  <changelog author="Dirk M&#xFC;ller &lt;dmueller@suse.com&gt;" date="1662379200">- avoid bashisms in /bin/sh based startup script</changelog>
  <changelog author="Andreas Schwab &lt;schwab@suse.de&gt;" date="1663848000">- riscv64 does not have llvm support yet,
  adapt the %postgresql_has_llvm macro accordingly.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1673265600">- bsc#1206796: Refine the distinction of where to use sysusers and
  use bcond to have the expression only in one place.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1679918400">- bsc#1209208: Drop hard dependency on systemd</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1684152000">- Overhaul postgresql-README.SUSE and move it from the binary
  package to the noarch wrapper package.
- bsc#1179231: Add an explanation for the /tmp -&gt; /run/postgresql
  move and permission change.
- Add postgresql-README as a separate source file.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1684843200">- boo#1122892: Add a sysconfig variable for initdb.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1691409600">- Bump major version to prepare for PostgreSQL 16, but keep
  default at 15 for now on Factory.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1694692800">- Bump default to 16 on Factory.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1697198400">- Interlock version and release of all noarch packages except for
  the postgresql-docs.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1707393600">- bsc#1219340: Require fillup.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1709035200">- bsc#1219340: The last fix was not correct. Improve it by removing
  the dependency again and call fillup only if it is installed.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1726142400">- bsc#1230423: Relax the dependency of extensions on the server
  version from exact major.minor to greater or equal, after Tom
  Lane confirmed on the PostgreSQL packagers list that ABI
  stability is being taken care of between minor releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1726747200">- Bump major and default to 17 for Factory and TW.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1731499200">- Bump major to 17 for SLE.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1733918400">- Bump default to 17 for SLE-15-SP7.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1746792000">- Bump major and default to 18 for Factory and TW.</changelog>
</package>
<package pkgid="5089e384ef3e8c7f77206498175956e336389629e27899857e0d3de5c7cfc088862bd01a2898d647631be2380c78a983a1c61c546e8d443029fbf03878073ec6" name="postgresql-docs" arch="noarch">
  <version epoch="0" ver="18" rel="24.3"/>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1673265600">- bsc#1206796: Refine the distinction of where to use sysusers and
  use bcond to have the expression only in one place.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1679918400">- bsc#1209208: Drop hard dependency on systemd</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1684152000">- Overhaul postgresql-README.SUSE and move it from the binary
  package to the noarch wrapper package.
- bsc#1179231: Add an explanation for the /tmp -&gt; /run/postgresql
  move and permission change.
- Add postgresql-README as a separate source file.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1684843200">- boo#1122892: Add a sysconfig variable for initdb.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1691409600">- Bump major version to prepare for PostgreSQL 16, but keep
  default at 15 for now on Factory.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1694692800">- Bump default to 16 on Factory.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1697198400">- Interlock version and release of all noarch packages except for
  the postgresql-docs.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1707393600">- bsc#1219340: Require fillup.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1709035200">- bsc#1219340: The last fix was not correct. Improve it by removing
  the dependency again and call fillup only if it is installed.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1726142400">- bsc#1230423: Relax the dependency of extensions on the server
  version from exact major.minor to greater or equal, after Tom
  Lane confirmed on the PostgreSQL packagers list that ABI
  stability is being taken care of between minor releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1726747200">- Bump major and default to 17 for Factory and TW.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1731499200">- Bump major to 17 for SLE.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1733918400">- Bump default to 17 for SLE-15-SP7.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1746792000">- Bump major and default to 18 for Factory and TW.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1764331200">- Bump major to 18 on SLE.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1775822400">- Get rid of update-alternatives and support immutable mode.
  See README.SUSE for details. (bsc#1245862, jsc#PED-14820)
- Merge the spec files from different products and use the product
  versions to decide about the default PostgreSQL version.</changelog>
</package>
<package pkgid="36a26b673ad79ed35007be2c54703ddbe974fd15f450390cc641eced63065c63eab8ea4d73f1985fb4a7c6c70d6074b215222eee3240d3baf0f2ca7323756bdf" name="postgresql-docs" arch="noarch">
  <version epoch="0" ver="18" rel="8.1"/>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1643371200">- Avoid a dependency on awk in postgresql-script.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1644494400">- Fix the pg_server_requires macro on older rpm versions (SLE-12).</changelog>
  <changelog author="Callum Farmer &lt;gmbr3@opensuse.org&gt;" date="1647432000">- Change to systemd-sysusers</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1653134400">- Bump to postgresql 15</changelog>
  <changelog author="Dirk M&#xFC;ller &lt;dmueller@suse.com&gt;" date="1662379200">- avoid bashisms in /bin/sh based startup script</changelog>
  <changelog author="Andreas Schwab &lt;schwab@suse.de&gt;" date="1663848000">- riscv64 does not have llvm support yet,
  adapt the %postgresql_has_llvm macro accordingly.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1673265600">- bsc#1206796: Refine the distinction of where to use sysusers and
  use bcond to have the expression only in one place.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1679918400">- bsc#1209208: Drop hard dependency on systemd</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1684152000">- Overhaul postgresql-README.SUSE and move it from the binary
  package to the noarch wrapper package.
- bsc#1179231: Add an explanation for the /tmp -&gt; /run/postgresql
  move and permission change.
- Add postgresql-README as a separate source file.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1684843200">- boo#1122892: Add a sysconfig variable for initdb.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1691409600">- Bump major version to prepare for PostgreSQL 16, but keep
  default at 15 for now on Factory.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1694692800">- Bump default to 16 on Factory.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1697198400">- Interlock version and release of all noarch packages except for
  the postgresql-docs.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1707393600">- bsc#1219340: Require fillup.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1709035200">- bsc#1219340: The last fix was not correct. Improve it by removing
  the dependency again and call fillup only if it is installed.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1726142400">- bsc#1230423: Relax the dependency of extensions on the server
  version from exact major.minor to greater or equal, after Tom
  Lane confirmed on the PostgreSQL packagers list that ABI
  stability is being taken care of between minor releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1726747200">- Bump major and default to 17 for Factory and TW.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1731499200">- Bump major to 17 for SLE.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1733918400">- Bump default to 17 for SLE-15-SP7.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1746792000">- Bump major and default to 18 for Factory and TW.</changelog>
</package>
<package pkgid="64d625b055290074707bcf7930ee97c0779c215c6f7730e32de22d3ad8614dbb946a6620b77e187e8c771ed1408f7377160895e2a0c9c4cf4f8c0a1023b1dfac" name="postgresql-llvmjit" arch="noarch">
  <version epoch="0" ver="18" rel="24.3"/>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1673265600">- bsc#1206796: Refine the distinction of where to use sysusers and
  use bcond to have the expression only in one place.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1679918400">- bsc#1209208: Drop hard dependency on systemd</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1684152000">- Overhaul postgresql-README.SUSE and move it from the binary
  package to the noarch wrapper package.
- bsc#1179231: Add an explanation for the /tmp -&gt; /run/postgresql
  move and permission change.
- Add postgresql-README as a separate source file.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1684843200">- boo#1122892: Add a sysconfig variable for initdb.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1691409600">- Bump major version to prepare for PostgreSQL 16, but keep
  default at 15 for now on Factory.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1694692800">- Bump default to 16 on Factory.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1697198400">- Interlock version and release of all noarch packages except for
  the postgresql-docs.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1707393600">- bsc#1219340: Require fillup.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1709035200">- bsc#1219340: The last fix was not correct. Improve it by removing
  the dependency again and call fillup only if it is installed.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1726142400">- bsc#1230423: Relax the dependency of extensions on the server
  version from exact major.minor to greater or equal, after Tom
  Lane confirmed on the PostgreSQL packagers list that ABI
  stability is being taken care of between minor releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1726747200">- Bump major and default to 17 for Factory and TW.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1731499200">- Bump major to 17 for SLE.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1733918400">- Bump default to 17 for SLE-15-SP7.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1746792000">- Bump major and default to 18 for Factory and TW.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1764331200">- Bump major to 18 on SLE.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1775822400">- Get rid of update-alternatives and support immutable mode.
  See README.SUSE for details. (bsc#1245862, jsc#PED-14820)
- Merge the spec files from different products and use the product
  versions to decide about the default PostgreSQL version.</changelog>
</package>
<package pkgid="7b364e909f50b4449237a7151f2e44a0d7cff325977ea761d7ece3bf491ac72ef7c12dd865ebd21b89444380b08cbdc6d729bdf5ff1b0088dab12aa1749938d7" name="postgresql-llvmjit" arch="noarch">
  <version epoch="0" ver="18" rel="8.1"/>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1643371200">- Avoid a dependency on awk in postgresql-script.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1644494400">- Fix the pg_server_requires macro on older rpm versions (SLE-12).</changelog>
  <changelog author="Callum Farmer &lt;gmbr3@opensuse.org&gt;" date="1647432000">- Change to systemd-sysusers</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1653134400">- Bump to postgresql 15</changelog>
  <changelog author="Dirk M&#xFC;ller &lt;dmueller@suse.com&gt;" date="1662379200">- avoid bashisms in /bin/sh based startup script</changelog>
  <changelog author="Andreas Schwab &lt;schwab@suse.de&gt;" date="1663848000">- riscv64 does not have llvm support yet,
  adapt the %postgresql_has_llvm macro accordingly.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1673265600">- bsc#1206796: Refine the distinction of where to use sysusers and
  use bcond to have the expression only in one place.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1679918400">- bsc#1209208: Drop hard dependency on systemd</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1684152000">- Overhaul postgresql-README.SUSE and move it from the binary
  package to the noarch wrapper package.
- bsc#1179231: Add an explanation for the /tmp -&gt; /run/postgresql
  move and permission change.
- Add postgresql-README as a separate source file.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1684843200">- boo#1122892: Add a sysconfig variable for initdb.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1691409600">- Bump major version to prepare for PostgreSQL 16, but keep
  default at 15 for now on Factory.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1694692800">- Bump default to 16 on Factory.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1697198400">- Interlock version and release of all noarch packages except for
  the postgresql-docs.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1707393600">- bsc#1219340: Require fillup.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1709035200">- bsc#1219340: The last fix was not correct. Improve it by removing
  the dependency again and call fillup only if it is installed.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1726142400">- bsc#1230423: Relax the dependency of extensions on the server
  version from exact major.minor to greater or equal, after Tom
  Lane confirmed on the PostgreSQL packagers list that ABI
  stability is being taken care of between minor releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1726747200">- Bump major and default to 17 for Factory and TW.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1731499200">- Bump major to 17 for SLE.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1733918400">- Bump default to 17 for SLE-15-SP7.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1746792000">- Bump major and default to 18 for Factory and TW.</changelog>
</package>
<package pkgid="1fc60100c9a0bd680c4111c75d827aad96f6c5eea8e73209baebbdfb4606b2bdb03ea203dcfb0c856e1fa900c876aff1915539733f6d1b4273ca4d8c2416373c" name="postgresql-llvmjit-devel" arch="noarch">
  <version epoch="0" ver="18" rel="24.3"/>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1673265600">- bsc#1206796: Refine the distinction of where to use sysusers and
  use bcond to have the expression only in one place.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1679918400">- bsc#1209208: Drop hard dependency on systemd</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1684152000">- Overhaul postgresql-README.SUSE and move it from the binary
  package to the noarch wrapper package.
- bsc#1179231: Add an explanation for the /tmp -&gt; /run/postgresql
  move and permission change.
- Add postgresql-README as a separate source file.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1684843200">- boo#1122892: Add a sysconfig variable for initdb.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1691409600">- Bump major version to prepare for PostgreSQL 16, but keep
  default at 15 for now on Factory.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1694692800">- Bump default to 16 on Factory.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1697198400">- Interlock version and release of all noarch packages except for
  the postgresql-docs.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1707393600">- bsc#1219340: Require fillup.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1709035200">- bsc#1219340: The last fix was not correct. Improve it by removing
  the dependency again and call fillup only if it is installed.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1726142400">- bsc#1230423: Relax the dependency of extensions on the server
  version from exact major.minor to greater or equal, after Tom
  Lane confirmed on the PostgreSQL packagers list that ABI
  stability is being taken care of between minor releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1726747200">- Bump major and default to 17 for Factory and TW.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1731499200">- Bump major to 17 for SLE.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1733918400">- Bump default to 17 for SLE-15-SP7.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1746792000">- Bump major and default to 18 for Factory and TW.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1764331200">- Bump major to 18 on SLE.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1775822400">- Get rid of update-alternatives and support immutable mode.
  See README.SUSE for details. (bsc#1245862, jsc#PED-14820)
- Merge the spec files from different products and use the product
  versions to decide about the default PostgreSQL version.</changelog>
</package>
<package pkgid="73dc32b27f4704775a07d246ac4cd0a462b41d6449fc61e3dffdb36d870a119779aa4bb1deb3dab9e42444998b7772e836ec92e25f8ee7c3584a359947ccb696" name="postgresql-llvmjit-devel" arch="noarch">
  <version epoch="0" ver="18" rel="8.1"/>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1643371200">- Avoid a dependency on awk in postgresql-script.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1644494400">- Fix the pg_server_requires macro on older rpm versions (SLE-12).</changelog>
  <changelog author="Callum Farmer &lt;gmbr3@opensuse.org&gt;" date="1647432000">- Change to systemd-sysusers</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1653134400">- Bump to postgresql 15</changelog>
  <changelog author="Dirk M&#xFC;ller &lt;dmueller@suse.com&gt;" date="1662379200">- avoid bashisms in /bin/sh based startup script</changelog>
  <changelog author="Andreas Schwab &lt;schwab@suse.de&gt;" date="1663848000">- riscv64 does not have llvm support yet,
  adapt the %postgresql_has_llvm macro accordingly.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1673265600">- bsc#1206796: Refine the distinction of where to use sysusers and
  use bcond to have the expression only in one place.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1679918400">- bsc#1209208: Drop hard dependency on systemd</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1684152000">- Overhaul postgresql-README.SUSE and move it from the binary
  package to the noarch wrapper package.
- bsc#1179231: Add an explanation for the /tmp -&gt; /run/postgresql
  move and permission change.
- Add postgresql-README as a separate source file.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1684843200">- boo#1122892: Add a sysconfig variable for initdb.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1691409600">- Bump major version to prepare for PostgreSQL 16, but keep
  default at 15 for now on Factory.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1694692800">- Bump default to 16 on Factory.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1697198400">- Interlock version and release of all noarch packages except for
  the postgresql-docs.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1707393600">- bsc#1219340: Require fillup.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1709035200">- bsc#1219340: The last fix was not correct. Improve it by removing
  the dependency again and call fillup only if it is installed.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1726142400">- bsc#1230423: Relax the dependency of extensions on the server
  version from exact major.minor to greater or equal, after Tom
  Lane confirmed on the PostgreSQL packagers list that ABI
  stability is being taken care of between minor releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1726747200">- Bump major and default to 17 for Factory and TW.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1731499200">- Bump major to 17 for SLE.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1733918400">- Bump default to 17 for SLE-15-SP7.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1746792000">- Bump major and default to 18 for Factory and TW.</changelog>
</package>
<package pkgid="5bb2a52ba9751689548c319c695e6d4facc9c6aa97d2cbfc276281e00ddc63ad644b6e9edfa4f4f934389f5f9ba2f0d64cb5b5b6cd6ca900f5cd79f5b4e0c673" name="postgresql-plperl" arch="noarch">
  <version epoch="0" ver="18" rel="24.3"/>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1673265600">- bsc#1206796: Refine the distinction of where to use sysusers and
  use bcond to have the expression only in one place.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1679918400">- bsc#1209208: Drop hard dependency on systemd</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1684152000">- Overhaul postgresql-README.SUSE and move it from the binary
  package to the noarch wrapper package.
- bsc#1179231: Add an explanation for the /tmp -&gt; /run/postgresql
  move and permission change.
- Add postgresql-README as a separate source file.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1684843200">- boo#1122892: Add a sysconfig variable for initdb.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1691409600">- Bump major version to prepare for PostgreSQL 16, but keep
  default at 15 for now on Factory.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1694692800">- Bump default to 16 on Factory.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1697198400">- Interlock version and release of all noarch packages except for
  the postgresql-docs.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1707393600">- bsc#1219340: Require fillup.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1709035200">- bsc#1219340: The last fix was not correct. Improve it by removing
  the dependency again and call fillup only if it is installed.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1726142400">- bsc#1230423: Relax the dependency of extensions on the server
  version from exact major.minor to greater or equal, after Tom
  Lane confirmed on the PostgreSQL packagers list that ABI
  stability is being taken care of between minor releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1726747200">- Bump major and default to 17 for Factory and TW.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1731499200">- Bump major to 17 for SLE.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1733918400">- Bump default to 17 for SLE-15-SP7.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1746792000">- Bump major and default to 18 for Factory and TW.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1764331200">- Bump major to 18 on SLE.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1775822400">- Get rid of update-alternatives and support immutable mode.
  See README.SUSE for details. (bsc#1245862, jsc#PED-14820)
- Merge the spec files from different products and use the product
  versions to decide about the default PostgreSQL version.</changelog>
</package>
<package pkgid="8e7a170df8b3cac5b65529bc2712d53c96c94a03e89cd534114f89672987ddcd9139ab9b3fa2fc4e4645a022e2e2c7d2d91709147655f739b4dd8c130db8cda4" name="postgresql-plperl" arch="noarch">
  <version epoch="0" ver="18" rel="8.1"/>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1643371200">- Avoid a dependency on awk in postgresql-script.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1644494400">- Fix the pg_server_requires macro on older rpm versions (SLE-12).</changelog>
  <changelog author="Callum Farmer &lt;gmbr3@opensuse.org&gt;" date="1647432000">- Change to systemd-sysusers</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1653134400">- Bump to postgresql 15</changelog>
  <changelog author="Dirk M&#xFC;ller &lt;dmueller@suse.com&gt;" date="1662379200">- avoid bashisms in /bin/sh based startup script</changelog>
  <changelog author="Andreas Schwab &lt;schwab@suse.de&gt;" date="1663848000">- riscv64 does not have llvm support yet,
  adapt the %postgresql_has_llvm macro accordingly.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1673265600">- bsc#1206796: Refine the distinction of where to use sysusers and
  use bcond to have the expression only in one place.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1679918400">- bsc#1209208: Drop hard dependency on systemd</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1684152000">- Overhaul postgresql-README.SUSE and move it from the binary
  package to the noarch wrapper package.
- bsc#1179231: Add an explanation for the /tmp -&gt; /run/postgresql
  move and permission change.
- Add postgresql-README as a separate source file.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1684843200">- boo#1122892: Add a sysconfig variable for initdb.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1691409600">- Bump major version to prepare for PostgreSQL 16, but keep
  default at 15 for now on Factory.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1694692800">- Bump default to 16 on Factory.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1697198400">- Interlock version and release of all noarch packages except for
  the postgresql-docs.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1707393600">- bsc#1219340: Require fillup.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1709035200">- bsc#1219340: The last fix was not correct. Improve it by removing
  the dependency again and call fillup only if it is installed.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1726142400">- bsc#1230423: Relax the dependency of extensions on the server
  version from exact major.minor to greater or equal, after Tom
  Lane confirmed on the PostgreSQL packagers list that ABI
  stability is being taken care of between minor releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1726747200">- Bump major and default to 17 for Factory and TW.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1731499200">- Bump major to 17 for SLE.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1733918400">- Bump default to 17 for SLE-15-SP7.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1746792000">- Bump major and default to 18 for Factory and TW.</changelog>
</package>
<package pkgid="768996623d63238f12255c3e72910e282968e01d862ea31cad2afa4c6a5adbba18a27ccf031ea792003777044c76531bf60b3ea1860be81e5f97fca90bd9be83" name="postgresql-plpython" arch="noarch">
  <version epoch="0" ver="18" rel="24.3"/>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1673265600">- bsc#1206796: Refine the distinction of where to use sysusers and
  use bcond to have the expression only in one place.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1679918400">- bsc#1209208: Drop hard dependency on systemd</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1684152000">- Overhaul postgresql-README.SUSE and move it from the binary
  package to the noarch wrapper package.
- bsc#1179231: Add an explanation for the /tmp -&gt; /run/postgresql
  move and permission change.
- Add postgresql-README as a separate source file.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1684843200">- boo#1122892: Add a sysconfig variable for initdb.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1691409600">- Bump major version to prepare for PostgreSQL 16, but keep
  default at 15 for now on Factory.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1694692800">- Bump default to 16 on Factory.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1697198400">- Interlock version and release of all noarch packages except for
  the postgresql-docs.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1707393600">- bsc#1219340: Require fillup.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1709035200">- bsc#1219340: The last fix was not correct. Improve it by removing
  the dependency again and call fillup only if it is installed.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1726142400">- bsc#1230423: Relax the dependency of extensions on the server
  version from exact major.minor to greater or equal, after Tom
  Lane confirmed on the PostgreSQL packagers list that ABI
  stability is being taken care of between minor releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1726747200">- Bump major and default to 17 for Factory and TW.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1731499200">- Bump major to 17 for SLE.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1733918400">- Bump default to 17 for SLE-15-SP7.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1746792000">- Bump major and default to 18 for Factory and TW.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1764331200">- Bump major to 18 on SLE.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1775822400">- Get rid of update-alternatives and support immutable mode.
  See README.SUSE for details. (bsc#1245862, jsc#PED-14820)
- Merge the spec files from different products and use the product
  versions to decide about the default PostgreSQL version.</changelog>
</package>
<package pkgid="9cb7e347e46decfc7b47f319e2cfc5360c53b5c766fc51ef95f84f37a96fcbb3a4ef6fe0d30ba3941e280488f0f7cd18bf46580295b1a8c242fdd6b183308b36" name="postgresql-plpython" arch="noarch">
  <version epoch="0" ver="18" rel="8.1"/>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1643371200">- Avoid a dependency on awk in postgresql-script.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1644494400">- Fix the pg_server_requires macro on older rpm versions (SLE-12).</changelog>
  <changelog author="Callum Farmer &lt;gmbr3@opensuse.org&gt;" date="1647432000">- Change to systemd-sysusers</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1653134400">- Bump to postgresql 15</changelog>
  <changelog author="Dirk M&#xFC;ller &lt;dmueller@suse.com&gt;" date="1662379200">- avoid bashisms in /bin/sh based startup script</changelog>
  <changelog author="Andreas Schwab &lt;schwab@suse.de&gt;" date="1663848000">- riscv64 does not have llvm support yet,
  adapt the %postgresql_has_llvm macro accordingly.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1673265600">- bsc#1206796: Refine the distinction of where to use sysusers and
  use bcond to have the expression only in one place.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1679918400">- bsc#1209208: Drop hard dependency on systemd</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1684152000">- Overhaul postgresql-README.SUSE and move it from the binary
  package to the noarch wrapper package.
- bsc#1179231: Add an explanation for the /tmp -&gt; /run/postgresql
  move and permission change.
- Add postgresql-README as a separate source file.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1684843200">- boo#1122892: Add a sysconfig variable for initdb.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1691409600">- Bump major version to prepare for PostgreSQL 16, but keep
  default at 15 for now on Factory.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1694692800">- Bump default to 16 on Factory.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1697198400">- Interlock version and release of all noarch packages except for
  the postgresql-docs.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1707393600">- bsc#1219340: Require fillup.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1709035200">- bsc#1219340: The last fix was not correct. Improve it by removing
  the dependency again and call fillup only if it is installed.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1726142400">- bsc#1230423: Relax the dependency of extensions on the server
  version from exact major.minor to greater or equal, after Tom
  Lane confirmed on the PostgreSQL packagers list that ABI
  stability is being taken care of between minor releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1726747200">- Bump major and default to 17 for Factory and TW.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1731499200">- Bump major to 17 for SLE.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1733918400">- Bump default to 17 for SLE-15-SP7.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1746792000">- Bump major and default to 18 for Factory and TW.</changelog>
</package>
<package pkgid="45e359fb71eac7225adce21bef4851e512ccc7039ed86ebacdf1475541f8d82fee162e2bf1a4f84713a2709d50691bb58d39e3c4fd00f4a08793ee21c6e43842" name="postgresql-pltcl" arch="noarch">
  <version epoch="0" ver="18" rel="24.3"/>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1673265600">- bsc#1206796: Refine the distinction of where to use sysusers and
  use bcond to have the expression only in one place.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1679918400">- bsc#1209208: Drop hard dependency on systemd</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1684152000">- Overhaul postgresql-README.SUSE and move it from the binary
  package to the noarch wrapper package.
- bsc#1179231: Add an explanation for the /tmp -&gt; /run/postgresql
  move and permission change.
- Add postgresql-README as a separate source file.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1684843200">- boo#1122892: Add a sysconfig variable for initdb.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1691409600">- Bump major version to prepare for PostgreSQL 16, but keep
  default at 15 for now on Factory.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1694692800">- Bump default to 16 on Factory.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1697198400">- Interlock version and release of all noarch packages except for
  the postgresql-docs.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1707393600">- bsc#1219340: Require fillup.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1709035200">- bsc#1219340: The last fix was not correct. Improve it by removing
  the dependency again and call fillup only if it is installed.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1726142400">- bsc#1230423: Relax the dependency of extensions on the server
  version from exact major.minor to greater or equal, after Tom
  Lane confirmed on the PostgreSQL packagers list that ABI
  stability is being taken care of between minor releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1726747200">- Bump major and default to 17 for Factory and TW.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1731499200">- Bump major to 17 for SLE.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1733918400">- Bump default to 17 for SLE-15-SP7.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1746792000">- Bump major and default to 18 for Factory and TW.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1764331200">- Bump major to 18 on SLE.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1775822400">- Get rid of update-alternatives and support immutable mode.
  See README.SUSE for details. (bsc#1245862, jsc#PED-14820)
- Merge the spec files from different products and use the product
  versions to decide about the default PostgreSQL version.</changelog>
</package>
<package pkgid="6d659ebe43fd386a4e28ec0fcf4a8249c78366c700aca3b4ba385a0db7baf3a06a11cf1f075a84bbc21e13377ac29b710039e06f2e38592733d6166332fa5043" name="postgresql-pltcl" arch="noarch">
  <version epoch="0" ver="18" rel="8.1"/>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1643371200">- Avoid a dependency on awk in postgresql-script.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1644494400">- Fix the pg_server_requires macro on older rpm versions (SLE-12).</changelog>
  <changelog author="Callum Farmer &lt;gmbr3@opensuse.org&gt;" date="1647432000">- Change to systemd-sysusers</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1653134400">- Bump to postgresql 15</changelog>
  <changelog author="Dirk M&#xFC;ller &lt;dmueller@suse.com&gt;" date="1662379200">- avoid bashisms in /bin/sh based startup script</changelog>
  <changelog author="Andreas Schwab &lt;schwab@suse.de&gt;" date="1663848000">- riscv64 does not have llvm support yet,
  adapt the %postgresql_has_llvm macro accordingly.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1673265600">- bsc#1206796: Refine the distinction of where to use sysusers and
  use bcond to have the expression only in one place.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1679918400">- bsc#1209208: Drop hard dependency on systemd</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1684152000">- Overhaul postgresql-README.SUSE and move it from the binary
  package to the noarch wrapper package.
- bsc#1179231: Add an explanation for the /tmp -&gt; /run/postgresql
  move and permission change.
- Add postgresql-README as a separate source file.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1684843200">- boo#1122892: Add a sysconfig variable for initdb.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1691409600">- Bump major version to prepare for PostgreSQL 16, but keep
  default at 15 for now on Factory.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1694692800">- Bump default to 16 on Factory.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1697198400">- Interlock version and release of all noarch packages except for
  the postgresql-docs.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1707393600">- bsc#1219340: Require fillup.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1709035200">- bsc#1219340: The last fix was not correct. Improve it by removing
  the dependency again and call fillup only if it is installed.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1726142400">- bsc#1230423: Relax the dependency of extensions on the server
  version from exact major.minor to greater or equal, after Tom
  Lane confirmed on the PostgreSQL packagers list that ABI
  stability is being taken care of between minor releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1726747200">- Bump major and default to 17 for Factory and TW.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1731499200">- Bump major to 17 for SLE.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1733918400">- Bump default to 17 for SLE-15-SP7.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1746792000">- Bump major and default to 18 for Factory and TW.</changelog>
</package>
<package pkgid="a4acde4e9f309aa5796c1d500c790c7af5b4eac15b0737d171a10c749bc8be607824737e80050774e7f260d247b8a85f7d328571e08a18a88afcf5fadbf4a537" name="postgresql-server" arch="noarch">
  <version epoch="0" ver="18" rel="24.3"/>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1673265600">- bsc#1206796: Refine the distinction of where to use sysusers and
  use bcond to have the expression only in one place.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1679918400">- bsc#1209208: Drop hard dependency on systemd</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1684152000">- Overhaul postgresql-README.SUSE and move it from the binary
  package to the noarch wrapper package.
- bsc#1179231: Add an explanation for the /tmp -&gt; /run/postgresql
  move and permission change.
- Add postgresql-README as a separate source file.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1684843200">- boo#1122892: Add a sysconfig variable for initdb.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1691409600">- Bump major version to prepare for PostgreSQL 16, but keep
  default at 15 for now on Factory.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1694692800">- Bump default to 16 on Factory.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1697198400">- Interlock version and release of all noarch packages except for
  the postgresql-docs.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1707393600">- bsc#1219340: Require fillup.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1709035200">- bsc#1219340: The last fix was not correct. Improve it by removing
  the dependency again and call fillup only if it is installed.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1726142400">- bsc#1230423: Relax the dependency of extensions on the server
  version from exact major.minor to greater or equal, after Tom
  Lane confirmed on the PostgreSQL packagers list that ABI
  stability is being taken care of between minor releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1726747200">- Bump major and default to 17 for Factory and TW.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1731499200">- Bump major to 17 for SLE.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1733918400">- Bump default to 17 for SLE-15-SP7.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1746792000">- Bump major and default to 18 for Factory and TW.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1764331200">- Bump major to 18 on SLE.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1775822400">- Get rid of update-alternatives and support immutable mode.
  See README.SUSE for details. (bsc#1245862, jsc#PED-14820)
- Merge the spec files from different products and use the product
  versions to decide about the default PostgreSQL version.</changelog>
</package>
<package pkgid="7fb99578dbf891c428a37aa362f0cfbfa44b9f7a6139a10d93cf1258008379b2743e99896a9bfaf7cf8e9aa70c15378c157cfe9ceca9d72a997310903771e5f7" name="postgresql-server" arch="noarch">
  <version epoch="0" ver="18" rel="8.1"/>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1643371200">- Avoid a dependency on awk in postgresql-script.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1644494400">- Fix the pg_server_requires macro on older rpm versions (SLE-12).</changelog>
  <changelog author="Callum Farmer &lt;gmbr3@opensuse.org&gt;" date="1647432000">- Change to systemd-sysusers</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1653134400">- Bump to postgresql 15</changelog>
  <changelog author="Dirk M&#xFC;ller &lt;dmueller@suse.com&gt;" date="1662379200">- avoid bashisms in /bin/sh based startup script</changelog>
  <changelog author="Andreas Schwab &lt;schwab@suse.de&gt;" date="1663848000">- riscv64 does not have llvm support yet,
  adapt the %postgresql_has_llvm macro accordingly.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1673265600">- bsc#1206796: Refine the distinction of where to use sysusers and
  use bcond to have the expression only in one place.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1679918400">- bsc#1209208: Drop hard dependency on systemd</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1684152000">- Overhaul postgresql-README.SUSE and move it from the binary
  package to the noarch wrapper package.
- bsc#1179231: Add an explanation for the /tmp -&gt; /run/postgresql
  move and permission change.
- Add postgresql-README as a separate source file.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1684843200">- boo#1122892: Add a sysconfig variable for initdb.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1691409600">- Bump major version to prepare for PostgreSQL 16, but keep
  default at 15 for now on Factory.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1694692800">- Bump default to 16 on Factory.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1697198400">- Interlock version and release of all noarch packages except for
  the postgresql-docs.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1707393600">- bsc#1219340: Require fillup.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1709035200">- bsc#1219340: The last fix was not correct. Improve it by removing
  the dependency again and call fillup only if it is installed.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1726142400">- bsc#1230423: Relax the dependency of extensions on the server
  version from exact major.minor to greater or equal, after Tom
  Lane confirmed on the PostgreSQL packagers list that ABI
  stability is being taken care of between minor releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1726747200">- Bump major and default to 17 for Factory and TW.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1731499200">- Bump major to 17 for SLE.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1733918400">- Bump default to 17 for SLE-15-SP7.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1746792000">- Bump major and default to 18 for Factory and TW.</changelog>
</package>
<package pkgid="5e21939e32f4d0974f74aff71f341ed6a9f96ed56a397b230e69554fec6c0bd5c7503d5d4218c6987ba6588e83307b8d64dbafecbdd840cd73f9d543294e0d24" name="postgresql-server-devel" arch="noarch">
  <version epoch="0" ver="18" rel="24.3"/>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1673265600">- bsc#1206796: Refine the distinction of where to use sysusers and
  use bcond to have the expression only in one place.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1679918400">- bsc#1209208: Drop hard dependency on systemd</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1684152000">- Overhaul postgresql-README.SUSE and move it from the binary
  package to the noarch wrapper package.
- bsc#1179231: Add an explanation for the /tmp -&gt; /run/postgresql
  move and permission change.
- Add postgresql-README as a separate source file.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1684843200">- boo#1122892: Add a sysconfig variable for initdb.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1691409600">- Bump major version to prepare for PostgreSQL 16, but keep
  default at 15 for now on Factory.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1694692800">- Bump default to 16 on Factory.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1697198400">- Interlock version and release of all noarch packages except for
  the postgresql-docs.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1707393600">- bsc#1219340: Require fillup.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1709035200">- bsc#1219340: The last fix was not correct. Improve it by removing
  the dependency again and call fillup only if it is installed.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1726142400">- bsc#1230423: Relax the dependency of extensions on the server
  version from exact major.minor to greater or equal, after Tom
  Lane confirmed on the PostgreSQL packagers list that ABI
  stability is being taken care of between minor releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1726747200">- Bump major and default to 17 for Factory and TW.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1731499200">- Bump major to 17 for SLE.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1733918400">- Bump default to 17 for SLE-15-SP7.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1746792000">- Bump major and default to 18 for Factory and TW.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1764331200">- Bump major to 18 on SLE.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1775822400">- Get rid of update-alternatives and support immutable mode.
  See README.SUSE for details. (bsc#1245862, jsc#PED-14820)
- Merge the spec files from different products and use the product
  versions to decide about the default PostgreSQL version.</changelog>
</package>
<package pkgid="9a256ac9ffcfda3f4b67f6ba05cc7ae897dd52de090e66be818986cbf8ae2a7f227c2f1493b047e58d1fb9210f77041f336a5d7a60337955d919888979302b20" name="postgresql-server-devel" arch="noarch">
  <version epoch="0" ver="18" rel="8.1"/>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1643371200">- Avoid a dependency on awk in postgresql-script.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1644494400">- Fix the pg_server_requires macro on older rpm versions (SLE-12).</changelog>
  <changelog author="Callum Farmer &lt;gmbr3@opensuse.org&gt;" date="1647432000">- Change to systemd-sysusers</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1653134400">- Bump to postgresql 15</changelog>
  <changelog author="Dirk M&#xFC;ller &lt;dmueller@suse.com&gt;" date="1662379200">- avoid bashisms in /bin/sh based startup script</changelog>
  <changelog author="Andreas Schwab &lt;schwab@suse.de&gt;" date="1663848000">- riscv64 does not have llvm support yet,
  adapt the %postgresql_has_llvm macro accordingly.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1673265600">- bsc#1206796: Refine the distinction of where to use sysusers and
  use bcond to have the expression only in one place.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1679918400">- bsc#1209208: Drop hard dependency on systemd</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1684152000">- Overhaul postgresql-README.SUSE and move it from the binary
  package to the noarch wrapper package.
- bsc#1179231: Add an explanation for the /tmp -&gt; /run/postgresql
  move and permission change.
- Add postgresql-README as a separate source file.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1684843200">- boo#1122892: Add a sysconfig variable for initdb.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1691409600">- Bump major version to prepare for PostgreSQL 16, but keep
  default at 15 for now on Factory.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1694692800">- Bump default to 16 on Factory.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1697198400">- Interlock version and release of all noarch packages except for
  the postgresql-docs.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1707393600">- bsc#1219340: Require fillup.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1709035200">- bsc#1219340: The last fix was not correct. Improve it by removing
  the dependency again and call fillup only if it is installed.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1726142400">- bsc#1230423: Relax the dependency of extensions on the server
  version from exact major.minor to greater or equal, after Tom
  Lane confirmed on the PostgreSQL packagers list that ABI
  stability is being taken care of between minor releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1726747200">- Bump major and default to 17 for Factory and TW.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1731499200">- Bump major to 17 for SLE.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1733918400">- Bump default to 17 for SLE-15-SP7.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1746792000">- Bump major and default to 18 for Factory and TW.</changelog>
</package>
<package pkgid="12251794c9dc6f8dfdfd4335d54ad2bf53c6f796f38d6de3b4fbdd322bef2da94b1241ffbb4a07c456d53c3b3896bf215587ae86b78f2258155e31d727991c13" name="postgresql-test" arch="noarch">
  <version epoch="0" ver="18" rel="24.3"/>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1673265600">- bsc#1206796: Refine the distinction of where to use sysusers and
  use bcond to have the expression only in one place.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1679918400">- bsc#1209208: Drop hard dependency on systemd</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1684152000">- Overhaul postgresql-README.SUSE and move it from the binary
  package to the noarch wrapper package.
- bsc#1179231: Add an explanation for the /tmp -&gt; /run/postgresql
  move and permission change.
- Add postgresql-README as a separate source file.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1684843200">- boo#1122892: Add a sysconfig variable for initdb.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1691409600">- Bump major version to prepare for PostgreSQL 16, but keep
  default at 15 for now on Factory.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1694692800">- Bump default to 16 on Factory.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1697198400">- Interlock version and release of all noarch packages except for
  the postgresql-docs.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1707393600">- bsc#1219340: Require fillup.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1709035200">- bsc#1219340: The last fix was not correct. Improve it by removing
  the dependency again and call fillup only if it is installed.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1726142400">- bsc#1230423: Relax the dependency of extensions on the server
  version from exact major.minor to greater or equal, after Tom
  Lane confirmed on the PostgreSQL packagers list that ABI
  stability is being taken care of between minor releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1726747200">- Bump major and default to 17 for Factory and TW.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1731499200">- Bump major to 17 for SLE.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1733918400">- Bump default to 17 for SLE-15-SP7.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1746792000">- Bump major and default to 18 for Factory and TW.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1764331200">- Bump major to 18 on SLE.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1775822400">- Get rid of update-alternatives and support immutable mode.
  See README.SUSE for details. (bsc#1245862, jsc#PED-14820)
- Merge the spec files from different products and use the product
  versions to decide about the default PostgreSQL version.</changelog>
</package>
<package pkgid="b81157ed744f145a3a4399142a3d278ef820c8b2c779d43cdfa428c22b9abbd799fb2d11c53577429d2b908d3ec719addbe38b66ed37c11d9fccce8f02fc1c47" name="postgresql-test" arch="noarch">
  <version epoch="0" ver="18" rel="8.1"/>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1643371200">- Avoid a dependency on awk in postgresql-script.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1644494400">- Fix the pg_server_requires macro on older rpm versions (SLE-12).</changelog>
  <changelog author="Callum Farmer &lt;gmbr3@opensuse.org&gt;" date="1647432000">- Change to systemd-sysusers</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1653134400">- Bump to postgresql 15</changelog>
  <changelog author="Dirk M&#xFC;ller &lt;dmueller@suse.com&gt;" date="1662379200">- avoid bashisms in /bin/sh based startup script</changelog>
  <changelog author="Andreas Schwab &lt;schwab@suse.de&gt;" date="1663848000">- riscv64 does not have llvm support yet,
  adapt the %postgresql_has_llvm macro accordingly.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1673265600">- bsc#1206796: Refine the distinction of where to use sysusers and
  use bcond to have the expression only in one place.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1679918400">- bsc#1209208: Drop hard dependency on systemd</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1684152000">- Overhaul postgresql-README.SUSE and move it from the binary
  package to the noarch wrapper package.
- bsc#1179231: Add an explanation for the /tmp -&gt; /run/postgresql
  move and permission change.
- Add postgresql-README as a separate source file.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1684843200">- boo#1122892: Add a sysconfig variable for initdb.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1691409600">- Bump major version to prepare for PostgreSQL 16, but keep
  default at 15 for now on Factory.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1694692800">- Bump default to 16 on Factory.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1697198400">- Interlock version and release of all noarch packages except for
  the postgresql-docs.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1707393600">- bsc#1219340: Require fillup.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1709035200">- bsc#1219340: The last fix was not correct. Improve it by removing
  the dependency again and call fillup only if it is installed.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1726142400">- bsc#1230423: Relax the dependency of extensions on the server
  version from exact major.minor to greater or equal, after Tom
  Lane confirmed on the PostgreSQL packagers list that ABI
  stability is being taken care of between minor releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1726747200">- Bump major and default to 17 for Factory and TW.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1731499200">- Bump major to 17 for SLE.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1733918400">- Bump default to 17 for SLE-15-SP7.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1746792000">- Bump major and default to 18 for Factory and TW.</changelog>
</package>
<package pkgid="bbd3520f6d35130fcfffc47b2f92532ba90e9b778e6727e5a6b5642e07a15599eca743020637c22794e55a0759f1d7bad8e797db78c98d74916934f3071b36ef" name="postgresql14" arch="aarch64">
  <version epoch="0" ver="14.22" rel="106.2"/>
  <changelog author="Dominique Leuenberger &lt;dimstar@opensuse.org&gt;" date="1709208000">- Use %patch -P N instead of deprecated %patchN.</changelog>
  <changelog author="Sarah Kriesch &lt;sarah.kriesch@opensuse.org&gt;" date="1709812800">- Remove constraints file because improved memory usage for s390x</changelog>
  <changelog author="Aaron Puchert &lt;aaronpuchert@alice-dsl.net&gt;" date="1714564800">- Require LLVM &lt;= 17 for now, because LLVM 18 doesn't seem to work.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1715169600">- Upgrade to 14.12 (bsc#1224051):
  * bsc#1224038, CVE-2024-4317: Restrict visibility of pg_stats_ext
    and pg_stats_ext_exprs entries to the table owner. See the
    release notes for the steps that have to be taken to fix
    existing PostgreSQL instances.
  * Fix incompatibility with LLVM 18.
  * https://www.postgresql.org/docs/release/14.12/
- Prepare for PostgreSQL 17.
- Make sure all compilation and doc generation happens in %build.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1723291200">- Upgrade to 14.13 (bsc#1229013):
  * bsc#1229013, CVE-2024-7348 PostgreSQL relation replacement
    during pg_dump executes arbitrary SQL
  * https://www.postgresql.org/about/news/p-2910/
  * https://www.postgresql.org/docs/release/14.13/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1730808000">- Sync spec file from postgresql17.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1731499200">- Upgrade to 14.14:
  * CVE-2024-10976, bsc#1233323: Ensure cached plans are marked as
    dependent on the calling role when RLS applies to a
    non-top-level table reference.
  * CVE-2024-10977, bsc#1233325: Make libpq discard error messages
    received during SSL or GSS protocol negotiation.
  * CVE-2024-10978, bsc#1233326: Fix unintended interactions
    between SET SESSION AUTHORIZATION and SET ROLE
  * CVE-2024-10979, bsc#1233327: Prevent trusted PL/Perl code from
    changing environment variables.
  * https://www.postgresql.org/about/news/p-2955/
  * https://www.postgresql.org/docs/release/14.14/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1732017600">- Upgrade to 14.15:
  * Repair ABI break for extensions that work with struct
    ResultRelInfo.
  * Restore functionality of ALTER {ROLE|DATABASE} SET role
  * Fix cases where a logical replication slot's restart_lsn could
    go backwards.
  * Avoid deleting still-needed WAL files during pg_rewind.
  * Count index scans in contrib/bloom indexes in the statistics
    views, such as the pg_stat_user_indexes.idx_scan counter.
  * Fix crash when checking to see if an index's opclass options
    have changed.
  * Avoid assertion failure caused by disconnected NFA sub-graphs
    in regular expression parsing.
  * https://www.postgresql.org/about/news/p-2965/
  * https://www.postgresql.org/docs/release/14.15/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 14.16:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/14.16/
  * https://www.postgresql.org/about/news/-3015/
- Disable LLVM JIT on loongarch64</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 14.17:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/14.17/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 14.18:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/14.18/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Upgrade to 14.19:
  * https://www.postgresql.org/about/news/postgresql-176-1610-1514-1419-1322-and-18-beta-3-released-3118/
  * https://www.postgresql.org/docs/release/14.19/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1758801600">- Sync spec file from version 18.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Upgrade to 14.20:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/14.20/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 14.21:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/14.21/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 14.22 to fix two regressions in 14.21:
  * https://www.postgresql.org/docs/release/14.22/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
</package>
<package pkgid="d0b0002d8178b9c5196d4a540646b3a36b8ed3296589565febdbe111568fc646f62834f1784fdf251878e6ca46cf3783513ed6658c64d5159104e7c6d72e6807" name="postgresql14" arch="ppc64le">
  <version epoch="0" ver="14.22" rel="106.2"/>
  <changelog author="Dominique Leuenberger &lt;dimstar@opensuse.org&gt;" date="1709208000">- Use %patch -P N instead of deprecated %patchN.</changelog>
  <changelog author="Sarah Kriesch &lt;sarah.kriesch@opensuse.org&gt;" date="1709812800">- Remove constraints file because improved memory usage for s390x</changelog>
  <changelog author="Aaron Puchert &lt;aaronpuchert@alice-dsl.net&gt;" date="1714564800">- Require LLVM &lt;= 17 for now, because LLVM 18 doesn't seem to work.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1715169600">- Upgrade to 14.12 (bsc#1224051):
  * bsc#1224038, CVE-2024-4317: Restrict visibility of pg_stats_ext
    and pg_stats_ext_exprs entries to the table owner. See the
    release notes for the steps that have to be taken to fix
    existing PostgreSQL instances.
  * Fix incompatibility with LLVM 18.
  * https://www.postgresql.org/docs/release/14.12/
- Prepare for PostgreSQL 17.
- Make sure all compilation and doc generation happens in %build.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1723291200">- Upgrade to 14.13 (bsc#1229013):
  * bsc#1229013, CVE-2024-7348 PostgreSQL relation replacement
    during pg_dump executes arbitrary SQL
  * https://www.postgresql.org/about/news/p-2910/
  * https://www.postgresql.org/docs/release/14.13/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1730808000">- Sync spec file from postgresql17.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1731499200">- Upgrade to 14.14:
  * CVE-2024-10976, bsc#1233323: Ensure cached plans are marked as
    dependent on the calling role when RLS applies to a
    non-top-level table reference.
  * CVE-2024-10977, bsc#1233325: Make libpq discard error messages
    received during SSL or GSS protocol negotiation.
  * CVE-2024-10978, bsc#1233326: Fix unintended interactions
    between SET SESSION AUTHORIZATION and SET ROLE
  * CVE-2024-10979, bsc#1233327: Prevent trusted PL/Perl code from
    changing environment variables.
  * https://www.postgresql.org/about/news/p-2955/
  * https://www.postgresql.org/docs/release/14.14/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1732017600">- Upgrade to 14.15:
  * Repair ABI break for extensions that work with struct
    ResultRelInfo.
  * Restore functionality of ALTER {ROLE|DATABASE} SET role
  * Fix cases where a logical replication slot's restart_lsn could
    go backwards.
  * Avoid deleting still-needed WAL files during pg_rewind.
  * Count index scans in contrib/bloom indexes in the statistics
    views, such as the pg_stat_user_indexes.idx_scan counter.
  * Fix crash when checking to see if an index's opclass options
    have changed.
  * Avoid assertion failure caused by disconnected NFA sub-graphs
    in regular expression parsing.
  * https://www.postgresql.org/about/news/p-2965/
  * https://www.postgresql.org/docs/release/14.15/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 14.16:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/14.16/
  * https://www.postgresql.org/about/news/-3015/
- Disable LLVM JIT on loongarch64</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 14.17:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/14.17/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 14.18:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/14.18/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Upgrade to 14.19:
  * https://www.postgresql.org/about/news/postgresql-176-1610-1514-1419-1322-and-18-beta-3-released-3118/
  * https://www.postgresql.org/docs/release/14.19/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1758801600">- Sync spec file from version 18.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Upgrade to 14.20:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/14.20/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 14.21:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/14.21/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 14.22 to fix two regressions in 14.21:
  * https://www.postgresql.org/docs/release/14.22/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
</package>
<package pkgid="6865b0466b9eb85fda4b0165b17f46278eeb3732ef7477c9751eb80462008477958d6bd10f05d31ea664ede383b5452dd2251d2f9c0971cd326ae864eb4dd2f3" name="postgresql14" arch="s390x">
  <version epoch="0" ver="14.22" rel="106.2"/>
  <changelog author="Dominique Leuenberger &lt;dimstar@opensuse.org&gt;" date="1709208000">- Use %patch -P N instead of deprecated %patchN.</changelog>
  <changelog author="Sarah Kriesch &lt;sarah.kriesch@opensuse.org&gt;" date="1709812800">- Remove constraints file because improved memory usage for s390x</changelog>
  <changelog author="Aaron Puchert &lt;aaronpuchert@alice-dsl.net&gt;" date="1714564800">- Require LLVM &lt;= 17 for now, because LLVM 18 doesn't seem to work.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1715169600">- Upgrade to 14.12 (bsc#1224051):
  * bsc#1224038, CVE-2024-4317: Restrict visibility of pg_stats_ext
    and pg_stats_ext_exprs entries to the table owner. See the
    release notes for the steps that have to be taken to fix
    existing PostgreSQL instances.
  * Fix incompatibility with LLVM 18.
  * https://www.postgresql.org/docs/release/14.12/
- Prepare for PostgreSQL 17.
- Make sure all compilation and doc generation happens in %build.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1723291200">- Upgrade to 14.13 (bsc#1229013):
  * bsc#1229013, CVE-2024-7348 PostgreSQL relation replacement
    during pg_dump executes arbitrary SQL
  * https://www.postgresql.org/about/news/p-2910/
  * https://www.postgresql.org/docs/release/14.13/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1730808000">- Sync spec file from postgresql17.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1731499200">- Upgrade to 14.14:
  * CVE-2024-10976, bsc#1233323: Ensure cached plans are marked as
    dependent on the calling role when RLS applies to a
    non-top-level table reference.
  * CVE-2024-10977, bsc#1233325: Make libpq discard error messages
    received during SSL or GSS protocol negotiation.
  * CVE-2024-10978, bsc#1233326: Fix unintended interactions
    between SET SESSION AUTHORIZATION and SET ROLE
  * CVE-2024-10979, bsc#1233327: Prevent trusted PL/Perl code from
    changing environment variables.
  * https://www.postgresql.org/about/news/p-2955/
  * https://www.postgresql.org/docs/release/14.14/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1732017600">- Upgrade to 14.15:
  * Repair ABI break for extensions that work with struct
    ResultRelInfo.
  * Restore functionality of ALTER {ROLE|DATABASE} SET role
  * Fix cases where a logical replication slot's restart_lsn could
    go backwards.
  * Avoid deleting still-needed WAL files during pg_rewind.
  * Count index scans in contrib/bloom indexes in the statistics
    views, such as the pg_stat_user_indexes.idx_scan counter.
  * Fix crash when checking to see if an index's opclass options
    have changed.
  * Avoid assertion failure caused by disconnected NFA sub-graphs
    in regular expression parsing.
  * https://www.postgresql.org/about/news/p-2965/
  * https://www.postgresql.org/docs/release/14.15/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 14.16:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/14.16/
  * https://www.postgresql.org/about/news/-3015/
- Disable LLVM JIT on loongarch64</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 14.17:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/14.17/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 14.18:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/14.18/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Upgrade to 14.19:
  * https://www.postgresql.org/about/news/postgresql-176-1610-1514-1419-1322-and-18-beta-3-released-3118/
  * https://www.postgresql.org/docs/release/14.19/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1758801600">- Sync spec file from version 18.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Upgrade to 14.20:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/14.20/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 14.21:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/14.21/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 14.22 to fix two regressions in 14.21:
  * https://www.postgresql.org/docs/release/14.22/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
</package>
<package pkgid="8a895038a2e09bead5606c7f25e6b64212c15fcb99c0dfafd453ce6e9e850c24c71a46d6328a81d328265a29983f6ee003c7b998b514ec26e96b31483fa46667" name="postgresql14" arch="src">
  <version epoch="0" ver="14.22" rel="106.2"/>
  <changelog author="Dominique Leuenberger &lt;dimstar@opensuse.org&gt;" date="1709208000">- Use %patch -P N instead of deprecated %patchN.</changelog>
  <changelog author="Sarah Kriesch &lt;sarah.kriesch@opensuse.org&gt;" date="1709812800">- Remove constraints file because improved memory usage for s390x</changelog>
  <changelog author="Aaron Puchert &lt;aaronpuchert@alice-dsl.net&gt;" date="1714564800">- Require LLVM &lt;= 17 for now, because LLVM 18 doesn't seem to work.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1715169600">- Upgrade to 14.12 (bsc#1224051):
  * bsc#1224038, CVE-2024-4317: Restrict visibility of pg_stats_ext
    and pg_stats_ext_exprs entries to the table owner. See the
    release notes for the steps that have to be taken to fix
    existing PostgreSQL instances.
  * Fix incompatibility with LLVM 18.
  * https://www.postgresql.org/docs/release/14.12/
- Prepare for PostgreSQL 17.
- Make sure all compilation and doc generation happens in %build.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1723291200">- Upgrade to 14.13 (bsc#1229013):
  * bsc#1229013, CVE-2024-7348 PostgreSQL relation replacement
    during pg_dump executes arbitrary SQL
  * https://www.postgresql.org/about/news/p-2910/
  * https://www.postgresql.org/docs/release/14.13/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1730808000">- Sync spec file from postgresql17.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1731499200">- Upgrade to 14.14:
  * CVE-2024-10976, bsc#1233323: Ensure cached plans are marked as
    dependent on the calling role when RLS applies to a
    non-top-level table reference.
  * CVE-2024-10977, bsc#1233325: Make libpq discard error messages
    received during SSL or GSS protocol negotiation.
  * CVE-2024-10978, bsc#1233326: Fix unintended interactions
    between SET SESSION AUTHORIZATION and SET ROLE
  * CVE-2024-10979, bsc#1233327: Prevent trusted PL/Perl code from
    changing environment variables.
  * https://www.postgresql.org/about/news/p-2955/
  * https://www.postgresql.org/docs/release/14.14/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1732017600">- Upgrade to 14.15:
  * Repair ABI break for extensions that work with struct
    ResultRelInfo.
  * Restore functionality of ALTER {ROLE|DATABASE} SET role
  * Fix cases where a logical replication slot's restart_lsn could
    go backwards.
  * Avoid deleting still-needed WAL files during pg_rewind.
  * Count index scans in contrib/bloom indexes in the statistics
    views, such as the pg_stat_user_indexes.idx_scan counter.
  * Fix crash when checking to see if an index's opclass options
    have changed.
  * Avoid assertion failure caused by disconnected NFA sub-graphs
    in regular expression parsing.
  * https://www.postgresql.org/about/news/p-2965/
  * https://www.postgresql.org/docs/release/14.15/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 14.16:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/14.16/
  * https://www.postgresql.org/about/news/-3015/
- Disable LLVM JIT on loongarch64</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 14.17:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/14.17/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 14.18:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/14.18/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Upgrade to 14.19:
  * https://www.postgresql.org/about/news/postgresql-176-1610-1514-1419-1322-and-18-beta-3-released-3118/
  * https://www.postgresql.org/docs/release/14.19/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1758801600">- Sync spec file from version 18.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Upgrade to 14.20:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/14.20/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 14.21:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/14.21/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 14.22 to fix two regressions in 14.21:
  * https://www.postgresql.org/docs/release/14.22/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
</package>
<package pkgid="1dcbf8432ae430e5192a9b19a6fcce6adc06a62b38c61cdbc104cc1bceec50188dca00bd0718ab851ee4a7627194c71d28d9710c39f9021635949802f874f20d" name="postgresql14" arch="src">
  <version epoch="0" ver="14.23" rel="116.2"/>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1715169600">- Upgrade to 14.12 (bsc#1224051):
  * bsc#1224038, CVE-2024-4317: Restrict visibility of pg_stats_ext
    and pg_stats_ext_exprs entries to the table owner. See the
    release notes for the steps that have to be taken to fix
    existing PostgreSQL instances.
  * Fix incompatibility with LLVM 18.
  * https://www.postgresql.org/docs/release/14.12/
- Prepare for PostgreSQL 17.
- Make sure all compilation and doc generation happens in %build.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1723291200">- Upgrade to 14.13 (bsc#1229013):
  * bsc#1229013, CVE-2024-7348 PostgreSQL relation replacement
    during pg_dump executes arbitrary SQL
  * https://www.postgresql.org/about/news/p-2910/
  * https://www.postgresql.org/docs/release/14.13/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1730808000">- Sync spec file from postgresql17.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1731499200">- Upgrade to 14.14:
  * CVE-2024-10976, bsc#1233323: Ensure cached plans are marked as
    dependent on the calling role when RLS applies to a
    non-top-level table reference.
  * CVE-2024-10977, bsc#1233325: Make libpq discard error messages
    received during SSL or GSS protocol negotiation.
  * CVE-2024-10978, bsc#1233326: Fix unintended interactions
    between SET SESSION AUTHORIZATION and SET ROLE
  * CVE-2024-10979, bsc#1233327: Prevent trusted PL/Perl code from
    changing environment variables.
  * https://www.postgresql.org/about/news/p-2955/
  * https://www.postgresql.org/docs/release/14.14/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1732017600">- Upgrade to 14.15:
  * Repair ABI break for extensions that work with struct
    ResultRelInfo.
  * Restore functionality of ALTER {ROLE|DATABASE} SET role
  * Fix cases where a logical replication slot's restart_lsn could
    go backwards.
  * Avoid deleting still-needed WAL files during pg_rewind.
  * Count index scans in contrib/bloom indexes in the statistics
    views, such as the pg_stat_user_indexes.idx_scan counter.
  * Fix crash when checking to see if an index's opclass options
    have changed.
  * Avoid assertion failure caused by disconnected NFA sub-graphs
    in regular expression parsing.
  * https://www.postgresql.org/about/news/p-2965/
  * https://www.postgresql.org/docs/release/14.15/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 14.16:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/14.16/
  * https://www.postgresql.org/about/news/-3015/
- Disable LLVM JIT on loongarch64</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 14.17:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/14.17/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 14.18:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/14.18/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Upgrade to 14.19:
  * https://www.postgresql.org/about/news/postgresql-176-1610-1514-1419-1322-and-18-beta-3-released-3118/
  * https://www.postgresql.org/docs/release/14.19/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1758801600">- Sync spec file from version 18.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Upgrade to 14.20:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/14.20/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 14.21:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/14.21/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 14.22 to fix two regressions in 14.21:
  * https://www.postgresql.org/docs/release/14.22/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1774872000">- Get rid of update-alternatives for openSUSE/SLE 16.0 and newer
  to support immutable systems and transactional updates.
  (jsc#PED-14823)</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1777550400">- bsc#1263804: After dropping update-alternatives we have to
  package /usr/bin/pg_config as an actual symlink, not %ghost.
- Fix spelling of build conditionals.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1778673600">- Update to version 14.23:
  * bsc#1265172, CVE-2026-6472: ensure the user has CREATE
    privilege on the schema specified
  * bsc#1265173, CVE-2026-6473: integer overflows in
    memory-allocation calculations
  * bsc#1265174, CVE-2026-6474: Guard against malicious time zone
    names
  * bsc#1265175, CVE-2026-6475: Prevent path traversal in
    pg_basebackup and pg_rewind
  * bsc#1265177, CVE-2026-6477: Mark PQfn() as unsafe, and avoid
    using it within libpq
  * bsc#1265178, CVE-2026-6478: Use timing-safe string comparisons
    in authentication code
  * bsc#1265179, CVE-2026-6479: Prevent unbounded recursion while
    processing startup packets
  * bsc#1265181, CVE-2026-6637: Prevent SQL injection and buffer
    overruns in contrib/spi
  * https://www.postgresql.org/docs/release/14.23/</changelog>
</package>
<package pkgid="e06b64d185d5805049cc7ff4ba5a0ce645c48b484a0a9f131f46f5e67cd0924ffa5bc24f7e87faa3f78a4032420c1b0087ded707850feece76d01fbb3fce5bd7" name="postgresql14" arch="x86_64">
  <version epoch="0" ver="14.23" rel="116.2"/>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1715169600">- Upgrade to 14.12 (bsc#1224051):
  * bsc#1224038, CVE-2024-4317: Restrict visibility of pg_stats_ext
    and pg_stats_ext_exprs entries to the table owner. See the
    release notes for the steps that have to be taken to fix
    existing PostgreSQL instances.
  * Fix incompatibility with LLVM 18.
  * https://www.postgresql.org/docs/release/14.12/
- Prepare for PostgreSQL 17.
- Make sure all compilation and doc generation happens in %build.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1723291200">- Upgrade to 14.13 (bsc#1229013):
  * bsc#1229013, CVE-2024-7348 PostgreSQL relation replacement
    during pg_dump executes arbitrary SQL
  * https://www.postgresql.org/about/news/p-2910/
  * https://www.postgresql.org/docs/release/14.13/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1730808000">- Sync spec file from postgresql17.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1731499200">- Upgrade to 14.14:
  * CVE-2024-10976, bsc#1233323: Ensure cached plans are marked as
    dependent on the calling role when RLS applies to a
    non-top-level table reference.
  * CVE-2024-10977, bsc#1233325: Make libpq discard error messages
    received during SSL or GSS protocol negotiation.
  * CVE-2024-10978, bsc#1233326: Fix unintended interactions
    between SET SESSION AUTHORIZATION and SET ROLE
  * CVE-2024-10979, bsc#1233327: Prevent trusted PL/Perl code from
    changing environment variables.
  * https://www.postgresql.org/about/news/p-2955/
  * https://www.postgresql.org/docs/release/14.14/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1732017600">- Upgrade to 14.15:
  * Repair ABI break for extensions that work with struct
    ResultRelInfo.
  * Restore functionality of ALTER {ROLE|DATABASE} SET role
  * Fix cases where a logical replication slot's restart_lsn could
    go backwards.
  * Avoid deleting still-needed WAL files during pg_rewind.
  * Count index scans in contrib/bloom indexes in the statistics
    views, such as the pg_stat_user_indexes.idx_scan counter.
  * Fix crash when checking to see if an index's opclass options
    have changed.
  * Avoid assertion failure caused by disconnected NFA sub-graphs
    in regular expression parsing.
  * https://www.postgresql.org/about/news/p-2965/
  * https://www.postgresql.org/docs/release/14.15/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 14.16:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/14.16/
  * https://www.postgresql.org/about/news/-3015/
- Disable LLVM JIT on loongarch64</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 14.17:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/14.17/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 14.18:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/14.18/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Upgrade to 14.19:
  * https://www.postgresql.org/about/news/postgresql-176-1610-1514-1419-1322-and-18-beta-3-released-3118/
  * https://www.postgresql.org/docs/release/14.19/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1758801600">- Sync spec file from version 18.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Upgrade to 14.20:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/14.20/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 14.21:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/14.21/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 14.22 to fix two regressions in 14.21:
  * https://www.postgresql.org/docs/release/14.22/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1774872000">- Get rid of update-alternatives for openSUSE/SLE 16.0 and newer
  to support immutable systems and transactional updates.
  (jsc#PED-14823)</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1777550400">- bsc#1263804: After dropping update-alternatives we have to
  package /usr/bin/pg_config as an actual symlink, not %ghost.
- Fix spelling of build conditionals.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1778673600">- Update to version 14.23:
  * bsc#1265172, CVE-2026-6472: ensure the user has CREATE
    privilege on the schema specified
  * bsc#1265173, CVE-2026-6473: integer overflows in
    memory-allocation calculations
  * bsc#1265174, CVE-2026-6474: Guard against malicious time zone
    names
  * bsc#1265175, CVE-2026-6475: Prevent path traversal in
    pg_basebackup and pg_rewind
  * bsc#1265177, CVE-2026-6477: Mark PQfn() as unsafe, and avoid
    using it within libpq
  * bsc#1265178, CVE-2026-6478: Use timing-safe string comparisons
    in authentication code
  * bsc#1265179, CVE-2026-6479: Prevent unbounded recursion while
    processing startup packets
  * bsc#1265181, CVE-2026-6637: Prevent SQL injection and buffer
    overruns in contrib/spi
  * https://www.postgresql.org/docs/release/14.23/</changelog>
</package>
<package pkgid="d58b5d9220dc26df888629ccabd548832b9d7886c00dd3b201622fbae7aea68eda3f5f9bb94af4d88ebf4e51345d34c9b7f54099a3f259c6f221eeb3eaceea37" name="postgresql14-contrib" arch="aarch64">
  <version epoch="0" ver="14.22" rel="106.2"/>
  <changelog author="Dominique Leuenberger &lt;dimstar@opensuse.org&gt;" date="1709208000">- Use %patch -P N instead of deprecated %patchN.</changelog>
  <changelog author="Sarah Kriesch &lt;sarah.kriesch@opensuse.org&gt;" date="1709812800">- Remove constraints file because improved memory usage for s390x</changelog>
  <changelog author="Aaron Puchert &lt;aaronpuchert@alice-dsl.net&gt;" date="1714564800">- Require LLVM &lt;= 17 for now, because LLVM 18 doesn't seem to work.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1715169600">- Upgrade to 14.12 (bsc#1224051):
  * bsc#1224038, CVE-2024-4317: Restrict visibility of pg_stats_ext
    and pg_stats_ext_exprs entries to the table owner. See the
    release notes for the steps that have to be taken to fix
    existing PostgreSQL instances.
  * Fix incompatibility with LLVM 18.
  * https://www.postgresql.org/docs/release/14.12/
- Prepare for PostgreSQL 17.
- Make sure all compilation and doc generation happens in %build.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1723291200">- Upgrade to 14.13 (bsc#1229013):
  * bsc#1229013, CVE-2024-7348 PostgreSQL relation replacement
    during pg_dump executes arbitrary SQL
  * https://www.postgresql.org/about/news/p-2910/
  * https://www.postgresql.org/docs/release/14.13/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1730808000">- Sync spec file from postgresql17.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1731499200">- Upgrade to 14.14:
  * CVE-2024-10976, bsc#1233323: Ensure cached plans are marked as
    dependent on the calling role when RLS applies to a
    non-top-level table reference.
  * CVE-2024-10977, bsc#1233325: Make libpq discard error messages
    received during SSL or GSS protocol negotiation.
  * CVE-2024-10978, bsc#1233326: Fix unintended interactions
    between SET SESSION AUTHORIZATION and SET ROLE
  * CVE-2024-10979, bsc#1233327: Prevent trusted PL/Perl code from
    changing environment variables.
  * https://www.postgresql.org/about/news/p-2955/
  * https://www.postgresql.org/docs/release/14.14/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1732017600">- Upgrade to 14.15:
  * Repair ABI break for extensions that work with struct
    ResultRelInfo.
  * Restore functionality of ALTER {ROLE|DATABASE} SET role
  * Fix cases where a logical replication slot's restart_lsn could
    go backwards.
  * Avoid deleting still-needed WAL files during pg_rewind.
  * Count index scans in contrib/bloom indexes in the statistics
    views, such as the pg_stat_user_indexes.idx_scan counter.
  * Fix crash when checking to see if an index's opclass options
    have changed.
  * Avoid assertion failure caused by disconnected NFA sub-graphs
    in regular expression parsing.
  * https://www.postgresql.org/about/news/p-2965/
  * https://www.postgresql.org/docs/release/14.15/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 14.16:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/14.16/
  * https://www.postgresql.org/about/news/-3015/
- Disable LLVM JIT on loongarch64</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 14.17:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/14.17/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 14.18:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/14.18/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Upgrade to 14.19:
  * https://www.postgresql.org/about/news/postgresql-176-1610-1514-1419-1322-and-18-beta-3-released-3118/
  * https://www.postgresql.org/docs/release/14.19/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1758801600">- Sync spec file from version 18.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Upgrade to 14.20:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/14.20/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 14.21:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/14.21/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 14.22 to fix two regressions in 14.21:
  * https://www.postgresql.org/docs/release/14.22/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
</package>
<package pkgid="6f82b84b0da160c6b455069fca977ff095d8c9c0821b88454fa43000eb8c8144b4f54b3654dda8fe30583fdb69a1284ff08ce20e0def1c4c639275fa1d47374b" name="postgresql14-contrib" arch="ppc64le">
  <version epoch="0" ver="14.22" rel="106.2"/>
  <changelog author="Dominique Leuenberger &lt;dimstar@opensuse.org&gt;" date="1709208000">- Use %patch -P N instead of deprecated %patchN.</changelog>
  <changelog author="Sarah Kriesch &lt;sarah.kriesch@opensuse.org&gt;" date="1709812800">- Remove constraints file because improved memory usage for s390x</changelog>
  <changelog author="Aaron Puchert &lt;aaronpuchert@alice-dsl.net&gt;" date="1714564800">- Require LLVM &lt;= 17 for now, because LLVM 18 doesn't seem to work.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1715169600">- Upgrade to 14.12 (bsc#1224051):
  * bsc#1224038, CVE-2024-4317: Restrict visibility of pg_stats_ext
    and pg_stats_ext_exprs entries to the table owner. See the
    release notes for the steps that have to be taken to fix
    existing PostgreSQL instances.
  * Fix incompatibility with LLVM 18.
  * https://www.postgresql.org/docs/release/14.12/
- Prepare for PostgreSQL 17.
- Make sure all compilation and doc generation happens in %build.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1723291200">- Upgrade to 14.13 (bsc#1229013):
  * bsc#1229013, CVE-2024-7348 PostgreSQL relation replacement
    during pg_dump executes arbitrary SQL
  * https://www.postgresql.org/about/news/p-2910/
  * https://www.postgresql.org/docs/release/14.13/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1730808000">- Sync spec file from postgresql17.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1731499200">- Upgrade to 14.14:
  * CVE-2024-10976, bsc#1233323: Ensure cached plans are marked as
    dependent on the calling role when RLS applies to a
    non-top-level table reference.
  * CVE-2024-10977, bsc#1233325: Make libpq discard error messages
    received during SSL or GSS protocol negotiation.
  * CVE-2024-10978, bsc#1233326: Fix unintended interactions
    between SET SESSION AUTHORIZATION and SET ROLE
  * CVE-2024-10979, bsc#1233327: Prevent trusted PL/Perl code from
    changing environment variables.
  * https://www.postgresql.org/about/news/p-2955/
  * https://www.postgresql.org/docs/release/14.14/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1732017600">- Upgrade to 14.15:
  * Repair ABI break for extensions that work with struct
    ResultRelInfo.
  * Restore functionality of ALTER {ROLE|DATABASE} SET role
  * Fix cases where a logical replication slot's restart_lsn could
    go backwards.
  * Avoid deleting still-needed WAL files during pg_rewind.
  * Count index scans in contrib/bloom indexes in the statistics
    views, such as the pg_stat_user_indexes.idx_scan counter.
  * Fix crash when checking to see if an index's opclass options
    have changed.
  * Avoid assertion failure caused by disconnected NFA sub-graphs
    in regular expression parsing.
  * https://www.postgresql.org/about/news/p-2965/
  * https://www.postgresql.org/docs/release/14.15/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 14.16:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/14.16/
  * https://www.postgresql.org/about/news/-3015/
- Disable LLVM JIT on loongarch64</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 14.17:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/14.17/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 14.18:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/14.18/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Upgrade to 14.19:
  * https://www.postgresql.org/about/news/postgresql-176-1610-1514-1419-1322-and-18-beta-3-released-3118/
  * https://www.postgresql.org/docs/release/14.19/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1758801600">- Sync spec file from version 18.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Upgrade to 14.20:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/14.20/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 14.21:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/14.21/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 14.22 to fix two regressions in 14.21:
  * https://www.postgresql.org/docs/release/14.22/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
</package>
<package pkgid="b31fc0889f82c338bcaccc7026c111a6e8c24cd8f480d30a7076cf989b6b31bcc8364dd07aa310fcdfa0d101221bed15e27629d0cc78aafcae305be76fdabea9" name="postgresql14-contrib" arch="s390x">
  <version epoch="0" ver="14.22" rel="106.2"/>
  <changelog author="Dominique Leuenberger &lt;dimstar@opensuse.org&gt;" date="1709208000">- Use %patch -P N instead of deprecated %patchN.</changelog>
  <changelog author="Sarah Kriesch &lt;sarah.kriesch@opensuse.org&gt;" date="1709812800">- Remove constraints file because improved memory usage for s390x</changelog>
  <changelog author="Aaron Puchert &lt;aaronpuchert@alice-dsl.net&gt;" date="1714564800">- Require LLVM &lt;= 17 for now, because LLVM 18 doesn't seem to work.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1715169600">- Upgrade to 14.12 (bsc#1224051):
  * bsc#1224038, CVE-2024-4317: Restrict visibility of pg_stats_ext
    and pg_stats_ext_exprs entries to the table owner. See the
    release notes for the steps that have to be taken to fix
    existing PostgreSQL instances.
  * Fix incompatibility with LLVM 18.
  * https://www.postgresql.org/docs/release/14.12/
- Prepare for PostgreSQL 17.
- Make sure all compilation and doc generation happens in %build.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1723291200">- Upgrade to 14.13 (bsc#1229013):
  * bsc#1229013, CVE-2024-7348 PostgreSQL relation replacement
    during pg_dump executes arbitrary SQL
  * https://www.postgresql.org/about/news/p-2910/
  * https://www.postgresql.org/docs/release/14.13/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1730808000">- Sync spec file from postgresql17.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1731499200">- Upgrade to 14.14:
  * CVE-2024-10976, bsc#1233323: Ensure cached plans are marked as
    dependent on the calling role when RLS applies to a
    non-top-level table reference.
  * CVE-2024-10977, bsc#1233325: Make libpq discard error messages
    received during SSL or GSS protocol negotiation.
  * CVE-2024-10978, bsc#1233326: Fix unintended interactions
    between SET SESSION AUTHORIZATION and SET ROLE
  * CVE-2024-10979, bsc#1233327: Prevent trusted PL/Perl code from
    changing environment variables.
  * https://www.postgresql.org/about/news/p-2955/
  * https://www.postgresql.org/docs/release/14.14/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1732017600">- Upgrade to 14.15:
  * Repair ABI break for extensions that work with struct
    ResultRelInfo.
  * Restore functionality of ALTER {ROLE|DATABASE} SET role
  * Fix cases where a logical replication slot's restart_lsn could
    go backwards.
  * Avoid deleting still-needed WAL files during pg_rewind.
  * Count index scans in contrib/bloom indexes in the statistics
    views, such as the pg_stat_user_indexes.idx_scan counter.
  * Fix crash when checking to see if an index's opclass options
    have changed.
  * Avoid assertion failure caused by disconnected NFA sub-graphs
    in regular expression parsing.
  * https://www.postgresql.org/about/news/p-2965/
  * https://www.postgresql.org/docs/release/14.15/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 14.16:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/14.16/
  * https://www.postgresql.org/about/news/-3015/
- Disable LLVM JIT on loongarch64</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 14.17:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/14.17/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 14.18:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/14.18/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Upgrade to 14.19:
  * https://www.postgresql.org/about/news/postgresql-176-1610-1514-1419-1322-and-18-beta-3-released-3118/
  * https://www.postgresql.org/docs/release/14.19/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1758801600">- Sync spec file from version 18.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Upgrade to 14.20:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/14.20/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 14.21:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/14.21/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 14.22 to fix two regressions in 14.21:
  * https://www.postgresql.org/docs/release/14.22/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
</package>
<package pkgid="4f3717895e3d32c22c990d0e5ce378dbe6a12ba13841568584a772eaae3aaf81a76f93f22769ab95fdd7c53a2221c2237e95817817109e819e4441c9e88b7e32" name="postgresql14-contrib" arch="x86_64">
  <version epoch="0" ver="14.23" rel="116.2"/>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1715169600">- Upgrade to 14.12 (bsc#1224051):
  * bsc#1224038, CVE-2024-4317: Restrict visibility of pg_stats_ext
    and pg_stats_ext_exprs entries to the table owner. See the
    release notes for the steps that have to be taken to fix
    existing PostgreSQL instances.
  * Fix incompatibility with LLVM 18.
  * https://www.postgresql.org/docs/release/14.12/
- Prepare for PostgreSQL 17.
- Make sure all compilation and doc generation happens in %build.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1723291200">- Upgrade to 14.13 (bsc#1229013):
  * bsc#1229013, CVE-2024-7348 PostgreSQL relation replacement
    during pg_dump executes arbitrary SQL
  * https://www.postgresql.org/about/news/p-2910/
  * https://www.postgresql.org/docs/release/14.13/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1730808000">- Sync spec file from postgresql17.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1731499200">- Upgrade to 14.14:
  * CVE-2024-10976, bsc#1233323: Ensure cached plans are marked as
    dependent on the calling role when RLS applies to a
    non-top-level table reference.
  * CVE-2024-10977, bsc#1233325: Make libpq discard error messages
    received during SSL or GSS protocol negotiation.
  * CVE-2024-10978, bsc#1233326: Fix unintended interactions
    between SET SESSION AUTHORIZATION and SET ROLE
  * CVE-2024-10979, bsc#1233327: Prevent trusted PL/Perl code from
    changing environment variables.
  * https://www.postgresql.org/about/news/p-2955/
  * https://www.postgresql.org/docs/release/14.14/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1732017600">- Upgrade to 14.15:
  * Repair ABI break for extensions that work with struct
    ResultRelInfo.
  * Restore functionality of ALTER {ROLE|DATABASE} SET role
  * Fix cases where a logical replication slot's restart_lsn could
    go backwards.
  * Avoid deleting still-needed WAL files during pg_rewind.
  * Count index scans in contrib/bloom indexes in the statistics
    views, such as the pg_stat_user_indexes.idx_scan counter.
  * Fix crash when checking to see if an index's opclass options
    have changed.
  * Avoid assertion failure caused by disconnected NFA sub-graphs
    in regular expression parsing.
  * https://www.postgresql.org/about/news/p-2965/
  * https://www.postgresql.org/docs/release/14.15/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 14.16:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/14.16/
  * https://www.postgresql.org/about/news/-3015/
- Disable LLVM JIT on loongarch64</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 14.17:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/14.17/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 14.18:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/14.18/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Upgrade to 14.19:
  * https://www.postgresql.org/about/news/postgresql-176-1610-1514-1419-1322-and-18-beta-3-released-3118/
  * https://www.postgresql.org/docs/release/14.19/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1758801600">- Sync spec file from version 18.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Upgrade to 14.20:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/14.20/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 14.21:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/14.21/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 14.22 to fix two regressions in 14.21:
  * https://www.postgresql.org/docs/release/14.22/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1774872000">- Get rid of update-alternatives for openSUSE/SLE 16.0 and newer
  to support immutable systems and transactional updates.
  (jsc#PED-14823)</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1777550400">- bsc#1263804: After dropping update-alternatives we have to
  package /usr/bin/pg_config as an actual symlink, not %ghost.
- Fix spelling of build conditionals.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1778673600">- Update to version 14.23:
  * bsc#1265172, CVE-2026-6472: ensure the user has CREATE
    privilege on the schema specified
  * bsc#1265173, CVE-2026-6473: integer overflows in
    memory-allocation calculations
  * bsc#1265174, CVE-2026-6474: Guard against malicious time zone
    names
  * bsc#1265175, CVE-2026-6475: Prevent path traversal in
    pg_basebackup and pg_rewind
  * bsc#1265177, CVE-2026-6477: Mark PQfn() as unsafe, and avoid
    using it within libpq
  * bsc#1265178, CVE-2026-6478: Use timing-safe string comparisons
    in authentication code
  * bsc#1265179, CVE-2026-6479: Prevent unbounded recursion while
    processing startup packets
  * bsc#1265181, CVE-2026-6637: Prevent SQL injection and buffer
    overruns in contrib/spi
  * https://www.postgresql.org/docs/release/14.23/</changelog>
</package>
<package pkgid="cbec5a118112cee2fe66761aa195fa2e76b7431ff96d203370f436e1e8782b9215b6d657e6157aecddf257786eb77e401542eca3bea4f855a6d20ada6746a456" name="postgresql14-devel" arch="aarch64">
  <version epoch="0" ver="14.22" rel="106.2"/>
  <changelog author="Dominique Leuenberger &lt;dimstar@opensuse.org&gt;" date="1709208000">- Use %patch -P N instead of deprecated %patchN.</changelog>
  <changelog author="Sarah Kriesch &lt;sarah.kriesch@opensuse.org&gt;" date="1709812800">- Remove constraints file because improved memory usage for s390x</changelog>
  <changelog author="Aaron Puchert &lt;aaronpuchert@alice-dsl.net&gt;" date="1714564800">- Require LLVM &lt;= 17 for now, because LLVM 18 doesn't seem to work.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1715169600">- Upgrade to 14.12 (bsc#1224051):
  * bsc#1224038, CVE-2024-4317: Restrict visibility of pg_stats_ext
    and pg_stats_ext_exprs entries to the table owner. See the
    release notes for the steps that have to be taken to fix
    existing PostgreSQL instances.
  * Fix incompatibility with LLVM 18.
  * https://www.postgresql.org/docs/release/14.12/
- Prepare for PostgreSQL 17.
- Make sure all compilation and doc generation happens in %build.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1723291200">- Upgrade to 14.13 (bsc#1229013):
  * bsc#1229013, CVE-2024-7348 PostgreSQL relation replacement
    during pg_dump executes arbitrary SQL
  * https://www.postgresql.org/about/news/p-2910/
  * https://www.postgresql.org/docs/release/14.13/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1730808000">- Sync spec file from postgresql17.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1731499200">- Upgrade to 14.14:
  * CVE-2024-10976, bsc#1233323: Ensure cached plans are marked as
    dependent on the calling role when RLS applies to a
    non-top-level table reference.
  * CVE-2024-10977, bsc#1233325: Make libpq discard error messages
    received during SSL or GSS protocol negotiation.
  * CVE-2024-10978, bsc#1233326: Fix unintended interactions
    between SET SESSION AUTHORIZATION and SET ROLE
  * CVE-2024-10979, bsc#1233327: Prevent trusted PL/Perl code from
    changing environment variables.
  * https://www.postgresql.org/about/news/p-2955/
  * https://www.postgresql.org/docs/release/14.14/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1732017600">- Upgrade to 14.15:
  * Repair ABI break for extensions that work with struct
    ResultRelInfo.
  * Restore functionality of ALTER {ROLE|DATABASE} SET role
  * Fix cases where a logical replication slot's restart_lsn could
    go backwards.
  * Avoid deleting still-needed WAL files during pg_rewind.
  * Count index scans in contrib/bloom indexes in the statistics
    views, such as the pg_stat_user_indexes.idx_scan counter.
  * Fix crash when checking to see if an index's opclass options
    have changed.
  * Avoid assertion failure caused by disconnected NFA sub-graphs
    in regular expression parsing.
  * https://www.postgresql.org/about/news/p-2965/
  * https://www.postgresql.org/docs/release/14.15/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 14.16:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/14.16/
  * https://www.postgresql.org/about/news/-3015/
- Disable LLVM JIT on loongarch64</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 14.17:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/14.17/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 14.18:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/14.18/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Upgrade to 14.19:
  * https://www.postgresql.org/about/news/postgresql-176-1610-1514-1419-1322-and-18-beta-3-released-3118/
  * https://www.postgresql.org/docs/release/14.19/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1758801600">- Sync spec file from version 18.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Upgrade to 14.20:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/14.20/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 14.21:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/14.21/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 14.22 to fix two regressions in 14.21:
  * https://www.postgresql.org/docs/release/14.22/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
</package>
<package pkgid="e1758b9acb27c51b3d6f23395bab23b5f7787599a9f518435ad9f59fb8edb7ce6c487df6d3c5f7c91bdca4d8fc04ef7f81307941b1d32411c6bed90d110411ac" name="postgresql14-devel" arch="ppc64le">
  <version epoch="0" ver="14.22" rel="106.2"/>
  <changelog author="Dominique Leuenberger &lt;dimstar@opensuse.org&gt;" date="1709208000">- Use %patch -P N instead of deprecated %patchN.</changelog>
  <changelog author="Sarah Kriesch &lt;sarah.kriesch@opensuse.org&gt;" date="1709812800">- Remove constraints file because improved memory usage for s390x</changelog>
  <changelog author="Aaron Puchert &lt;aaronpuchert@alice-dsl.net&gt;" date="1714564800">- Require LLVM &lt;= 17 for now, because LLVM 18 doesn't seem to work.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1715169600">- Upgrade to 14.12 (bsc#1224051):
  * bsc#1224038, CVE-2024-4317: Restrict visibility of pg_stats_ext
    and pg_stats_ext_exprs entries to the table owner. See the
    release notes for the steps that have to be taken to fix
    existing PostgreSQL instances.
  * Fix incompatibility with LLVM 18.
  * https://www.postgresql.org/docs/release/14.12/
- Prepare for PostgreSQL 17.
- Make sure all compilation and doc generation happens in %build.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1723291200">- Upgrade to 14.13 (bsc#1229013):
  * bsc#1229013, CVE-2024-7348 PostgreSQL relation replacement
    during pg_dump executes arbitrary SQL
  * https://www.postgresql.org/about/news/p-2910/
  * https://www.postgresql.org/docs/release/14.13/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1730808000">- Sync spec file from postgresql17.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1731499200">- Upgrade to 14.14:
  * CVE-2024-10976, bsc#1233323: Ensure cached plans are marked as
    dependent on the calling role when RLS applies to a
    non-top-level table reference.
  * CVE-2024-10977, bsc#1233325: Make libpq discard error messages
    received during SSL or GSS protocol negotiation.
  * CVE-2024-10978, bsc#1233326: Fix unintended interactions
    between SET SESSION AUTHORIZATION and SET ROLE
  * CVE-2024-10979, bsc#1233327: Prevent trusted PL/Perl code from
    changing environment variables.
  * https://www.postgresql.org/about/news/p-2955/
  * https://www.postgresql.org/docs/release/14.14/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1732017600">- Upgrade to 14.15:
  * Repair ABI break for extensions that work with struct
    ResultRelInfo.
  * Restore functionality of ALTER {ROLE|DATABASE} SET role
  * Fix cases where a logical replication slot's restart_lsn could
    go backwards.
  * Avoid deleting still-needed WAL files during pg_rewind.
  * Count index scans in contrib/bloom indexes in the statistics
    views, such as the pg_stat_user_indexes.idx_scan counter.
  * Fix crash when checking to see if an index's opclass options
    have changed.
  * Avoid assertion failure caused by disconnected NFA sub-graphs
    in regular expression parsing.
  * https://www.postgresql.org/about/news/p-2965/
  * https://www.postgresql.org/docs/release/14.15/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 14.16:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/14.16/
  * https://www.postgresql.org/about/news/-3015/
- Disable LLVM JIT on loongarch64</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 14.17:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/14.17/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 14.18:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/14.18/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Upgrade to 14.19:
  * https://www.postgresql.org/about/news/postgresql-176-1610-1514-1419-1322-and-18-beta-3-released-3118/
  * https://www.postgresql.org/docs/release/14.19/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1758801600">- Sync spec file from version 18.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Upgrade to 14.20:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/14.20/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 14.21:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/14.21/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 14.22 to fix two regressions in 14.21:
  * https://www.postgresql.org/docs/release/14.22/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
</package>
<package pkgid="39c557b788872618f25807ab5343dabf8610d587b0bdcdd0e9539b7422cf3f6ab97cf741499fd154c54e125ed823e2f98fc7030b56de026f758d2dedc42c9513" name="postgresql14-devel" arch="s390x">
  <version epoch="0" ver="14.22" rel="106.2"/>
  <changelog author="Dominique Leuenberger &lt;dimstar@opensuse.org&gt;" date="1709208000">- Use %patch -P N instead of deprecated %patchN.</changelog>
  <changelog author="Sarah Kriesch &lt;sarah.kriesch@opensuse.org&gt;" date="1709812800">- Remove constraints file because improved memory usage for s390x</changelog>
  <changelog author="Aaron Puchert &lt;aaronpuchert@alice-dsl.net&gt;" date="1714564800">- Require LLVM &lt;= 17 for now, because LLVM 18 doesn't seem to work.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1715169600">- Upgrade to 14.12 (bsc#1224051):
  * bsc#1224038, CVE-2024-4317: Restrict visibility of pg_stats_ext
    and pg_stats_ext_exprs entries to the table owner. See the
    release notes for the steps that have to be taken to fix
    existing PostgreSQL instances.
  * Fix incompatibility with LLVM 18.
  * https://www.postgresql.org/docs/release/14.12/
- Prepare for PostgreSQL 17.
- Make sure all compilation and doc generation happens in %build.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1723291200">- Upgrade to 14.13 (bsc#1229013):
  * bsc#1229013, CVE-2024-7348 PostgreSQL relation replacement
    during pg_dump executes arbitrary SQL
  * https://www.postgresql.org/about/news/p-2910/
  * https://www.postgresql.org/docs/release/14.13/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1730808000">- Sync spec file from postgresql17.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1731499200">- Upgrade to 14.14:
  * CVE-2024-10976, bsc#1233323: Ensure cached plans are marked as
    dependent on the calling role when RLS applies to a
    non-top-level table reference.
  * CVE-2024-10977, bsc#1233325: Make libpq discard error messages
    received during SSL or GSS protocol negotiation.
  * CVE-2024-10978, bsc#1233326: Fix unintended interactions
    between SET SESSION AUTHORIZATION and SET ROLE
  * CVE-2024-10979, bsc#1233327: Prevent trusted PL/Perl code from
    changing environment variables.
  * https://www.postgresql.org/about/news/p-2955/
  * https://www.postgresql.org/docs/release/14.14/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1732017600">- Upgrade to 14.15:
  * Repair ABI break for extensions that work with struct
    ResultRelInfo.
  * Restore functionality of ALTER {ROLE|DATABASE} SET role
  * Fix cases where a logical replication slot's restart_lsn could
    go backwards.
  * Avoid deleting still-needed WAL files during pg_rewind.
  * Count index scans in contrib/bloom indexes in the statistics
    views, such as the pg_stat_user_indexes.idx_scan counter.
  * Fix crash when checking to see if an index's opclass options
    have changed.
  * Avoid assertion failure caused by disconnected NFA sub-graphs
    in regular expression parsing.
  * https://www.postgresql.org/about/news/p-2965/
  * https://www.postgresql.org/docs/release/14.15/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 14.16:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/14.16/
  * https://www.postgresql.org/about/news/-3015/
- Disable LLVM JIT on loongarch64</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 14.17:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/14.17/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 14.18:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/14.18/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Upgrade to 14.19:
  * https://www.postgresql.org/about/news/postgresql-176-1610-1514-1419-1322-and-18-beta-3-released-3118/
  * https://www.postgresql.org/docs/release/14.19/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1758801600">- Sync spec file from version 18.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Upgrade to 14.20:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/14.20/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 14.21:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/14.21/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 14.22 to fix two regressions in 14.21:
  * https://www.postgresql.org/docs/release/14.22/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
</package>
<package pkgid="c36fb7cb7f38b10865459aa0b365abe4b755a65e4c0232eee78562d8642fbf184eefffbc8ab3d76a3d1604fec19e61cbcb7b7324580c5fd073a30d1076829b04" name="postgresql14-devel" arch="x86_64">
  <version epoch="0" ver="14.23" rel="116.2"/>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1715169600">- Upgrade to 14.12 (bsc#1224051):
  * bsc#1224038, CVE-2024-4317: Restrict visibility of pg_stats_ext
    and pg_stats_ext_exprs entries to the table owner. See the
    release notes for the steps that have to be taken to fix
    existing PostgreSQL instances.
  * Fix incompatibility with LLVM 18.
  * https://www.postgresql.org/docs/release/14.12/
- Prepare for PostgreSQL 17.
- Make sure all compilation and doc generation happens in %build.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1723291200">- Upgrade to 14.13 (bsc#1229013):
  * bsc#1229013, CVE-2024-7348 PostgreSQL relation replacement
    during pg_dump executes arbitrary SQL
  * https://www.postgresql.org/about/news/p-2910/
  * https://www.postgresql.org/docs/release/14.13/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1730808000">- Sync spec file from postgresql17.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1731499200">- Upgrade to 14.14:
  * CVE-2024-10976, bsc#1233323: Ensure cached plans are marked as
    dependent on the calling role when RLS applies to a
    non-top-level table reference.
  * CVE-2024-10977, bsc#1233325: Make libpq discard error messages
    received during SSL or GSS protocol negotiation.
  * CVE-2024-10978, bsc#1233326: Fix unintended interactions
    between SET SESSION AUTHORIZATION and SET ROLE
  * CVE-2024-10979, bsc#1233327: Prevent trusted PL/Perl code from
    changing environment variables.
  * https://www.postgresql.org/about/news/p-2955/
  * https://www.postgresql.org/docs/release/14.14/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1732017600">- Upgrade to 14.15:
  * Repair ABI break for extensions that work with struct
    ResultRelInfo.
  * Restore functionality of ALTER {ROLE|DATABASE} SET role
  * Fix cases where a logical replication slot's restart_lsn could
    go backwards.
  * Avoid deleting still-needed WAL files during pg_rewind.
  * Count index scans in contrib/bloom indexes in the statistics
    views, such as the pg_stat_user_indexes.idx_scan counter.
  * Fix crash when checking to see if an index's opclass options
    have changed.
  * Avoid assertion failure caused by disconnected NFA sub-graphs
    in regular expression parsing.
  * https://www.postgresql.org/about/news/p-2965/
  * https://www.postgresql.org/docs/release/14.15/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 14.16:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/14.16/
  * https://www.postgresql.org/about/news/-3015/
- Disable LLVM JIT on loongarch64</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 14.17:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/14.17/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 14.18:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/14.18/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Upgrade to 14.19:
  * https://www.postgresql.org/about/news/postgresql-176-1610-1514-1419-1322-and-18-beta-3-released-3118/
  * https://www.postgresql.org/docs/release/14.19/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1758801600">- Sync spec file from version 18.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Upgrade to 14.20:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/14.20/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 14.21:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/14.21/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 14.22 to fix two regressions in 14.21:
  * https://www.postgresql.org/docs/release/14.22/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1774872000">- Get rid of update-alternatives for openSUSE/SLE 16.0 and newer
  to support immutable systems and transactional updates.
  (jsc#PED-14823)</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1777550400">- bsc#1263804: After dropping update-alternatives we have to
  package /usr/bin/pg_config as an actual symlink, not %ghost.
- Fix spelling of build conditionals.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1778673600">- Update to version 14.23:
  * bsc#1265172, CVE-2026-6472: ensure the user has CREATE
    privilege on the schema specified
  * bsc#1265173, CVE-2026-6473: integer overflows in
    memory-allocation calculations
  * bsc#1265174, CVE-2026-6474: Guard against malicious time zone
    names
  * bsc#1265175, CVE-2026-6475: Prevent path traversal in
    pg_basebackup and pg_rewind
  * bsc#1265177, CVE-2026-6477: Mark PQfn() as unsafe, and avoid
    using it within libpq
  * bsc#1265178, CVE-2026-6478: Use timing-safe string comparisons
    in authentication code
  * bsc#1265179, CVE-2026-6479: Prevent unbounded recursion while
    processing startup packets
  * bsc#1265181, CVE-2026-6637: Prevent SQL injection and buffer
    overruns in contrib/spi
  * https://www.postgresql.org/docs/release/14.23/</changelog>
</package>
<package pkgid="d515dd23d43ffe094d548c0b4f9765c2a9c4a47a2909fc0a54644b17f3edf99b463df8d6056f79cda521668d28f637115de1fae92fd9435def546f167c11af9f" name="postgresql14-docs" arch="noarch">
  <version epoch="0" ver="14.22" rel="106.2"/>
  <changelog author="Dominique Leuenberger &lt;dimstar@opensuse.org&gt;" date="1709208000">- Use %patch -P N instead of deprecated %patchN.</changelog>
  <changelog author="Sarah Kriesch &lt;sarah.kriesch@opensuse.org&gt;" date="1709812800">- Remove constraints file because improved memory usage for s390x</changelog>
  <changelog author="Aaron Puchert &lt;aaronpuchert@alice-dsl.net&gt;" date="1714564800">- Require LLVM &lt;= 17 for now, because LLVM 18 doesn't seem to work.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1715169600">- Upgrade to 14.12 (bsc#1224051):
  * bsc#1224038, CVE-2024-4317: Restrict visibility of pg_stats_ext
    and pg_stats_ext_exprs entries to the table owner. See the
    release notes for the steps that have to be taken to fix
    existing PostgreSQL instances.
  * Fix incompatibility with LLVM 18.
  * https://www.postgresql.org/docs/release/14.12/
- Prepare for PostgreSQL 17.
- Make sure all compilation and doc generation happens in %build.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1723291200">- Upgrade to 14.13 (bsc#1229013):
  * bsc#1229013, CVE-2024-7348 PostgreSQL relation replacement
    during pg_dump executes arbitrary SQL
  * https://www.postgresql.org/about/news/p-2910/
  * https://www.postgresql.org/docs/release/14.13/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1730808000">- Sync spec file from postgresql17.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1731499200">- Upgrade to 14.14:
  * CVE-2024-10976, bsc#1233323: Ensure cached plans are marked as
    dependent on the calling role when RLS applies to a
    non-top-level table reference.
  * CVE-2024-10977, bsc#1233325: Make libpq discard error messages
    received during SSL or GSS protocol negotiation.
  * CVE-2024-10978, bsc#1233326: Fix unintended interactions
    between SET SESSION AUTHORIZATION and SET ROLE
  * CVE-2024-10979, bsc#1233327: Prevent trusted PL/Perl code from
    changing environment variables.
  * https://www.postgresql.org/about/news/p-2955/
  * https://www.postgresql.org/docs/release/14.14/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1732017600">- Upgrade to 14.15:
  * Repair ABI break for extensions that work with struct
    ResultRelInfo.
  * Restore functionality of ALTER {ROLE|DATABASE} SET role
  * Fix cases where a logical replication slot's restart_lsn could
    go backwards.
  * Avoid deleting still-needed WAL files during pg_rewind.
  * Count index scans in contrib/bloom indexes in the statistics
    views, such as the pg_stat_user_indexes.idx_scan counter.
  * Fix crash when checking to see if an index's opclass options
    have changed.
  * Avoid assertion failure caused by disconnected NFA sub-graphs
    in regular expression parsing.
  * https://www.postgresql.org/about/news/p-2965/
  * https://www.postgresql.org/docs/release/14.15/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 14.16:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/14.16/
  * https://www.postgresql.org/about/news/-3015/
- Disable LLVM JIT on loongarch64</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 14.17:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/14.17/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 14.18:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/14.18/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Upgrade to 14.19:
  * https://www.postgresql.org/about/news/postgresql-176-1610-1514-1419-1322-and-18-beta-3-released-3118/
  * https://www.postgresql.org/docs/release/14.19/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1758801600">- Sync spec file from version 18.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Upgrade to 14.20:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/14.20/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 14.21:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/14.21/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 14.22 to fix two regressions in 14.21:
  * https://www.postgresql.org/docs/release/14.22/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
</package>
<package pkgid="0d25d0aff690539997e7b2dac37bee7ce990723537b5e57fdd49095c7fb5771cf8723dca3b077d372b19b0ebaff380aeb1a5e415f60e55ff6d6a04f956aeeee7" name="postgresql14-docs" arch="noarch">
  <version epoch="0" ver="14.23" rel="116.2"/>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1715169600">- Upgrade to 14.12 (bsc#1224051):
  * bsc#1224038, CVE-2024-4317: Restrict visibility of pg_stats_ext
    and pg_stats_ext_exprs entries to the table owner. See the
    release notes for the steps that have to be taken to fix
    existing PostgreSQL instances.
  * Fix incompatibility with LLVM 18.
  * https://www.postgresql.org/docs/release/14.12/
- Prepare for PostgreSQL 17.
- Make sure all compilation and doc generation happens in %build.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1723291200">- Upgrade to 14.13 (bsc#1229013):
  * bsc#1229013, CVE-2024-7348 PostgreSQL relation replacement
    during pg_dump executes arbitrary SQL
  * https://www.postgresql.org/about/news/p-2910/
  * https://www.postgresql.org/docs/release/14.13/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1730808000">- Sync spec file from postgresql17.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1731499200">- Upgrade to 14.14:
  * CVE-2024-10976, bsc#1233323: Ensure cached plans are marked as
    dependent on the calling role when RLS applies to a
    non-top-level table reference.
  * CVE-2024-10977, bsc#1233325: Make libpq discard error messages
    received during SSL or GSS protocol negotiation.
  * CVE-2024-10978, bsc#1233326: Fix unintended interactions
    between SET SESSION AUTHORIZATION and SET ROLE
  * CVE-2024-10979, bsc#1233327: Prevent trusted PL/Perl code from
    changing environment variables.
  * https://www.postgresql.org/about/news/p-2955/
  * https://www.postgresql.org/docs/release/14.14/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1732017600">- Upgrade to 14.15:
  * Repair ABI break for extensions that work with struct
    ResultRelInfo.
  * Restore functionality of ALTER {ROLE|DATABASE} SET role
  * Fix cases where a logical replication slot's restart_lsn could
    go backwards.
  * Avoid deleting still-needed WAL files during pg_rewind.
  * Count index scans in contrib/bloom indexes in the statistics
    views, such as the pg_stat_user_indexes.idx_scan counter.
  * Fix crash when checking to see if an index's opclass options
    have changed.
  * Avoid assertion failure caused by disconnected NFA sub-graphs
    in regular expression parsing.
  * https://www.postgresql.org/about/news/p-2965/
  * https://www.postgresql.org/docs/release/14.15/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 14.16:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/14.16/
  * https://www.postgresql.org/about/news/-3015/
- Disable LLVM JIT on loongarch64</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 14.17:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/14.17/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 14.18:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/14.18/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Upgrade to 14.19:
  * https://www.postgresql.org/about/news/postgresql-176-1610-1514-1419-1322-and-18-beta-3-released-3118/
  * https://www.postgresql.org/docs/release/14.19/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1758801600">- Sync spec file from version 18.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Upgrade to 14.20:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/14.20/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 14.21:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/14.21/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 14.22 to fix two regressions in 14.21:
  * https://www.postgresql.org/docs/release/14.22/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1774872000">- Get rid of update-alternatives for openSUSE/SLE 16.0 and newer
  to support immutable systems and transactional updates.
  (jsc#PED-14823)</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1777550400">- bsc#1263804: After dropping update-alternatives we have to
  package /usr/bin/pg_config as an actual symlink, not %ghost.
- Fix spelling of build conditionals.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1778673600">- Update to version 14.23:
  * bsc#1265172, CVE-2026-6472: ensure the user has CREATE
    privilege on the schema specified
  * bsc#1265173, CVE-2026-6473: integer overflows in
    memory-allocation calculations
  * bsc#1265174, CVE-2026-6474: Guard against malicious time zone
    names
  * bsc#1265175, CVE-2026-6475: Prevent path traversal in
    pg_basebackup and pg_rewind
  * bsc#1265177, CVE-2026-6477: Mark PQfn() as unsafe, and avoid
    using it within libpq
  * bsc#1265178, CVE-2026-6478: Use timing-safe string comparisons
    in authentication code
  * bsc#1265179, CVE-2026-6479: Prevent unbounded recursion while
    processing startup packets
  * bsc#1265181, CVE-2026-6637: Prevent SQL injection and buffer
    overruns in contrib/spi
  * https://www.postgresql.org/docs/release/14.23/</changelog>
</package>
<package pkgid="77238d757661a129199118bc770a360ad2c427b134b2d6e36e8e3605dc6fccaf6dae07cc2405ce5286fdd3d2967f23736f608c299add62db779e662f0552c0aa" name="postgresql14-llvmjit" arch="aarch64">
  <version epoch="0" ver="14.22" rel="106.2"/>
  <changelog author="Dominique Leuenberger &lt;dimstar@opensuse.org&gt;" date="1709208000">- Use %patch -P N instead of deprecated %patchN.</changelog>
  <changelog author="Sarah Kriesch &lt;sarah.kriesch@opensuse.org&gt;" date="1709812800">- Remove constraints file because improved memory usage for s390x</changelog>
  <changelog author="Aaron Puchert &lt;aaronpuchert@alice-dsl.net&gt;" date="1714564800">- Require LLVM &lt;= 17 for now, because LLVM 18 doesn't seem to work.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1715169600">- Upgrade to 14.12 (bsc#1224051):
  * bsc#1224038, CVE-2024-4317: Restrict visibility of pg_stats_ext
    and pg_stats_ext_exprs entries to the table owner. See the
    release notes for the steps that have to be taken to fix
    existing PostgreSQL instances.
  * Fix incompatibility with LLVM 18.
  * https://www.postgresql.org/docs/release/14.12/
- Prepare for PostgreSQL 17.
- Make sure all compilation and doc generation happens in %build.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1723291200">- Upgrade to 14.13 (bsc#1229013):
  * bsc#1229013, CVE-2024-7348 PostgreSQL relation replacement
    during pg_dump executes arbitrary SQL
  * https://www.postgresql.org/about/news/p-2910/
  * https://www.postgresql.org/docs/release/14.13/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1730808000">- Sync spec file from postgresql17.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1731499200">- Upgrade to 14.14:
  * CVE-2024-10976, bsc#1233323: Ensure cached plans are marked as
    dependent on the calling role when RLS applies to a
    non-top-level table reference.
  * CVE-2024-10977, bsc#1233325: Make libpq discard error messages
    received during SSL or GSS protocol negotiation.
  * CVE-2024-10978, bsc#1233326: Fix unintended interactions
    between SET SESSION AUTHORIZATION and SET ROLE
  * CVE-2024-10979, bsc#1233327: Prevent trusted PL/Perl code from
    changing environment variables.
  * https://www.postgresql.org/about/news/p-2955/
  * https://www.postgresql.org/docs/release/14.14/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1732017600">- Upgrade to 14.15:
  * Repair ABI break for extensions that work with struct
    ResultRelInfo.
  * Restore functionality of ALTER {ROLE|DATABASE} SET role
  * Fix cases where a logical replication slot's restart_lsn could
    go backwards.
  * Avoid deleting still-needed WAL files during pg_rewind.
  * Count index scans in contrib/bloom indexes in the statistics
    views, such as the pg_stat_user_indexes.idx_scan counter.
  * Fix crash when checking to see if an index's opclass options
    have changed.
  * Avoid assertion failure caused by disconnected NFA sub-graphs
    in regular expression parsing.
  * https://www.postgresql.org/about/news/p-2965/
  * https://www.postgresql.org/docs/release/14.15/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 14.16:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/14.16/
  * https://www.postgresql.org/about/news/-3015/
- Disable LLVM JIT on loongarch64</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 14.17:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/14.17/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 14.18:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/14.18/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Upgrade to 14.19:
  * https://www.postgresql.org/about/news/postgresql-176-1610-1514-1419-1322-and-18-beta-3-released-3118/
  * https://www.postgresql.org/docs/release/14.19/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1758801600">- Sync spec file from version 18.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Upgrade to 14.20:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/14.20/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 14.21:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/14.21/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 14.22 to fix two regressions in 14.21:
  * https://www.postgresql.org/docs/release/14.22/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
</package>
<package pkgid="3faf17ab9e4b9019cba347d5d1f12895d011e8d6e968a08c3de44c790ff62575d9f6c8d5686b2236147285e2b1f7af100b8741d74fb343f1a8f1109721847ed3" name="postgresql14-llvmjit" arch="ppc64le">
  <version epoch="0" ver="14.22" rel="106.2"/>
  <changelog author="Dominique Leuenberger &lt;dimstar@opensuse.org&gt;" date="1709208000">- Use %patch -P N instead of deprecated %patchN.</changelog>
  <changelog author="Sarah Kriesch &lt;sarah.kriesch@opensuse.org&gt;" date="1709812800">- Remove constraints file because improved memory usage for s390x</changelog>
  <changelog author="Aaron Puchert &lt;aaronpuchert@alice-dsl.net&gt;" date="1714564800">- Require LLVM &lt;= 17 for now, because LLVM 18 doesn't seem to work.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1715169600">- Upgrade to 14.12 (bsc#1224051):
  * bsc#1224038, CVE-2024-4317: Restrict visibility of pg_stats_ext
    and pg_stats_ext_exprs entries to the table owner. See the
    release notes for the steps that have to be taken to fix
    existing PostgreSQL instances.
  * Fix incompatibility with LLVM 18.
  * https://www.postgresql.org/docs/release/14.12/
- Prepare for PostgreSQL 17.
- Make sure all compilation and doc generation happens in %build.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1723291200">- Upgrade to 14.13 (bsc#1229013):
  * bsc#1229013, CVE-2024-7348 PostgreSQL relation replacement
    during pg_dump executes arbitrary SQL
  * https://www.postgresql.org/about/news/p-2910/
  * https://www.postgresql.org/docs/release/14.13/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1730808000">- Sync spec file from postgresql17.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1731499200">- Upgrade to 14.14:
  * CVE-2024-10976, bsc#1233323: Ensure cached plans are marked as
    dependent on the calling role when RLS applies to a
    non-top-level table reference.
  * CVE-2024-10977, bsc#1233325: Make libpq discard error messages
    received during SSL or GSS protocol negotiation.
  * CVE-2024-10978, bsc#1233326: Fix unintended interactions
    between SET SESSION AUTHORIZATION and SET ROLE
  * CVE-2024-10979, bsc#1233327: Prevent trusted PL/Perl code from
    changing environment variables.
  * https://www.postgresql.org/about/news/p-2955/
  * https://www.postgresql.org/docs/release/14.14/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1732017600">- Upgrade to 14.15:
  * Repair ABI break for extensions that work with struct
    ResultRelInfo.
  * Restore functionality of ALTER {ROLE|DATABASE} SET role
  * Fix cases where a logical replication slot's restart_lsn could
    go backwards.
  * Avoid deleting still-needed WAL files during pg_rewind.
  * Count index scans in contrib/bloom indexes in the statistics
    views, such as the pg_stat_user_indexes.idx_scan counter.
  * Fix crash when checking to see if an index's opclass options
    have changed.
  * Avoid assertion failure caused by disconnected NFA sub-graphs
    in regular expression parsing.
  * https://www.postgresql.org/about/news/p-2965/
  * https://www.postgresql.org/docs/release/14.15/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 14.16:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/14.16/
  * https://www.postgresql.org/about/news/-3015/
- Disable LLVM JIT on loongarch64</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 14.17:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/14.17/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 14.18:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/14.18/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Upgrade to 14.19:
  * https://www.postgresql.org/about/news/postgresql-176-1610-1514-1419-1322-and-18-beta-3-released-3118/
  * https://www.postgresql.org/docs/release/14.19/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1758801600">- Sync spec file from version 18.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Upgrade to 14.20:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/14.20/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 14.21:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/14.21/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 14.22 to fix two regressions in 14.21:
  * https://www.postgresql.org/docs/release/14.22/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
</package>
<package pkgid="303f67b45d4b5a358074633c50e48487001c80c8f31c34d478c37aa146a4aed07f963ac00b82f94fa68844a01698bfbde2da675dd5b520bfcfa786e4b147d90d" name="postgresql14-llvmjit" arch="s390x">
  <version epoch="0" ver="14.22" rel="106.2"/>
  <changelog author="Dominique Leuenberger &lt;dimstar@opensuse.org&gt;" date="1709208000">- Use %patch -P N instead of deprecated %patchN.</changelog>
  <changelog author="Sarah Kriesch &lt;sarah.kriesch@opensuse.org&gt;" date="1709812800">- Remove constraints file because improved memory usage for s390x</changelog>
  <changelog author="Aaron Puchert &lt;aaronpuchert@alice-dsl.net&gt;" date="1714564800">- Require LLVM &lt;= 17 for now, because LLVM 18 doesn't seem to work.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1715169600">- Upgrade to 14.12 (bsc#1224051):
  * bsc#1224038, CVE-2024-4317: Restrict visibility of pg_stats_ext
    and pg_stats_ext_exprs entries to the table owner. See the
    release notes for the steps that have to be taken to fix
    existing PostgreSQL instances.
  * Fix incompatibility with LLVM 18.
  * https://www.postgresql.org/docs/release/14.12/
- Prepare for PostgreSQL 17.
- Make sure all compilation and doc generation happens in %build.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1723291200">- Upgrade to 14.13 (bsc#1229013):
  * bsc#1229013, CVE-2024-7348 PostgreSQL relation replacement
    during pg_dump executes arbitrary SQL
  * https://www.postgresql.org/about/news/p-2910/
  * https://www.postgresql.org/docs/release/14.13/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1730808000">- Sync spec file from postgresql17.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1731499200">- Upgrade to 14.14:
  * CVE-2024-10976, bsc#1233323: Ensure cached plans are marked as
    dependent on the calling role when RLS applies to a
    non-top-level table reference.
  * CVE-2024-10977, bsc#1233325: Make libpq discard error messages
    received during SSL or GSS protocol negotiation.
  * CVE-2024-10978, bsc#1233326: Fix unintended interactions
    between SET SESSION AUTHORIZATION and SET ROLE
  * CVE-2024-10979, bsc#1233327: Prevent trusted PL/Perl code from
    changing environment variables.
  * https://www.postgresql.org/about/news/p-2955/
  * https://www.postgresql.org/docs/release/14.14/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1732017600">- Upgrade to 14.15:
  * Repair ABI break for extensions that work with struct
    ResultRelInfo.
  * Restore functionality of ALTER {ROLE|DATABASE} SET role
  * Fix cases where a logical replication slot's restart_lsn could
    go backwards.
  * Avoid deleting still-needed WAL files during pg_rewind.
  * Count index scans in contrib/bloom indexes in the statistics
    views, such as the pg_stat_user_indexes.idx_scan counter.
  * Fix crash when checking to see if an index's opclass options
    have changed.
  * Avoid assertion failure caused by disconnected NFA sub-graphs
    in regular expression parsing.
  * https://www.postgresql.org/about/news/p-2965/
  * https://www.postgresql.org/docs/release/14.15/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 14.16:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/14.16/
  * https://www.postgresql.org/about/news/-3015/
- Disable LLVM JIT on loongarch64</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 14.17:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/14.17/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 14.18:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/14.18/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Upgrade to 14.19:
  * https://www.postgresql.org/about/news/postgresql-176-1610-1514-1419-1322-and-18-beta-3-released-3118/
  * https://www.postgresql.org/docs/release/14.19/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1758801600">- Sync spec file from version 18.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Upgrade to 14.20:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/14.20/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 14.21:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/14.21/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 14.22 to fix two regressions in 14.21:
  * https://www.postgresql.org/docs/release/14.22/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
</package>
<package pkgid="413c870f72d220d2eca49a2ddcfd5c7fa742bc59bf25a05638ba7d0d1976a2c8876ad1034a6868625ab3fc7ab31b32c1137ebde4c94a2733ec855e5f1002ba6d" name="postgresql14-llvmjit" arch="x86_64">
  <version epoch="0" ver="14.23" rel="116.2"/>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1715169600">- Upgrade to 14.12 (bsc#1224051):
  * bsc#1224038, CVE-2024-4317: Restrict visibility of pg_stats_ext
    and pg_stats_ext_exprs entries to the table owner. See the
    release notes for the steps that have to be taken to fix
    existing PostgreSQL instances.
  * Fix incompatibility with LLVM 18.
  * https://www.postgresql.org/docs/release/14.12/
- Prepare for PostgreSQL 17.
- Make sure all compilation and doc generation happens in %build.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1723291200">- Upgrade to 14.13 (bsc#1229013):
  * bsc#1229013, CVE-2024-7348 PostgreSQL relation replacement
    during pg_dump executes arbitrary SQL
  * https://www.postgresql.org/about/news/p-2910/
  * https://www.postgresql.org/docs/release/14.13/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1730808000">- Sync spec file from postgresql17.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1731499200">- Upgrade to 14.14:
  * CVE-2024-10976, bsc#1233323: Ensure cached plans are marked as
    dependent on the calling role when RLS applies to a
    non-top-level table reference.
  * CVE-2024-10977, bsc#1233325: Make libpq discard error messages
    received during SSL or GSS protocol negotiation.
  * CVE-2024-10978, bsc#1233326: Fix unintended interactions
    between SET SESSION AUTHORIZATION and SET ROLE
  * CVE-2024-10979, bsc#1233327: Prevent trusted PL/Perl code from
    changing environment variables.
  * https://www.postgresql.org/about/news/p-2955/
  * https://www.postgresql.org/docs/release/14.14/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1732017600">- Upgrade to 14.15:
  * Repair ABI break for extensions that work with struct
    ResultRelInfo.
  * Restore functionality of ALTER {ROLE|DATABASE} SET role
  * Fix cases where a logical replication slot's restart_lsn could
    go backwards.
  * Avoid deleting still-needed WAL files during pg_rewind.
  * Count index scans in contrib/bloom indexes in the statistics
    views, such as the pg_stat_user_indexes.idx_scan counter.
  * Fix crash when checking to see if an index's opclass options
    have changed.
  * Avoid assertion failure caused by disconnected NFA sub-graphs
    in regular expression parsing.
  * https://www.postgresql.org/about/news/p-2965/
  * https://www.postgresql.org/docs/release/14.15/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 14.16:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/14.16/
  * https://www.postgresql.org/about/news/-3015/
- Disable LLVM JIT on loongarch64</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 14.17:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/14.17/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 14.18:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/14.18/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Upgrade to 14.19:
  * https://www.postgresql.org/about/news/postgresql-176-1610-1514-1419-1322-and-18-beta-3-released-3118/
  * https://www.postgresql.org/docs/release/14.19/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1758801600">- Sync spec file from version 18.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Upgrade to 14.20:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/14.20/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 14.21:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/14.21/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 14.22 to fix two regressions in 14.21:
  * https://www.postgresql.org/docs/release/14.22/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1774872000">- Get rid of update-alternatives for openSUSE/SLE 16.0 and newer
  to support immutable systems and transactional updates.
  (jsc#PED-14823)</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1777550400">- bsc#1263804: After dropping update-alternatives we have to
  package /usr/bin/pg_config as an actual symlink, not %ghost.
- Fix spelling of build conditionals.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1778673600">- Update to version 14.23:
  * bsc#1265172, CVE-2026-6472: ensure the user has CREATE
    privilege on the schema specified
  * bsc#1265173, CVE-2026-6473: integer overflows in
    memory-allocation calculations
  * bsc#1265174, CVE-2026-6474: Guard against malicious time zone
    names
  * bsc#1265175, CVE-2026-6475: Prevent path traversal in
    pg_basebackup and pg_rewind
  * bsc#1265177, CVE-2026-6477: Mark PQfn() as unsafe, and avoid
    using it within libpq
  * bsc#1265178, CVE-2026-6478: Use timing-safe string comparisons
    in authentication code
  * bsc#1265179, CVE-2026-6479: Prevent unbounded recursion while
    processing startup packets
  * bsc#1265181, CVE-2026-6637: Prevent SQL injection and buffer
    overruns in contrib/spi
  * https://www.postgresql.org/docs/release/14.23/</changelog>
</package>
<package pkgid="76a4139a210e419b4249cfdc20f2534680f8ce3e1059e77589ecb02b8e16324652d402f41548bd0757123e85329790727b8463c37cee7c7f18b5607121cfd9d3" name="postgresql14-llvmjit-devel" arch="aarch64">
  <version epoch="0" ver="14.22" rel="106.2"/>
  <changelog author="Dominique Leuenberger &lt;dimstar@opensuse.org&gt;" date="1709208000">- Use %patch -P N instead of deprecated %patchN.</changelog>
  <changelog author="Sarah Kriesch &lt;sarah.kriesch@opensuse.org&gt;" date="1709812800">- Remove constraints file because improved memory usage for s390x</changelog>
  <changelog author="Aaron Puchert &lt;aaronpuchert@alice-dsl.net&gt;" date="1714564800">- Require LLVM &lt;= 17 for now, because LLVM 18 doesn't seem to work.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1715169600">- Upgrade to 14.12 (bsc#1224051):
  * bsc#1224038, CVE-2024-4317: Restrict visibility of pg_stats_ext
    and pg_stats_ext_exprs entries to the table owner. See the
    release notes for the steps that have to be taken to fix
    existing PostgreSQL instances.
  * Fix incompatibility with LLVM 18.
  * https://www.postgresql.org/docs/release/14.12/
- Prepare for PostgreSQL 17.
- Make sure all compilation and doc generation happens in %build.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1723291200">- Upgrade to 14.13 (bsc#1229013):
  * bsc#1229013, CVE-2024-7348 PostgreSQL relation replacement
    during pg_dump executes arbitrary SQL
  * https://www.postgresql.org/about/news/p-2910/
  * https://www.postgresql.org/docs/release/14.13/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1730808000">- Sync spec file from postgresql17.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1731499200">- Upgrade to 14.14:
  * CVE-2024-10976, bsc#1233323: Ensure cached plans are marked as
    dependent on the calling role when RLS applies to a
    non-top-level table reference.
  * CVE-2024-10977, bsc#1233325: Make libpq discard error messages
    received during SSL or GSS protocol negotiation.
  * CVE-2024-10978, bsc#1233326: Fix unintended interactions
    between SET SESSION AUTHORIZATION and SET ROLE
  * CVE-2024-10979, bsc#1233327: Prevent trusted PL/Perl code from
    changing environment variables.
  * https://www.postgresql.org/about/news/p-2955/
  * https://www.postgresql.org/docs/release/14.14/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1732017600">- Upgrade to 14.15:
  * Repair ABI break for extensions that work with struct
    ResultRelInfo.
  * Restore functionality of ALTER {ROLE|DATABASE} SET role
  * Fix cases where a logical replication slot's restart_lsn could
    go backwards.
  * Avoid deleting still-needed WAL files during pg_rewind.
  * Count index scans in contrib/bloom indexes in the statistics
    views, such as the pg_stat_user_indexes.idx_scan counter.
  * Fix crash when checking to see if an index's opclass options
    have changed.
  * Avoid assertion failure caused by disconnected NFA sub-graphs
    in regular expression parsing.
  * https://www.postgresql.org/about/news/p-2965/
  * https://www.postgresql.org/docs/release/14.15/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 14.16:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/14.16/
  * https://www.postgresql.org/about/news/-3015/
- Disable LLVM JIT on loongarch64</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 14.17:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/14.17/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 14.18:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/14.18/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Upgrade to 14.19:
  * https://www.postgresql.org/about/news/postgresql-176-1610-1514-1419-1322-and-18-beta-3-released-3118/
  * https://www.postgresql.org/docs/release/14.19/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1758801600">- Sync spec file from version 18.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Upgrade to 14.20:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/14.20/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 14.21:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/14.21/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 14.22 to fix two regressions in 14.21:
  * https://www.postgresql.org/docs/release/14.22/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
</package>
<package pkgid="4c425d53e2df59fa5a57f323e57bd030ba1677faae8bdb1c15c21b4962555a467c1c9fd7d7ad3eaec98ec056f043c77ce35d65fb471679679a987e6c299e9e43" name="postgresql14-llvmjit-devel" arch="ppc64le">
  <version epoch="0" ver="14.22" rel="106.2"/>
  <changelog author="Dominique Leuenberger &lt;dimstar@opensuse.org&gt;" date="1709208000">- Use %patch -P N instead of deprecated %patchN.</changelog>
  <changelog author="Sarah Kriesch &lt;sarah.kriesch@opensuse.org&gt;" date="1709812800">- Remove constraints file because improved memory usage for s390x</changelog>
  <changelog author="Aaron Puchert &lt;aaronpuchert@alice-dsl.net&gt;" date="1714564800">- Require LLVM &lt;= 17 for now, because LLVM 18 doesn't seem to work.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1715169600">- Upgrade to 14.12 (bsc#1224051):
  * bsc#1224038, CVE-2024-4317: Restrict visibility of pg_stats_ext
    and pg_stats_ext_exprs entries to the table owner. See the
    release notes for the steps that have to be taken to fix
    existing PostgreSQL instances.
  * Fix incompatibility with LLVM 18.
  * https://www.postgresql.org/docs/release/14.12/
- Prepare for PostgreSQL 17.
- Make sure all compilation and doc generation happens in %build.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1723291200">- Upgrade to 14.13 (bsc#1229013):
  * bsc#1229013, CVE-2024-7348 PostgreSQL relation replacement
    during pg_dump executes arbitrary SQL
  * https://www.postgresql.org/about/news/p-2910/
  * https://www.postgresql.org/docs/release/14.13/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1730808000">- Sync spec file from postgresql17.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1731499200">- Upgrade to 14.14:
  * CVE-2024-10976, bsc#1233323: Ensure cached plans are marked as
    dependent on the calling role when RLS applies to a
    non-top-level table reference.
  * CVE-2024-10977, bsc#1233325: Make libpq discard error messages
    received during SSL or GSS protocol negotiation.
  * CVE-2024-10978, bsc#1233326: Fix unintended interactions
    between SET SESSION AUTHORIZATION and SET ROLE
  * CVE-2024-10979, bsc#1233327: Prevent trusted PL/Perl code from
    changing environment variables.
  * https://www.postgresql.org/about/news/p-2955/
  * https://www.postgresql.org/docs/release/14.14/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1732017600">- Upgrade to 14.15:
  * Repair ABI break for extensions that work with struct
    ResultRelInfo.
  * Restore functionality of ALTER {ROLE|DATABASE} SET role
  * Fix cases where a logical replication slot's restart_lsn could
    go backwards.
  * Avoid deleting still-needed WAL files during pg_rewind.
  * Count index scans in contrib/bloom indexes in the statistics
    views, such as the pg_stat_user_indexes.idx_scan counter.
  * Fix crash when checking to see if an index's opclass options
    have changed.
  * Avoid assertion failure caused by disconnected NFA sub-graphs
    in regular expression parsing.
  * https://www.postgresql.org/about/news/p-2965/
  * https://www.postgresql.org/docs/release/14.15/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 14.16:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/14.16/
  * https://www.postgresql.org/about/news/-3015/
- Disable LLVM JIT on loongarch64</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 14.17:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/14.17/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 14.18:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/14.18/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Upgrade to 14.19:
  * https://www.postgresql.org/about/news/postgresql-176-1610-1514-1419-1322-and-18-beta-3-released-3118/
  * https://www.postgresql.org/docs/release/14.19/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1758801600">- Sync spec file from version 18.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Upgrade to 14.20:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/14.20/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 14.21:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/14.21/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 14.22 to fix two regressions in 14.21:
  * https://www.postgresql.org/docs/release/14.22/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
</package>
<package pkgid="cfedd43d64d6503489489e3b74bd8c30430d89e713f03a6d941634e9ac9a872a3f2254b8cfb6d86f8b4bf34b129df4ad143d658ef320ef3929ee1d59fbc87f48" name="postgresql14-llvmjit-devel" arch="s390x">
  <version epoch="0" ver="14.22" rel="106.2"/>
  <changelog author="Dominique Leuenberger &lt;dimstar@opensuse.org&gt;" date="1709208000">- Use %patch -P N instead of deprecated %patchN.</changelog>
  <changelog author="Sarah Kriesch &lt;sarah.kriesch@opensuse.org&gt;" date="1709812800">- Remove constraints file because improved memory usage for s390x</changelog>
  <changelog author="Aaron Puchert &lt;aaronpuchert@alice-dsl.net&gt;" date="1714564800">- Require LLVM &lt;= 17 for now, because LLVM 18 doesn't seem to work.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1715169600">- Upgrade to 14.12 (bsc#1224051):
  * bsc#1224038, CVE-2024-4317: Restrict visibility of pg_stats_ext
    and pg_stats_ext_exprs entries to the table owner. See the
    release notes for the steps that have to be taken to fix
    existing PostgreSQL instances.
  * Fix incompatibility with LLVM 18.
  * https://www.postgresql.org/docs/release/14.12/
- Prepare for PostgreSQL 17.
- Make sure all compilation and doc generation happens in %build.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1723291200">- Upgrade to 14.13 (bsc#1229013):
  * bsc#1229013, CVE-2024-7348 PostgreSQL relation replacement
    during pg_dump executes arbitrary SQL
  * https://www.postgresql.org/about/news/p-2910/
  * https://www.postgresql.org/docs/release/14.13/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1730808000">- Sync spec file from postgresql17.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1731499200">- Upgrade to 14.14:
  * CVE-2024-10976, bsc#1233323: Ensure cached plans are marked as
    dependent on the calling role when RLS applies to a
    non-top-level table reference.
  * CVE-2024-10977, bsc#1233325: Make libpq discard error messages
    received during SSL or GSS protocol negotiation.
  * CVE-2024-10978, bsc#1233326: Fix unintended interactions
    between SET SESSION AUTHORIZATION and SET ROLE
  * CVE-2024-10979, bsc#1233327: Prevent trusted PL/Perl code from
    changing environment variables.
  * https://www.postgresql.org/about/news/p-2955/
  * https://www.postgresql.org/docs/release/14.14/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1732017600">- Upgrade to 14.15:
  * Repair ABI break for extensions that work with struct
    ResultRelInfo.
  * Restore functionality of ALTER {ROLE|DATABASE} SET role
  * Fix cases where a logical replication slot's restart_lsn could
    go backwards.
  * Avoid deleting still-needed WAL files during pg_rewind.
  * Count index scans in contrib/bloom indexes in the statistics
    views, such as the pg_stat_user_indexes.idx_scan counter.
  * Fix crash when checking to see if an index's opclass options
    have changed.
  * Avoid assertion failure caused by disconnected NFA sub-graphs
    in regular expression parsing.
  * https://www.postgresql.org/about/news/p-2965/
  * https://www.postgresql.org/docs/release/14.15/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 14.16:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/14.16/
  * https://www.postgresql.org/about/news/-3015/
- Disable LLVM JIT on loongarch64</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 14.17:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/14.17/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 14.18:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/14.18/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Upgrade to 14.19:
  * https://www.postgresql.org/about/news/postgresql-176-1610-1514-1419-1322-and-18-beta-3-released-3118/
  * https://www.postgresql.org/docs/release/14.19/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1758801600">- Sync spec file from version 18.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Upgrade to 14.20:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/14.20/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 14.21:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/14.21/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 14.22 to fix two regressions in 14.21:
  * https://www.postgresql.org/docs/release/14.22/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
</package>
<package pkgid="f255b2f90a0aead453fc40aaa26f9dc9a8be6923b3cbef22d9399f58b76d3abd4624d500208f8b094045c2029e5df41a256f09a01ea7b6c026b4ec7415cefa8a" name="postgresql14-llvmjit-devel" arch="x86_64">
  <version epoch="0" ver="14.23" rel="116.2"/>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1715169600">- Upgrade to 14.12 (bsc#1224051):
  * bsc#1224038, CVE-2024-4317: Restrict visibility of pg_stats_ext
    and pg_stats_ext_exprs entries to the table owner. See the
    release notes for the steps that have to be taken to fix
    existing PostgreSQL instances.
  * Fix incompatibility with LLVM 18.
  * https://www.postgresql.org/docs/release/14.12/
- Prepare for PostgreSQL 17.
- Make sure all compilation and doc generation happens in %build.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1723291200">- Upgrade to 14.13 (bsc#1229013):
  * bsc#1229013, CVE-2024-7348 PostgreSQL relation replacement
    during pg_dump executes arbitrary SQL
  * https://www.postgresql.org/about/news/p-2910/
  * https://www.postgresql.org/docs/release/14.13/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1730808000">- Sync spec file from postgresql17.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1731499200">- Upgrade to 14.14:
  * CVE-2024-10976, bsc#1233323: Ensure cached plans are marked as
    dependent on the calling role when RLS applies to a
    non-top-level table reference.
  * CVE-2024-10977, bsc#1233325: Make libpq discard error messages
    received during SSL or GSS protocol negotiation.
  * CVE-2024-10978, bsc#1233326: Fix unintended interactions
    between SET SESSION AUTHORIZATION and SET ROLE
  * CVE-2024-10979, bsc#1233327: Prevent trusted PL/Perl code from
    changing environment variables.
  * https://www.postgresql.org/about/news/p-2955/
  * https://www.postgresql.org/docs/release/14.14/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1732017600">- Upgrade to 14.15:
  * Repair ABI break for extensions that work with struct
    ResultRelInfo.
  * Restore functionality of ALTER {ROLE|DATABASE} SET role
  * Fix cases where a logical replication slot's restart_lsn could
    go backwards.
  * Avoid deleting still-needed WAL files during pg_rewind.
  * Count index scans in contrib/bloom indexes in the statistics
    views, such as the pg_stat_user_indexes.idx_scan counter.
  * Fix crash when checking to see if an index's opclass options
    have changed.
  * Avoid assertion failure caused by disconnected NFA sub-graphs
    in regular expression parsing.
  * https://www.postgresql.org/about/news/p-2965/
  * https://www.postgresql.org/docs/release/14.15/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 14.16:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/14.16/
  * https://www.postgresql.org/about/news/-3015/
- Disable LLVM JIT on loongarch64</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 14.17:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/14.17/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 14.18:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/14.18/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Upgrade to 14.19:
  * https://www.postgresql.org/about/news/postgresql-176-1610-1514-1419-1322-and-18-beta-3-released-3118/
  * https://www.postgresql.org/docs/release/14.19/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1758801600">- Sync spec file from version 18.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Upgrade to 14.20:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/14.20/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 14.21:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/14.21/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 14.22 to fix two regressions in 14.21:
  * https://www.postgresql.org/docs/release/14.22/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1774872000">- Get rid of update-alternatives for openSUSE/SLE 16.0 and newer
  to support immutable systems and transactional updates.
  (jsc#PED-14823)</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1777550400">- bsc#1263804: After dropping update-alternatives we have to
  package /usr/bin/pg_config as an actual symlink, not %ghost.
- Fix spelling of build conditionals.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1778673600">- Update to version 14.23:
  * bsc#1265172, CVE-2026-6472: ensure the user has CREATE
    privilege on the schema specified
  * bsc#1265173, CVE-2026-6473: integer overflows in
    memory-allocation calculations
  * bsc#1265174, CVE-2026-6474: Guard against malicious time zone
    names
  * bsc#1265175, CVE-2026-6475: Prevent path traversal in
    pg_basebackup and pg_rewind
  * bsc#1265177, CVE-2026-6477: Mark PQfn() as unsafe, and avoid
    using it within libpq
  * bsc#1265178, CVE-2026-6478: Use timing-safe string comparisons
    in authentication code
  * bsc#1265179, CVE-2026-6479: Prevent unbounded recursion while
    processing startup packets
  * bsc#1265181, CVE-2026-6637: Prevent SQL injection and buffer
    overruns in contrib/spi
  * https://www.postgresql.org/docs/release/14.23/</changelog>
</package>
<package pkgid="80a03f2999fbc03d6edb39040e4245c70c33fe91a46ba498ec8e33adc68017e221ecb087e7cf2c6840fe09f61a35fc420cf72b62cc80344c567af40f9ff9e1a3" name="postgresql14-plperl" arch="aarch64">
  <version epoch="0" ver="14.22" rel="106.2"/>
  <changelog author="Dominique Leuenberger &lt;dimstar@opensuse.org&gt;" date="1709208000">- Use %patch -P N instead of deprecated %patchN.</changelog>
  <changelog author="Sarah Kriesch &lt;sarah.kriesch@opensuse.org&gt;" date="1709812800">- Remove constraints file because improved memory usage for s390x</changelog>
  <changelog author="Aaron Puchert &lt;aaronpuchert@alice-dsl.net&gt;" date="1714564800">- Require LLVM &lt;= 17 for now, because LLVM 18 doesn't seem to work.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1715169600">- Upgrade to 14.12 (bsc#1224051):
  * bsc#1224038, CVE-2024-4317: Restrict visibility of pg_stats_ext
    and pg_stats_ext_exprs entries to the table owner. See the
    release notes for the steps that have to be taken to fix
    existing PostgreSQL instances.
  * Fix incompatibility with LLVM 18.
  * https://www.postgresql.org/docs/release/14.12/
- Prepare for PostgreSQL 17.
- Make sure all compilation and doc generation happens in %build.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1723291200">- Upgrade to 14.13 (bsc#1229013):
  * bsc#1229013, CVE-2024-7348 PostgreSQL relation replacement
    during pg_dump executes arbitrary SQL
  * https://www.postgresql.org/about/news/p-2910/
  * https://www.postgresql.org/docs/release/14.13/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1730808000">- Sync spec file from postgresql17.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1731499200">- Upgrade to 14.14:
  * CVE-2024-10976, bsc#1233323: Ensure cached plans are marked as
    dependent on the calling role when RLS applies to a
    non-top-level table reference.
  * CVE-2024-10977, bsc#1233325: Make libpq discard error messages
    received during SSL or GSS protocol negotiation.
  * CVE-2024-10978, bsc#1233326: Fix unintended interactions
    between SET SESSION AUTHORIZATION and SET ROLE
  * CVE-2024-10979, bsc#1233327: Prevent trusted PL/Perl code from
    changing environment variables.
  * https://www.postgresql.org/about/news/p-2955/
  * https://www.postgresql.org/docs/release/14.14/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1732017600">- Upgrade to 14.15:
  * Repair ABI break for extensions that work with struct
    ResultRelInfo.
  * Restore functionality of ALTER {ROLE|DATABASE} SET role
  * Fix cases where a logical replication slot's restart_lsn could
    go backwards.
  * Avoid deleting still-needed WAL files during pg_rewind.
  * Count index scans in contrib/bloom indexes in the statistics
    views, such as the pg_stat_user_indexes.idx_scan counter.
  * Fix crash when checking to see if an index's opclass options
    have changed.
  * Avoid assertion failure caused by disconnected NFA sub-graphs
    in regular expression parsing.
  * https://www.postgresql.org/about/news/p-2965/
  * https://www.postgresql.org/docs/release/14.15/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 14.16:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/14.16/
  * https://www.postgresql.org/about/news/-3015/
- Disable LLVM JIT on loongarch64</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 14.17:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/14.17/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 14.18:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/14.18/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Upgrade to 14.19:
  * https://www.postgresql.org/about/news/postgresql-176-1610-1514-1419-1322-and-18-beta-3-released-3118/
  * https://www.postgresql.org/docs/release/14.19/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1758801600">- Sync spec file from version 18.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Upgrade to 14.20:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/14.20/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 14.21:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/14.21/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 14.22 to fix two regressions in 14.21:
  * https://www.postgresql.org/docs/release/14.22/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
</package>
<package pkgid="8173e0615d4a972775f5a3b4e68e62824b7c1426c4586322ca92afeb3ce426f95aecda33d1ee860eb6fecbb02a4e43ae82628ccec17cc8f2b7c3375d5de340e1" name="postgresql14-plperl" arch="ppc64le">
  <version epoch="0" ver="14.22" rel="106.2"/>
  <changelog author="Dominique Leuenberger &lt;dimstar@opensuse.org&gt;" date="1709208000">- Use %patch -P N instead of deprecated %patchN.</changelog>
  <changelog author="Sarah Kriesch &lt;sarah.kriesch@opensuse.org&gt;" date="1709812800">- Remove constraints file because improved memory usage for s390x</changelog>
  <changelog author="Aaron Puchert &lt;aaronpuchert@alice-dsl.net&gt;" date="1714564800">- Require LLVM &lt;= 17 for now, because LLVM 18 doesn't seem to work.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1715169600">- Upgrade to 14.12 (bsc#1224051):
  * bsc#1224038, CVE-2024-4317: Restrict visibility of pg_stats_ext
    and pg_stats_ext_exprs entries to the table owner. See the
    release notes for the steps that have to be taken to fix
    existing PostgreSQL instances.
  * Fix incompatibility with LLVM 18.
  * https://www.postgresql.org/docs/release/14.12/
- Prepare for PostgreSQL 17.
- Make sure all compilation and doc generation happens in %build.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1723291200">- Upgrade to 14.13 (bsc#1229013):
  * bsc#1229013, CVE-2024-7348 PostgreSQL relation replacement
    during pg_dump executes arbitrary SQL
  * https://www.postgresql.org/about/news/p-2910/
  * https://www.postgresql.org/docs/release/14.13/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1730808000">- Sync spec file from postgresql17.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1731499200">- Upgrade to 14.14:
  * CVE-2024-10976, bsc#1233323: Ensure cached plans are marked as
    dependent on the calling role when RLS applies to a
    non-top-level table reference.
  * CVE-2024-10977, bsc#1233325: Make libpq discard error messages
    received during SSL or GSS protocol negotiation.
  * CVE-2024-10978, bsc#1233326: Fix unintended interactions
    between SET SESSION AUTHORIZATION and SET ROLE
  * CVE-2024-10979, bsc#1233327: Prevent trusted PL/Perl code from
    changing environment variables.
  * https://www.postgresql.org/about/news/p-2955/
  * https://www.postgresql.org/docs/release/14.14/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1732017600">- Upgrade to 14.15:
  * Repair ABI break for extensions that work with struct
    ResultRelInfo.
  * Restore functionality of ALTER {ROLE|DATABASE} SET role
  * Fix cases where a logical replication slot's restart_lsn could
    go backwards.
  * Avoid deleting still-needed WAL files during pg_rewind.
  * Count index scans in contrib/bloom indexes in the statistics
    views, such as the pg_stat_user_indexes.idx_scan counter.
  * Fix crash when checking to see if an index's opclass options
    have changed.
  * Avoid assertion failure caused by disconnected NFA sub-graphs
    in regular expression parsing.
  * https://www.postgresql.org/about/news/p-2965/
  * https://www.postgresql.org/docs/release/14.15/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 14.16:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/14.16/
  * https://www.postgresql.org/about/news/-3015/
- Disable LLVM JIT on loongarch64</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 14.17:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/14.17/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 14.18:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/14.18/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Upgrade to 14.19:
  * https://www.postgresql.org/about/news/postgresql-176-1610-1514-1419-1322-and-18-beta-3-released-3118/
  * https://www.postgresql.org/docs/release/14.19/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1758801600">- Sync spec file from version 18.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Upgrade to 14.20:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/14.20/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 14.21:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/14.21/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 14.22 to fix two regressions in 14.21:
  * https://www.postgresql.org/docs/release/14.22/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
</package>
<package pkgid="0ba3a73d8868abb82ec804cde6e486fad798eee2b0172932a329d3f5c51092782acd6ea6fff0aafb584028711968828f959a0a9b8beaa6e5debbd2d0b07ea01e" name="postgresql14-plperl" arch="s390x">
  <version epoch="0" ver="14.22" rel="106.2"/>
  <changelog author="Dominique Leuenberger &lt;dimstar@opensuse.org&gt;" date="1709208000">- Use %patch -P N instead of deprecated %patchN.</changelog>
  <changelog author="Sarah Kriesch &lt;sarah.kriesch@opensuse.org&gt;" date="1709812800">- Remove constraints file because improved memory usage for s390x</changelog>
  <changelog author="Aaron Puchert &lt;aaronpuchert@alice-dsl.net&gt;" date="1714564800">- Require LLVM &lt;= 17 for now, because LLVM 18 doesn't seem to work.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1715169600">- Upgrade to 14.12 (bsc#1224051):
  * bsc#1224038, CVE-2024-4317: Restrict visibility of pg_stats_ext
    and pg_stats_ext_exprs entries to the table owner. See the
    release notes for the steps that have to be taken to fix
    existing PostgreSQL instances.
  * Fix incompatibility with LLVM 18.
  * https://www.postgresql.org/docs/release/14.12/
- Prepare for PostgreSQL 17.
- Make sure all compilation and doc generation happens in %build.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1723291200">- Upgrade to 14.13 (bsc#1229013):
  * bsc#1229013, CVE-2024-7348 PostgreSQL relation replacement
    during pg_dump executes arbitrary SQL
  * https://www.postgresql.org/about/news/p-2910/
  * https://www.postgresql.org/docs/release/14.13/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1730808000">- Sync spec file from postgresql17.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1731499200">- Upgrade to 14.14:
  * CVE-2024-10976, bsc#1233323: Ensure cached plans are marked as
    dependent on the calling role when RLS applies to a
    non-top-level table reference.
  * CVE-2024-10977, bsc#1233325: Make libpq discard error messages
    received during SSL or GSS protocol negotiation.
  * CVE-2024-10978, bsc#1233326: Fix unintended interactions
    between SET SESSION AUTHORIZATION and SET ROLE
  * CVE-2024-10979, bsc#1233327: Prevent trusted PL/Perl code from
    changing environment variables.
  * https://www.postgresql.org/about/news/p-2955/
  * https://www.postgresql.org/docs/release/14.14/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1732017600">- Upgrade to 14.15:
  * Repair ABI break for extensions that work with struct
    ResultRelInfo.
  * Restore functionality of ALTER {ROLE|DATABASE} SET role
  * Fix cases where a logical replication slot's restart_lsn could
    go backwards.
  * Avoid deleting still-needed WAL files during pg_rewind.
  * Count index scans in contrib/bloom indexes in the statistics
    views, such as the pg_stat_user_indexes.idx_scan counter.
  * Fix crash when checking to see if an index's opclass options
    have changed.
  * Avoid assertion failure caused by disconnected NFA sub-graphs
    in regular expression parsing.
  * https://www.postgresql.org/about/news/p-2965/
  * https://www.postgresql.org/docs/release/14.15/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 14.16:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/14.16/
  * https://www.postgresql.org/about/news/-3015/
- Disable LLVM JIT on loongarch64</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 14.17:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/14.17/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 14.18:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/14.18/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Upgrade to 14.19:
  * https://www.postgresql.org/about/news/postgresql-176-1610-1514-1419-1322-and-18-beta-3-released-3118/
  * https://www.postgresql.org/docs/release/14.19/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1758801600">- Sync spec file from version 18.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Upgrade to 14.20:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/14.20/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 14.21:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/14.21/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 14.22 to fix two regressions in 14.21:
  * https://www.postgresql.org/docs/release/14.22/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
</package>
<package pkgid="848f3313d37b6a850eda4ee9000e5c02ce19fbee693fc29ec3171e9cfe4484de8a7f45d367bcb18dd15a550ceb74a05d993386e37f5832abb9398a7a6762990f" name="postgresql14-plperl" arch="x86_64">
  <version epoch="0" ver="14.23" rel="116.2"/>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1715169600">- Upgrade to 14.12 (bsc#1224051):
  * bsc#1224038, CVE-2024-4317: Restrict visibility of pg_stats_ext
    and pg_stats_ext_exprs entries to the table owner. See the
    release notes for the steps that have to be taken to fix
    existing PostgreSQL instances.
  * Fix incompatibility with LLVM 18.
  * https://www.postgresql.org/docs/release/14.12/
- Prepare for PostgreSQL 17.
- Make sure all compilation and doc generation happens in %build.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1723291200">- Upgrade to 14.13 (bsc#1229013):
  * bsc#1229013, CVE-2024-7348 PostgreSQL relation replacement
    during pg_dump executes arbitrary SQL
  * https://www.postgresql.org/about/news/p-2910/
  * https://www.postgresql.org/docs/release/14.13/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1730808000">- Sync spec file from postgresql17.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1731499200">- Upgrade to 14.14:
  * CVE-2024-10976, bsc#1233323: Ensure cached plans are marked as
    dependent on the calling role when RLS applies to a
    non-top-level table reference.
  * CVE-2024-10977, bsc#1233325: Make libpq discard error messages
    received during SSL or GSS protocol negotiation.
  * CVE-2024-10978, bsc#1233326: Fix unintended interactions
    between SET SESSION AUTHORIZATION and SET ROLE
  * CVE-2024-10979, bsc#1233327: Prevent trusted PL/Perl code from
    changing environment variables.
  * https://www.postgresql.org/about/news/p-2955/
  * https://www.postgresql.org/docs/release/14.14/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1732017600">- Upgrade to 14.15:
  * Repair ABI break for extensions that work with struct
    ResultRelInfo.
  * Restore functionality of ALTER {ROLE|DATABASE} SET role
  * Fix cases where a logical replication slot's restart_lsn could
    go backwards.
  * Avoid deleting still-needed WAL files during pg_rewind.
  * Count index scans in contrib/bloom indexes in the statistics
    views, such as the pg_stat_user_indexes.idx_scan counter.
  * Fix crash when checking to see if an index's opclass options
    have changed.
  * Avoid assertion failure caused by disconnected NFA sub-graphs
    in regular expression parsing.
  * https://www.postgresql.org/about/news/p-2965/
  * https://www.postgresql.org/docs/release/14.15/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 14.16:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/14.16/
  * https://www.postgresql.org/about/news/-3015/
- Disable LLVM JIT on loongarch64</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 14.17:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/14.17/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 14.18:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/14.18/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Upgrade to 14.19:
  * https://www.postgresql.org/about/news/postgresql-176-1610-1514-1419-1322-and-18-beta-3-released-3118/
  * https://www.postgresql.org/docs/release/14.19/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1758801600">- Sync spec file from version 18.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Upgrade to 14.20:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/14.20/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 14.21:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/14.21/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 14.22 to fix two regressions in 14.21:
  * https://www.postgresql.org/docs/release/14.22/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1774872000">- Get rid of update-alternatives for openSUSE/SLE 16.0 and newer
  to support immutable systems and transactional updates.
  (jsc#PED-14823)</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1777550400">- bsc#1263804: After dropping update-alternatives we have to
  package /usr/bin/pg_config as an actual symlink, not %ghost.
- Fix spelling of build conditionals.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1778673600">- Update to version 14.23:
  * bsc#1265172, CVE-2026-6472: ensure the user has CREATE
    privilege on the schema specified
  * bsc#1265173, CVE-2026-6473: integer overflows in
    memory-allocation calculations
  * bsc#1265174, CVE-2026-6474: Guard against malicious time zone
    names
  * bsc#1265175, CVE-2026-6475: Prevent path traversal in
    pg_basebackup and pg_rewind
  * bsc#1265177, CVE-2026-6477: Mark PQfn() as unsafe, and avoid
    using it within libpq
  * bsc#1265178, CVE-2026-6478: Use timing-safe string comparisons
    in authentication code
  * bsc#1265179, CVE-2026-6479: Prevent unbounded recursion while
    processing startup packets
  * bsc#1265181, CVE-2026-6637: Prevent SQL injection and buffer
    overruns in contrib/spi
  * https://www.postgresql.org/docs/release/14.23/</changelog>
</package>
<package pkgid="1556169167a3e368d94f71a9df8e0dd7cffd70b1e7adf135e9bbbb89bf3c1d866be8e2c3cd9ceda20b0397c9dde006b8c3beae85d233a7e92c035f5e54b19e0f" name="postgresql14-plpython" arch="aarch64">
  <version epoch="0" ver="14.22" rel="106.2"/>
  <changelog author="Dominique Leuenberger &lt;dimstar@opensuse.org&gt;" date="1709208000">- Use %patch -P N instead of deprecated %patchN.</changelog>
  <changelog author="Sarah Kriesch &lt;sarah.kriesch@opensuse.org&gt;" date="1709812800">- Remove constraints file because improved memory usage for s390x</changelog>
  <changelog author="Aaron Puchert &lt;aaronpuchert@alice-dsl.net&gt;" date="1714564800">- Require LLVM &lt;= 17 for now, because LLVM 18 doesn't seem to work.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1715169600">- Upgrade to 14.12 (bsc#1224051):
  * bsc#1224038, CVE-2024-4317: Restrict visibility of pg_stats_ext
    and pg_stats_ext_exprs entries to the table owner. See the
    release notes for the steps that have to be taken to fix
    existing PostgreSQL instances.
  * Fix incompatibility with LLVM 18.
  * https://www.postgresql.org/docs/release/14.12/
- Prepare for PostgreSQL 17.
- Make sure all compilation and doc generation happens in %build.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1723291200">- Upgrade to 14.13 (bsc#1229013):
  * bsc#1229013, CVE-2024-7348 PostgreSQL relation replacement
    during pg_dump executes arbitrary SQL
  * https://www.postgresql.org/about/news/p-2910/
  * https://www.postgresql.org/docs/release/14.13/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1730808000">- Sync spec file from postgresql17.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1731499200">- Upgrade to 14.14:
  * CVE-2024-10976, bsc#1233323: Ensure cached plans are marked as
    dependent on the calling role when RLS applies to a
    non-top-level table reference.
  * CVE-2024-10977, bsc#1233325: Make libpq discard error messages
    received during SSL or GSS protocol negotiation.
  * CVE-2024-10978, bsc#1233326: Fix unintended interactions
    between SET SESSION AUTHORIZATION and SET ROLE
  * CVE-2024-10979, bsc#1233327: Prevent trusted PL/Perl code from
    changing environment variables.
  * https://www.postgresql.org/about/news/p-2955/
  * https://www.postgresql.org/docs/release/14.14/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1732017600">- Upgrade to 14.15:
  * Repair ABI break for extensions that work with struct
    ResultRelInfo.
  * Restore functionality of ALTER {ROLE|DATABASE} SET role
  * Fix cases where a logical replication slot's restart_lsn could
    go backwards.
  * Avoid deleting still-needed WAL files during pg_rewind.
  * Count index scans in contrib/bloom indexes in the statistics
    views, such as the pg_stat_user_indexes.idx_scan counter.
  * Fix crash when checking to see if an index's opclass options
    have changed.
  * Avoid assertion failure caused by disconnected NFA sub-graphs
    in regular expression parsing.
  * https://www.postgresql.org/about/news/p-2965/
  * https://www.postgresql.org/docs/release/14.15/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 14.16:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/14.16/
  * https://www.postgresql.org/about/news/-3015/
- Disable LLVM JIT on loongarch64</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 14.17:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/14.17/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 14.18:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/14.18/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Upgrade to 14.19:
  * https://www.postgresql.org/about/news/postgresql-176-1610-1514-1419-1322-and-18-beta-3-released-3118/
  * https://www.postgresql.org/docs/release/14.19/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1758801600">- Sync spec file from version 18.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Upgrade to 14.20:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/14.20/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 14.21:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/14.21/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 14.22 to fix two regressions in 14.21:
  * https://www.postgresql.org/docs/release/14.22/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
</package>
<package pkgid="84574f404a14a8b283d323fd583c86c0e64b732f332be3cff1b13fcc1a9bc2f0755428ebdb596a901159d9212118cdae1fc45a79153778b461f70a4f1372eb59" name="postgresql14-plpython" arch="ppc64le">
  <version epoch="0" ver="14.22" rel="106.2"/>
  <changelog author="Dominique Leuenberger &lt;dimstar@opensuse.org&gt;" date="1709208000">- Use %patch -P N instead of deprecated %patchN.</changelog>
  <changelog author="Sarah Kriesch &lt;sarah.kriesch@opensuse.org&gt;" date="1709812800">- Remove constraints file because improved memory usage for s390x</changelog>
  <changelog author="Aaron Puchert &lt;aaronpuchert@alice-dsl.net&gt;" date="1714564800">- Require LLVM &lt;= 17 for now, because LLVM 18 doesn't seem to work.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1715169600">- Upgrade to 14.12 (bsc#1224051):
  * bsc#1224038, CVE-2024-4317: Restrict visibility of pg_stats_ext
    and pg_stats_ext_exprs entries to the table owner. See the
    release notes for the steps that have to be taken to fix
    existing PostgreSQL instances.
  * Fix incompatibility with LLVM 18.
  * https://www.postgresql.org/docs/release/14.12/
- Prepare for PostgreSQL 17.
- Make sure all compilation and doc generation happens in %build.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1723291200">- Upgrade to 14.13 (bsc#1229013):
  * bsc#1229013, CVE-2024-7348 PostgreSQL relation replacement
    during pg_dump executes arbitrary SQL
  * https://www.postgresql.org/about/news/p-2910/
  * https://www.postgresql.org/docs/release/14.13/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1730808000">- Sync spec file from postgresql17.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1731499200">- Upgrade to 14.14:
  * CVE-2024-10976, bsc#1233323: Ensure cached plans are marked as
    dependent on the calling role when RLS applies to a
    non-top-level table reference.
  * CVE-2024-10977, bsc#1233325: Make libpq discard error messages
    received during SSL or GSS protocol negotiation.
  * CVE-2024-10978, bsc#1233326: Fix unintended interactions
    between SET SESSION AUTHORIZATION and SET ROLE
  * CVE-2024-10979, bsc#1233327: Prevent trusted PL/Perl code from
    changing environment variables.
  * https://www.postgresql.org/about/news/p-2955/
  * https://www.postgresql.org/docs/release/14.14/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1732017600">- Upgrade to 14.15:
  * Repair ABI break for extensions that work with struct
    ResultRelInfo.
  * Restore functionality of ALTER {ROLE|DATABASE} SET role
  * Fix cases where a logical replication slot's restart_lsn could
    go backwards.
  * Avoid deleting still-needed WAL files during pg_rewind.
  * Count index scans in contrib/bloom indexes in the statistics
    views, such as the pg_stat_user_indexes.idx_scan counter.
  * Fix crash when checking to see if an index's opclass options
    have changed.
  * Avoid assertion failure caused by disconnected NFA sub-graphs
    in regular expression parsing.
  * https://www.postgresql.org/about/news/p-2965/
  * https://www.postgresql.org/docs/release/14.15/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 14.16:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/14.16/
  * https://www.postgresql.org/about/news/-3015/
- Disable LLVM JIT on loongarch64</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 14.17:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/14.17/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 14.18:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/14.18/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Upgrade to 14.19:
  * https://www.postgresql.org/about/news/postgresql-176-1610-1514-1419-1322-and-18-beta-3-released-3118/
  * https://www.postgresql.org/docs/release/14.19/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1758801600">- Sync spec file from version 18.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Upgrade to 14.20:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/14.20/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 14.21:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/14.21/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 14.22 to fix two regressions in 14.21:
  * https://www.postgresql.org/docs/release/14.22/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
</package>
<package pkgid="9c71af5578c7563827aaac014db19ffe7682e3e9902f057cb8b399f49443d96544068c61c534c77c3874a320bc5eafdcbc3b04f336074a678ebfc04ce48cb2b8" name="postgresql14-plpython" arch="s390x">
  <version epoch="0" ver="14.22" rel="106.2"/>
  <changelog author="Dominique Leuenberger &lt;dimstar@opensuse.org&gt;" date="1709208000">- Use %patch -P N instead of deprecated %patchN.</changelog>
  <changelog author="Sarah Kriesch &lt;sarah.kriesch@opensuse.org&gt;" date="1709812800">- Remove constraints file because improved memory usage for s390x</changelog>
  <changelog author="Aaron Puchert &lt;aaronpuchert@alice-dsl.net&gt;" date="1714564800">- Require LLVM &lt;= 17 for now, because LLVM 18 doesn't seem to work.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1715169600">- Upgrade to 14.12 (bsc#1224051):
  * bsc#1224038, CVE-2024-4317: Restrict visibility of pg_stats_ext
    and pg_stats_ext_exprs entries to the table owner. See the
    release notes for the steps that have to be taken to fix
    existing PostgreSQL instances.
  * Fix incompatibility with LLVM 18.
  * https://www.postgresql.org/docs/release/14.12/
- Prepare for PostgreSQL 17.
- Make sure all compilation and doc generation happens in %build.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1723291200">- Upgrade to 14.13 (bsc#1229013):
  * bsc#1229013, CVE-2024-7348 PostgreSQL relation replacement
    during pg_dump executes arbitrary SQL
  * https://www.postgresql.org/about/news/p-2910/
  * https://www.postgresql.org/docs/release/14.13/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1730808000">- Sync spec file from postgresql17.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1731499200">- Upgrade to 14.14:
  * CVE-2024-10976, bsc#1233323: Ensure cached plans are marked as
    dependent on the calling role when RLS applies to a
    non-top-level table reference.
  * CVE-2024-10977, bsc#1233325: Make libpq discard error messages
    received during SSL or GSS protocol negotiation.
  * CVE-2024-10978, bsc#1233326: Fix unintended interactions
    between SET SESSION AUTHORIZATION and SET ROLE
  * CVE-2024-10979, bsc#1233327: Prevent trusted PL/Perl code from
    changing environment variables.
  * https://www.postgresql.org/about/news/p-2955/
  * https://www.postgresql.org/docs/release/14.14/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1732017600">- Upgrade to 14.15:
  * Repair ABI break for extensions that work with struct
    ResultRelInfo.
  * Restore functionality of ALTER {ROLE|DATABASE} SET role
  * Fix cases where a logical replication slot's restart_lsn could
    go backwards.
  * Avoid deleting still-needed WAL files during pg_rewind.
  * Count index scans in contrib/bloom indexes in the statistics
    views, such as the pg_stat_user_indexes.idx_scan counter.
  * Fix crash when checking to see if an index's opclass options
    have changed.
  * Avoid assertion failure caused by disconnected NFA sub-graphs
    in regular expression parsing.
  * https://www.postgresql.org/about/news/p-2965/
  * https://www.postgresql.org/docs/release/14.15/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 14.16:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/14.16/
  * https://www.postgresql.org/about/news/-3015/
- Disable LLVM JIT on loongarch64</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 14.17:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/14.17/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 14.18:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/14.18/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Upgrade to 14.19:
  * https://www.postgresql.org/about/news/postgresql-176-1610-1514-1419-1322-and-18-beta-3-released-3118/
  * https://www.postgresql.org/docs/release/14.19/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1758801600">- Sync spec file from version 18.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Upgrade to 14.20:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/14.20/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 14.21:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/14.21/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 14.22 to fix two regressions in 14.21:
  * https://www.postgresql.org/docs/release/14.22/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
</package>
<package pkgid="8715c9ccb87fc75a30e7e7b5d5a279b53a86940c37d3b491fd4c6c93e82ab013e04f3df22778132fd53cb53e922fbc1408df758ab9edafe80ecb7a560b4e9041" name="postgresql14-plpython" arch="x86_64">
  <version epoch="0" ver="14.23" rel="116.2"/>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1715169600">- Upgrade to 14.12 (bsc#1224051):
  * bsc#1224038, CVE-2024-4317: Restrict visibility of pg_stats_ext
    and pg_stats_ext_exprs entries to the table owner. See the
    release notes for the steps that have to be taken to fix
    existing PostgreSQL instances.
  * Fix incompatibility with LLVM 18.
  * https://www.postgresql.org/docs/release/14.12/
- Prepare for PostgreSQL 17.
- Make sure all compilation and doc generation happens in %build.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1723291200">- Upgrade to 14.13 (bsc#1229013):
  * bsc#1229013, CVE-2024-7348 PostgreSQL relation replacement
    during pg_dump executes arbitrary SQL
  * https://www.postgresql.org/about/news/p-2910/
  * https://www.postgresql.org/docs/release/14.13/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1730808000">- Sync spec file from postgresql17.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1731499200">- Upgrade to 14.14:
  * CVE-2024-10976, bsc#1233323: Ensure cached plans are marked as
    dependent on the calling role when RLS applies to a
    non-top-level table reference.
  * CVE-2024-10977, bsc#1233325: Make libpq discard error messages
    received during SSL or GSS protocol negotiation.
  * CVE-2024-10978, bsc#1233326: Fix unintended interactions
    between SET SESSION AUTHORIZATION and SET ROLE
  * CVE-2024-10979, bsc#1233327: Prevent trusted PL/Perl code from
    changing environment variables.
  * https://www.postgresql.org/about/news/p-2955/
  * https://www.postgresql.org/docs/release/14.14/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1732017600">- Upgrade to 14.15:
  * Repair ABI break for extensions that work with struct
    ResultRelInfo.
  * Restore functionality of ALTER {ROLE|DATABASE} SET role
  * Fix cases where a logical replication slot's restart_lsn could
    go backwards.
  * Avoid deleting still-needed WAL files during pg_rewind.
  * Count index scans in contrib/bloom indexes in the statistics
    views, such as the pg_stat_user_indexes.idx_scan counter.
  * Fix crash when checking to see if an index's opclass options
    have changed.
  * Avoid assertion failure caused by disconnected NFA sub-graphs
    in regular expression parsing.
  * https://www.postgresql.org/about/news/p-2965/
  * https://www.postgresql.org/docs/release/14.15/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 14.16:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/14.16/
  * https://www.postgresql.org/about/news/-3015/
- Disable LLVM JIT on loongarch64</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 14.17:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/14.17/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 14.18:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/14.18/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Upgrade to 14.19:
  * https://www.postgresql.org/about/news/postgresql-176-1610-1514-1419-1322-and-18-beta-3-released-3118/
  * https://www.postgresql.org/docs/release/14.19/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1758801600">- Sync spec file from version 18.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Upgrade to 14.20:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/14.20/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 14.21:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/14.21/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 14.22 to fix two regressions in 14.21:
  * https://www.postgresql.org/docs/release/14.22/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1774872000">- Get rid of update-alternatives for openSUSE/SLE 16.0 and newer
  to support immutable systems and transactional updates.
  (jsc#PED-14823)</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1777550400">- bsc#1263804: After dropping update-alternatives we have to
  package /usr/bin/pg_config as an actual symlink, not %ghost.
- Fix spelling of build conditionals.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1778673600">- Update to version 14.23:
  * bsc#1265172, CVE-2026-6472: ensure the user has CREATE
    privilege on the schema specified
  * bsc#1265173, CVE-2026-6473: integer overflows in
    memory-allocation calculations
  * bsc#1265174, CVE-2026-6474: Guard against malicious time zone
    names
  * bsc#1265175, CVE-2026-6475: Prevent path traversal in
    pg_basebackup and pg_rewind
  * bsc#1265177, CVE-2026-6477: Mark PQfn() as unsafe, and avoid
    using it within libpq
  * bsc#1265178, CVE-2026-6478: Use timing-safe string comparisons
    in authentication code
  * bsc#1265179, CVE-2026-6479: Prevent unbounded recursion while
    processing startup packets
  * bsc#1265181, CVE-2026-6637: Prevent SQL injection and buffer
    overruns in contrib/spi
  * https://www.postgresql.org/docs/release/14.23/</changelog>
</package>
<package pkgid="c9616819533f34c2bea0eed1014a1bdcf1d1523bc6493fd6ef685d7f21aece457507c857ed24f34ebff92ad8854c55ccca40fb44a7b1a6fca20597c1bc409e8f" name="postgresql14-pltcl" arch="aarch64">
  <version epoch="0" ver="14.22" rel="106.2"/>
  <changelog author="Dominique Leuenberger &lt;dimstar@opensuse.org&gt;" date="1709208000">- Use %patch -P N instead of deprecated %patchN.</changelog>
  <changelog author="Sarah Kriesch &lt;sarah.kriesch@opensuse.org&gt;" date="1709812800">- Remove constraints file because improved memory usage for s390x</changelog>
  <changelog author="Aaron Puchert &lt;aaronpuchert@alice-dsl.net&gt;" date="1714564800">- Require LLVM &lt;= 17 for now, because LLVM 18 doesn't seem to work.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1715169600">- Upgrade to 14.12 (bsc#1224051):
  * bsc#1224038, CVE-2024-4317: Restrict visibility of pg_stats_ext
    and pg_stats_ext_exprs entries to the table owner. See the
    release notes for the steps that have to be taken to fix
    existing PostgreSQL instances.
  * Fix incompatibility with LLVM 18.
  * https://www.postgresql.org/docs/release/14.12/
- Prepare for PostgreSQL 17.
- Make sure all compilation and doc generation happens in %build.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1723291200">- Upgrade to 14.13 (bsc#1229013):
  * bsc#1229013, CVE-2024-7348 PostgreSQL relation replacement
    during pg_dump executes arbitrary SQL
  * https://www.postgresql.org/about/news/p-2910/
  * https://www.postgresql.org/docs/release/14.13/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1730808000">- Sync spec file from postgresql17.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1731499200">- Upgrade to 14.14:
  * CVE-2024-10976, bsc#1233323: Ensure cached plans are marked as
    dependent on the calling role when RLS applies to a
    non-top-level table reference.
  * CVE-2024-10977, bsc#1233325: Make libpq discard error messages
    received during SSL or GSS protocol negotiation.
  * CVE-2024-10978, bsc#1233326: Fix unintended interactions
    between SET SESSION AUTHORIZATION and SET ROLE
  * CVE-2024-10979, bsc#1233327: Prevent trusted PL/Perl code from
    changing environment variables.
  * https://www.postgresql.org/about/news/p-2955/
  * https://www.postgresql.org/docs/release/14.14/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1732017600">- Upgrade to 14.15:
  * Repair ABI break for extensions that work with struct
    ResultRelInfo.
  * Restore functionality of ALTER {ROLE|DATABASE} SET role
  * Fix cases where a logical replication slot's restart_lsn could
    go backwards.
  * Avoid deleting still-needed WAL files during pg_rewind.
  * Count index scans in contrib/bloom indexes in the statistics
    views, such as the pg_stat_user_indexes.idx_scan counter.
  * Fix crash when checking to see if an index's opclass options
    have changed.
  * Avoid assertion failure caused by disconnected NFA sub-graphs
    in regular expression parsing.
  * https://www.postgresql.org/about/news/p-2965/
  * https://www.postgresql.org/docs/release/14.15/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 14.16:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/14.16/
  * https://www.postgresql.org/about/news/-3015/
- Disable LLVM JIT on loongarch64</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 14.17:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/14.17/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 14.18:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/14.18/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Upgrade to 14.19:
  * https://www.postgresql.org/about/news/postgresql-176-1610-1514-1419-1322-and-18-beta-3-released-3118/
  * https://www.postgresql.org/docs/release/14.19/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1758801600">- Sync spec file from version 18.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Upgrade to 14.20:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/14.20/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 14.21:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/14.21/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 14.22 to fix two regressions in 14.21:
  * https://www.postgresql.org/docs/release/14.22/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
</package>
<package pkgid="a4d4289882e68b092f1b30d00da52a45a687845dc15b1947afb107bc8bd8ae26836339bed32ce3a258ab0f82cdfba5366e09fd947403a82e345c754b9d17b295" name="postgresql14-pltcl" arch="ppc64le">
  <version epoch="0" ver="14.22" rel="106.2"/>
  <changelog author="Dominique Leuenberger &lt;dimstar@opensuse.org&gt;" date="1709208000">- Use %patch -P N instead of deprecated %patchN.</changelog>
  <changelog author="Sarah Kriesch &lt;sarah.kriesch@opensuse.org&gt;" date="1709812800">- Remove constraints file because improved memory usage for s390x</changelog>
  <changelog author="Aaron Puchert &lt;aaronpuchert@alice-dsl.net&gt;" date="1714564800">- Require LLVM &lt;= 17 for now, because LLVM 18 doesn't seem to work.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1715169600">- Upgrade to 14.12 (bsc#1224051):
  * bsc#1224038, CVE-2024-4317: Restrict visibility of pg_stats_ext
    and pg_stats_ext_exprs entries to the table owner. See the
    release notes for the steps that have to be taken to fix
    existing PostgreSQL instances.
  * Fix incompatibility with LLVM 18.
  * https://www.postgresql.org/docs/release/14.12/
- Prepare for PostgreSQL 17.
- Make sure all compilation and doc generation happens in %build.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1723291200">- Upgrade to 14.13 (bsc#1229013):
  * bsc#1229013, CVE-2024-7348 PostgreSQL relation replacement
    during pg_dump executes arbitrary SQL
  * https://www.postgresql.org/about/news/p-2910/
  * https://www.postgresql.org/docs/release/14.13/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1730808000">- Sync spec file from postgresql17.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1731499200">- Upgrade to 14.14:
  * CVE-2024-10976, bsc#1233323: Ensure cached plans are marked as
    dependent on the calling role when RLS applies to a
    non-top-level table reference.
  * CVE-2024-10977, bsc#1233325: Make libpq discard error messages
    received during SSL or GSS protocol negotiation.
  * CVE-2024-10978, bsc#1233326: Fix unintended interactions
    between SET SESSION AUTHORIZATION and SET ROLE
  * CVE-2024-10979, bsc#1233327: Prevent trusted PL/Perl code from
    changing environment variables.
  * https://www.postgresql.org/about/news/p-2955/
  * https://www.postgresql.org/docs/release/14.14/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1732017600">- Upgrade to 14.15:
  * Repair ABI break for extensions that work with struct
    ResultRelInfo.
  * Restore functionality of ALTER {ROLE|DATABASE} SET role
  * Fix cases where a logical replication slot's restart_lsn could
    go backwards.
  * Avoid deleting still-needed WAL files during pg_rewind.
  * Count index scans in contrib/bloom indexes in the statistics
    views, such as the pg_stat_user_indexes.idx_scan counter.
  * Fix crash when checking to see if an index's opclass options
    have changed.
  * Avoid assertion failure caused by disconnected NFA sub-graphs
    in regular expression parsing.
  * https://www.postgresql.org/about/news/p-2965/
  * https://www.postgresql.org/docs/release/14.15/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 14.16:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/14.16/
  * https://www.postgresql.org/about/news/-3015/
- Disable LLVM JIT on loongarch64</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 14.17:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/14.17/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 14.18:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/14.18/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Upgrade to 14.19:
  * https://www.postgresql.org/about/news/postgresql-176-1610-1514-1419-1322-and-18-beta-3-released-3118/
  * https://www.postgresql.org/docs/release/14.19/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1758801600">- Sync spec file from version 18.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Upgrade to 14.20:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/14.20/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 14.21:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/14.21/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 14.22 to fix two regressions in 14.21:
  * https://www.postgresql.org/docs/release/14.22/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
</package>
<package pkgid="b7a1aee42a3bff13041f937eb3ce5da5240ec6238b81c2e34eb20957cbf567aad9b125eb1f384a46753d83b84fadf0b5194e3ac1b528ee3a9012b9c72abf0726" name="postgresql14-pltcl" arch="s390x">
  <version epoch="0" ver="14.22" rel="106.2"/>
  <changelog author="Dominique Leuenberger &lt;dimstar@opensuse.org&gt;" date="1709208000">- Use %patch -P N instead of deprecated %patchN.</changelog>
  <changelog author="Sarah Kriesch &lt;sarah.kriesch@opensuse.org&gt;" date="1709812800">- Remove constraints file because improved memory usage for s390x</changelog>
  <changelog author="Aaron Puchert &lt;aaronpuchert@alice-dsl.net&gt;" date="1714564800">- Require LLVM &lt;= 17 for now, because LLVM 18 doesn't seem to work.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1715169600">- Upgrade to 14.12 (bsc#1224051):
  * bsc#1224038, CVE-2024-4317: Restrict visibility of pg_stats_ext
    and pg_stats_ext_exprs entries to the table owner. See the
    release notes for the steps that have to be taken to fix
    existing PostgreSQL instances.
  * Fix incompatibility with LLVM 18.
  * https://www.postgresql.org/docs/release/14.12/
- Prepare for PostgreSQL 17.
- Make sure all compilation and doc generation happens in %build.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1723291200">- Upgrade to 14.13 (bsc#1229013):
  * bsc#1229013, CVE-2024-7348 PostgreSQL relation replacement
    during pg_dump executes arbitrary SQL
  * https://www.postgresql.org/about/news/p-2910/
  * https://www.postgresql.org/docs/release/14.13/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1730808000">- Sync spec file from postgresql17.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1731499200">- Upgrade to 14.14:
  * CVE-2024-10976, bsc#1233323: Ensure cached plans are marked as
    dependent on the calling role when RLS applies to a
    non-top-level table reference.
  * CVE-2024-10977, bsc#1233325: Make libpq discard error messages
    received during SSL or GSS protocol negotiation.
  * CVE-2024-10978, bsc#1233326: Fix unintended interactions
    between SET SESSION AUTHORIZATION and SET ROLE
  * CVE-2024-10979, bsc#1233327: Prevent trusted PL/Perl code from
    changing environment variables.
  * https://www.postgresql.org/about/news/p-2955/
  * https://www.postgresql.org/docs/release/14.14/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1732017600">- Upgrade to 14.15:
  * Repair ABI break for extensions that work with struct
    ResultRelInfo.
  * Restore functionality of ALTER {ROLE|DATABASE} SET role
  * Fix cases where a logical replication slot's restart_lsn could
    go backwards.
  * Avoid deleting still-needed WAL files during pg_rewind.
  * Count index scans in contrib/bloom indexes in the statistics
    views, such as the pg_stat_user_indexes.idx_scan counter.
  * Fix crash when checking to see if an index's opclass options
    have changed.
  * Avoid assertion failure caused by disconnected NFA sub-graphs
    in regular expression parsing.
  * https://www.postgresql.org/about/news/p-2965/
  * https://www.postgresql.org/docs/release/14.15/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 14.16:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/14.16/
  * https://www.postgresql.org/about/news/-3015/
- Disable LLVM JIT on loongarch64</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 14.17:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/14.17/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 14.18:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/14.18/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Upgrade to 14.19:
  * https://www.postgresql.org/about/news/postgresql-176-1610-1514-1419-1322-and-18-beta-3-released-3118/
  * https://www.postgresql.org/docs/release/14.19/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1758801600">- Sync spec file from version 18.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Upgrade to 14.20:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/14.20/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 14.21:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/14.21/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 14.22 to fix two regressions in 14.21:
  * https://www.postgresql.org/docs/release/14.22/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
</package>
<package pkgid="7e94e0055363892992384ac7fdba40319746b90715c57e04d83991a8488f1967bf5cc235d9c3e86d98171ebcf278c41cc0df85e6dd6f0b7e5dfc49dbddca23b3" name="postgresql14-pltcl" arch="x86_64">
  <version epoch="0" ver="14.23" rel="116.2"/>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1715169600">- Upgrade to 14.12 (bsc#1224051):
  * bsc#1224038, CVE-2024-4317: Restrict visibility of pg_stats_ext
    and pg_stats_ext_exprs entries to the table owner. See the
    release notes for the steps that have to be taken to fix
    existing PostgreSQL instances.
  * Fix incompatibility with LLVM 18.
  * https://www.postgresql.org/docs/release/14.12/
- Prepare for PostgreSQL 17.
- Make sure all compilation and doc generation happens in %build.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1723291200">- Upgrade to 14.13 (bsc#1229013):
  * bsc#1229013, CVE-2024-7348 PostgreSQL relation replacement
    during pg_dump executes arbitrary SQL
  * https://www.postgresql.org/about/news/p-2910/
  * https://www.postgresql.org/docs/release/14.13/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1730808000">- Sync spec file from postgresql17.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1731499200">- Upgrade to 14.14:
  * CVE-2024-10976, bsc#1233323: Ensure cached plans are marked as
    dependent on the calling role when RLS applies to a
    non-top-level table reference.
  * CVE-2024-10977, bsc#1233325: Make libpq discard error messages
    received during SSL or GSS protocol negotiation.
  * CVE-2024-10978, bsc#1233326: Fix unintended interactions
    between SET SESSION AUTHORIZATION and SET ROLE
  * CVE-2024-10979, bsc#1233327: Prevent trusted PL/Perl code from
    changing environment variables.
  * https://www.postgresql.org/about/news/p-2955/
  * https://www.postgresql.org/docs/release/14.14/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1732017600">- Upgrade to 14.15:
  * Repair ABI break for extensions that work with struct
    ResultRelInfo.
  * Restore functionality of ALTER {ROLE|DATABASE} SET role
  * Fix cases where a logical replication slot's restart_lsn could
    go backwards.
  * Avoid deleting still-needed WAL files during pg_rewind.
  * Count index scans in contrib/bloom indexes in the statistics
    views, such as the pg_stat_user_indexes.idx_scan counter.
  * Fix crash when checking to see if an index's opclass options
    have changed.
  * Avoid assertion failure caused by disconnected NFA sub-graphs
    in regular expression parsing.
  * https://www.postgresql.org/about/news/p-2965/
  * https://www.postgresql.org/docs/release/14.15/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 14.16:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/14.16/
  * https://www.postgresql.org/about/news/-3015/
- Disable LLVM JIT on loongarch64</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 14.17:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/14.17/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 14.18:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/14.18/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Upgrade to 14.19:
  * https://www.postgresql.org/about/news/postgresql-176-1610-1514-1419-1322-and-18-beta-3-released-3118/
  * https://www.postgresql.org/docs/release/14.19/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1758801600">- Sync spec file from version 18.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Upgrade to 14.20:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/14.20/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 14.21:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/14.21/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 14.22 to fix two regressions in 14.21:
  * https://www.postgresql.org/docs/release/14.22/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1774872000">- Get rid of update-alternatives for openSUSE/SLE 16.0 and newer
  to support immutable systems and transactional updates.
  (jsc#PED-14823)</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1777550400">- bsc#1263804: After dropping update-alternatives we have to
  package /usr/bin/pg_config as an actual symlink, not %ghost.
- Fix spelling of build conditionals.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1778673600">- Update to version 14.23:
  * bsc#1265172, CVE-2026-6472: ensure the user has CREATE
    privilege on the schema specified
  * bsc#1265173, CVE-2026-6473: integer overflows in
    memory-allocation calculations
  * bsc#1265174, CVE-2026-6474: Guard against malicious time zone
    names
  * bsc#1265175, CVE-2026-6475: Prevent path traversal in
    pg_basebackup and pg_rewind
  * bsc#1265177, CVE-2026-6477: Mark PQfn() as unsafe, and avoid
    using it within libpq
  * bsc#1265178, CVE-2026-6478: Use timing-safe string comparisons
    in authentication code
  * bsc#1265179, CVE-2026-6479: Prevent unbounded recursion while
    processing startup packets
  * bsc#1265181, CVE-2026-6637: Prevent SQL injection and buffer
    overruns in contrib/spi
  * https://www.postgresql.org/docs/release/14.23/</changelog>
</package>
<package pkgid="ab2be7a7da2bef9c08b8a27c2dd511fcbac8e4f9231ba484509fb55c8b98367a5a056154f125aa565cbd17561d341ee391d24408025b645d8fcad5d7a395ac78" name="postgresql14-server" arch="aarch64">
  <version epoch="0" ver="14.22" rel="106.2"/>
  <changelog author="Dominique Leuenberger &lt;dimstar@opensuse.org&gt;" date="1709208000">- Use %patch -P N instead of deprecated %patchN.</changelog>
  <changelog author="Sarah Kriesch &lt;sarah.kriesch@opensuse.org&gt;" date="1709812800">- Remove constraints file because improved memory usage for s390x</changelog>
  <changelog author="Aaron Puchert &lt;aaronpuchert@alice-dsl.net&gt;" date="1714564800">- Require LLVM &lt;= 17 for now, because LLVM 18 doesn't seem to work.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1715169600">- Upgrade to 14.12 (bsc#1224051):
  * bsc#1224038, CVE-2024-4317: Restrict visibility of pg_stats_ext
    and pg_stats_ext_exprs entries to the table owner. See the
    release notes for the steps that have to be taken to fix
    existing PostgreSQL instances.
  * Fix incompatibility with LLVM 18.
  * https://www.postgresql.org/docs/release/14.12/
- Prepare for PostgreSQL 17.
- Make sure all compilation and doc generation happens in %build.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1723291200">- Upgrade to 14.13 (bsc#1229013):
  * bsc#1229013, CVE-2024-7348 PostgreSQL relation replacement
    during pg_dump executes arbitrary SQL
  * https://www.postgresql.org/about/news/p-2910/
  * https://www.postgresql.org/docs/release/14.13/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1730808000">- Sync spec file from postgresql17.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1731499200">- Upgrade to 14.14:
  * CVE-2024-10976, bsc#1233323: Ensure cached plans are marked as
    dependent on the calling role when RLS applies to a
    non-top-level table reference.
  * CVE-2024-10977, bsc#1233325: Make libpq discard error messages
    received during SSL or GSS protocol negotiation.
  * CVE-2024-10978, bsc#1233326: Fix unintended interactions
    between SET SESSION AUTHORIZATION and SET ROLE
  * CVE-2024-10979, bsc#1233327: Prevent trusted PL/Perl code from
    changing environment variables.
  * https://www.postgresql.org/about/news/p-2955/
  * https://www.postgresql.org/docs/release/14.14/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1732017600">- Upgrade to 14.15:
  * Repair ABI break for extensions that work with struct
    ResultRelInfo.
  * Restore functionality of ALTER {ROLE|DATABASE} SET role
  * Fix cases where a logical replication slot's restart_lsn could
    go backwards.
  * Avoid deleting still-needed WAL files during pg_rewind.
  * Count index scans in contrib/bloom indexes in the statistics
    views, such as the pg_stat_user_indexes.idx_scan counter.
  * Fix crash when checking to see if an index's opclass options
    have changed.
  * Avoid assertion failure caused by disconnected NFA sub-graphs
    in regular expression parsing.
  * https://www.postgresql.org/about/news/p-2965/
  * https://www.postgresql.org/docs/release/14.15/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 14.16:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/14.16/
  * https://www.postgresql.org/about/news/-3015/
- Disable LLVM JIT on loongarch64</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 14.17:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/14.17/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 14.18:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/14.18/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Upgrade to 14.19:
  * https://www.postgresql.org/about/news/postgresql-176-1610-1514-1419-1322-and-18-beta-3-released-3118/
  * https://www.postgresql.org/docs/release/14.19/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1758801600">- Sync spec file from version 18.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Upgrade to 14.20:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/14.20/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 14.21:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/14.21/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 14.22 to fix two regressions in 14.21:
  * https://www.postgresql.org/docs/release/14.22/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
</package>
<package pkgid="2126f78107f1c4b60197c14aadd11e318dad36aca9a7ce7ec20c1749a2589674a9704ce6c67540f0d5319299b78babdd63805d702a6d651f44d0929cf763b612" name="postgresql14-server" arch="ppc64le">
  <version epoch="0" ver="14.22" rel="106.2"/>
  <changelog author="Dominique Leuenberger &lt;dimstar@opensuse.org&gt;" date="1709208000">- Use %patch -P N instead of deprecated %patchN.</changelog>
  <changelog author="Sarah Kriesch &lt;sarah.kriesch@opensuse.org&gt;" date="1709812800">- Remove constraints file because improved memory usage for s390x</changelog>
  <changelog author="Aaron Puchert &lt;aaronpuchert@alice-dsl.net&gt;" date="1714564800">- Require LLVM &lt;= 17 for now, because LLVM 18 doesn't seem to work.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1715169600">- Upgrade to 14.12 (bsc#1224051):
  * bsc#1224038, CVE-2024-4317: Restrict visibility of pg_stats_ext
    and pg_stats_ext_exprs entries to the table owner. See the
    release notes for the steps that have to be taken to fix
    existing PostgreSQL instances.
  * Fix incompatibility with LLVM 18.
  * https://www.postgresql.org/docs/release/14.12/
- Prepare for PostgreSQL 17.
- Make sure all compilation and doc generation happens in %build.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1723291200">- Upgrade to 14.13 (bsc#1229013):
  * bsc#1229013, CVE-2024-7348 PostgreSQL relation replacement
    during pg_dump executes arbitrary SQL
  * https://www.postgresql.org/about/news/p-2910/
  * https://www.postgresql.org/docs/release/14.13/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1730808000">- Sync spec file from postgresql17.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1731499200">- Upgrade to 14.14:
  * CVE-2024-10976, bsc#1233323: Ensure cached plans are marked as
    dependent on the calling role when RLS applies to a
    non-top-level table reference.
  * CVE-2024-10977, bsc#1233325: Make libpq discard error messages
    received during SSL or GSS protocol negotiation.
  * CVE-2024-10978, bsc#1233326: Fix unintended interactions
    between SET SESSION AUTHORIZATION and SET ROLE
  * CVE-2024-10979, bsc#1233327: Prevent trusted PL/Perl code from
    changing environment variables.
  * https://www.postgresql.org/about/news/p-2955/
  * https://www.postgresql.org/docs/release/14.14/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1732017600">- Upgrade to 14.15:
  * Repair ABI break for extensions that work with struct
    ResultRelInfo.
  * Restore functionality of ALTER {ROLE|DATABASE} SET role
  * Fix cases where a logical replication slot's restart_lsn could
    go backwards.
  * Avoid deleting still-needed WAL files during pg_rewind.
  * Count index scans in contrib/bloom indexes in the statistics
    views, such as the pg_stat_user_indexes.idx_scan counter.
  * Fix crash when checking to see if an index's opclass options
    have changed.
  * Avoid assertion failure caused by disconnected NFA sub-graphs
    in regular expression parsing.
  * https://www.postgresql.org/about/news/p-2965/
  * https://www.postgresql.org/docs/release/14.15/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 14.16:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/14.16/
  * https://www.postgresql.org/about/news/-3015/
- Disable LLVM JIT on loongarch64</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 14.17:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/14.17/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 14.18:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/14.18/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Upgrade to 14.19:
  * https://www.postgresql.org/about/news/postgresql-176-1610-1514-1419-1322-and-18-beta-3-released-3118/
  * https://www.postgresql.org/docs/release/14.19/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1758801600">- Sync spec file from version 18.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Upgrade to 14.20:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/14.20/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 14.21:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/14.21/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 14.22 to fix two regressions in 14.21:
  * https://www.postgresql.org/docs/release/14.22/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
</package>
<package pkgid="dcd227e6db0e0065f27075b2d14312bdb89587e994e73565c82d2b36e18e7e5c5522a54c2ccb17f71cbac5a79f2107a13ba293a8609179e231c46f4fc1a7e44b" name="postgresql14-server" arch="s390x">
  <version epoch="0" ver="14.22" rel="106.2"/>
  <changelog author="Dominique Leuenberger &lt;dimstar@opensuse.org&gt;" date="1709208000">- Use %patch -P N instead of deprecated %patchN.</changelog>
  <changelog author="Sarah Kriesch &lt;sarah.kriesch@opensuse.org&gt;" date="1709812800">- Remove constraints file because improved memory usage for s390x</changelog>
  <changelog author="Aaron Puchert &lt;aaronpuchert@alice-dsl.net&gt;" date="1714564800">- Require LLVM &lt;= 17 for now, because LLVM 18 doesn't seem to work.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1715169600">- Upgrade to 14.12 (bsc#1224051):
  * bsc#1224038, CVE-2024-4317: Restrict visibility of pg_stats_ext
    and pg_stats_ext_exprs entries to the table owner. See the
    release notes for the steps that have to be taken to fix
    existing PostgreSQL instances.
  * Fix incompatibility with LLVM 18.
  * https://www.postgresql.org/docs/release/14.12/
- Prepare for PostgreSQL 17.
- Make sure all compilation and doc generation happens in %build.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1723291200">- Upgrade to 14.13 (bsc#1229013):
  * bsc#1229013, CVE-2024-7348 PostgreSQL relation replacement
    during pg_dump executes arbitrary SQL
  * https://www.postgresql.org/about/news/p-2910/
  * https://www.postgresql.org/docs/release/14.13/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1730808000">- Sync spec file from postgresql17.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1731499200">- Upgrade to 14.14:
  * CVE-2024-10976, bsc#1233323: Ensure cached plans are marked as
    dependent on the calling role when RLS applies to a
    non-top-level table reference.
  * CVE-2024-10977, bsc#1233325: Make libpq discard error messages
    received during SSL or GSS protocol negotiation.
  * CVE-2024-10978, bsc#1233326: Fix unintended interactions
    between SET SESSION AUTHORIZATION and SET ROLE
  * CVE-2024-10979, bsc#1233327: Prevent trusted PL/Perl code from
    changing environment variables.
  * https://www.postgresql.org/about/news/p-2955/
  * https://www.postgresql.org/docs/release/14.14/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1732017600">- Upgrade to 14.15:
  * Repair ABI break for extensions that work with struct
    ResultRelInfo.
  * Restore functionality of ALTER {ROLE|DATABASE} SET role
  * Fix cases where a logical replication slot's restart_lsn could
    go backwards.
  * Avoid deleting still-needed WAL files during pg_rewind.
  * Count index scans in contrib/bloom indexes in the statistics
    views, such as the pg_stat_user_indexes.idx_scan counter.
  * Fix crash when checking to see if an index's opclass options
    have changed.
  * Avoid assertion failure caused by disconnected NFA sub-graphs
    in regular expression parsing.
  * https://www.postgresql.org/about/news/p-2965/
  * https://www.postgresql.org/docs/release/14.15/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 14.16:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/14.16/
  * https://www.postgresql.org/about/news/-3015/
- Disable LLVM JIT on loongarch64</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 14.17:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/14.17/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 14.18:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/14.18/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Upgrade to 14.19:
  * https://www.postgresql.org/about/news/postgresql-176-1610-1514-1419-1322-and-18-beta-3-released-3118/
  * https://www.postgresql.org/docs/release/14.19/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1758801600">- Sync spec file from version 18.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Upgrade to 14.20:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/14.20/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 14.21:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/14.21/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 14.22 to fix two regressions in 14.21:
  * https://www.postgresql.org/docs/release/14.22/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
</package>
<package pkgid="74be5c992c65fe2a85da418af0da61d655595425ccdc552f0748eb1d0a15bcf6fda52dc1c2cea29b0bbef0addd804d50356ac72323e10db124914bc070e3dbf3" name="postgresql14-server" arch="x86_64">
  <version epoch="0" ver="14.23" rel="116.2"/>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1715169600">- Upgrade to 14.12 (bsc#1224051):
  * bsc#1224038, CVE-2024-4317: Restrict visibility of pg_stats_ext
    and pg_stats_ext_exprs entries to the table owner. See the
    release notes for the steps that have to be taken to fix
    existing PostgreSQL instances.
  * Fix incompatibility with LLVM 18.
  * https://www.postgresql.org/docs/release/14.12/
- Prepare for PostgreSQL 17.
- Make sure all compilation and doc generation happens in %build.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1723291200">- Upgrade to 14.13 (bsc#1229013):
  * bsc#1229013, CVE-2024-7348 PostgreSQL relation replacement
    during pg_dump executes arbitrary SQL
  * https://www.postgresql.org/about/news/p-2910/
  * https://www.postgresql.org/docs/release/14.13/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1730808000">- Sync spec file from postgresql17.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1731499200">- Upgrade to 14.14:
  * CVE-2024-10976, bsc#1233323: Ensure cached plans are marked as
    dependent on the calling role when RLS applies to a
    non-top-level table reference.
  * CVE-2024-10977, bsc#1233325: Make libpq discard error messages
    received during SSL or GSS protocol negotiation.
  * CVE-2024-10978, bsc#1233326: Fix unintended interactions
    between SET SESSION AUTHORIZATION and SET ROLE
  * CVE-2024-10979, bsc#1233327: Prevent trusted PL/Perl code from
    changing environment variables.
  * https://www.postgresql.org/about/news/p-2955/
  * https://www.postgresql.org/docs/release/14.14/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1732017600">- Upgrade to 14.15:
  * Repair ABI break for extensions that work with struct
    ResultRelInfo.
  * Restore functionality of ALTER {ROLE|DATABASE} SET role
  * Fix cases where a logical replication slot's restart_lsn could
    go backwards.
  * Avoid deleting still-needed WAL files during pg_rewind.
  * Count index scans in contrib/bloom indexes in the statistics
    views, such as the pg_stat_user_indexes.idx_scan counter.
  * Fix crash when checking to see if an index's opclass options
    have changed.
  * Avoid assertion failure caused by disconnected NFA sub-graphs
    in regular expression parsing.
  * https://www.postgresql.org/about/news/p-2965/
  * https://www.postgresql.org/docs/release/14.15/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 14.16:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/14.16/
  * https://www.postgresql.org/about/news/-3015/
- Disable LLVM JIT on loongarch64</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 14.17:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/14.17/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 14.18:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/14.18/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Upgrade to 14.19:
  * https://www.postgresql.org/about/news/postgresql-176-1610-1514-1419-1322-and-18-beta-3-released-3118/
  * https://www.postgresql.org/docs/release/14.19/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1758801600">- Sync spec file from version 18.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Upgrade to 14.20:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/14.20/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 14.21:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/14.21/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 14.22 to fix two regressions in 14.21:
  * https://www.postgresql.org/docs/release/14.22/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1774872000">- Get rid of update-alternatives for openSUSE/SLE 16.0 and newer
  to support immutable systems and transactional updates.
  (jsc#PED-14823)</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1777550400">- bsc#1263804: After dropping update-alternatives we have to
  package /usr/bin/pg_config as an actual symlink, not %ghost.
- Fix spelling of build conditionals.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1778673600">- Update to version 14.23:
  * bsc#1265172, CVE-2026-6472: ensure the user has CREATE
    privilege on the schema specified
  * bsc#1265173, CVE-2026-6473: integer overflows in
    memory-allocation calculations
  * bsc#1265174, CVE-2026-6474: Guard against malicious time zone
    names
  * bsc#1265175, CVE-2026-6475: Prevent path traversal in
    pg_basebackup and pg_rewind
  * bsc#1265177, CVE-2026-6477: Mark PQfn() as unsafe, and avoid
    using it within libpq
  * bsc#1265178, CVE-2026-6478: Use timing-safe string comparisons
    in authentication code
  * bsc#1265179, CVE-2026-6479: Prevent unbounded recursion while
    processing startup packets
  * bsc#1265181, CVE-2026-6637: Prevent SQL injection and buffer
    overruns in contrib/spi
  * https://www.postgresql.org/docs/release/14.23/</changelog>
</package>
<package pkgid="faf74976dc1f89e94e61ee4dd6accde9008806d277b7917e97b9449072972ee0b7356765494ae1551e1967b95a7a1cbd8722d3122bde827f7d2133291223756d" name="postgresql14-server-devel" arch="aarch64">
  <version epoch="0" ver="14.22" rel="106.2"/>
  <changelog author="Dominique Leuenberger &lt;dimstar@opensuse.org&gt;" date="1709208000">- Use %patch -P N instead of deprecated %patchN.</changelog>
  <changelog author="Sarah Kriesch &lt;sarah.kriesch@opensuse.org&gt;" date="1709812800">- Remove constraints file because improved memory usage for s390x</changelog>
  <changelog author="Aaron Puchert &lt;aaronpuchert@alice-dsl.net&gt;" date="1714564800">- Require LLVM &lt;= 17 for now, because LLVM 18 doesn't seem to work.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1715169600">- Upgrade to 14.12 (bsc#1224051):
  * bsc#1224038, CVE-2024-4317: Restrict visibility of pg_stats_ext
    and pg_stats_ext_exprs entries to the table owner. See the
    release notes for the steps that have to be taken to fix
    existing PostgreSQL instances.
  * Fix incompatibility with LLVM 18.
  * https://www.postgresql.org/docs/release/14.12/
- Prepare for PostgreSQL 17.
- Make sure all compilation and doc generation happens in %build.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1723291200">- Upgrade to 14.13 (bsc#1229013):
  * bsc#1229013, CVE-2024-7348 PostgreSQL relation replacement
    during pg_dump executes arbitrary SQL
  * https://www.postgresql.org/about/news/p-2910/
  * https://www.postgresql.org/docs/release/14.13/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1730808000">- Sync spec file from postgresql17.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1731499200">- Upgrade to 14.14:
  * CVE-2024-10976, bsc#1233323: Ensure cached plans are marked as
    dependent on the calling role when RLS applies to a
    non-top-level table reference.
  * CVE-2024-10977, bsc#1233325: Make libpq discard error messages
    received during SSL or GSS protocol negotiation.
  * CVE-2024-10978, bsc#1233326: Fix unintended interactions
    between SET SESSION AUTHORIZATION and SET ROLE
  * CVE-2024-10979, bsc#1233327: Prevent trusted PL/Perl code from
    changing environment variables.
  * https://www.postgresql.org/about/news/p-2955/
  * https://www.postgresql.org/docs/release/14.14/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1732017600">- Upgrade to 14.15:
  * Repair ABI break for extensions that work with struct
    ResultRelInfo.
  * Restore functionality of ALTER {ROLE|DATABASE} SET role
  * Fix cases where a logical replication slot's restart_lsn could
    go backwards.
  * Avoid deleting still-needed WAL files during pg_rewind.
  * Count index scans in contrib/bloom indexes in the statistics
    views, such as the pg_stat_user_indexes.idx_scan counter.
  * Fix crash when checking to see if an index's opclass options
    have changed.
  * Avoid assertion failure caused by disconnected NFA sub-graphs
    in regular expression parsing.
  * https://www.postgresql.org/about/news/p-2965/
  * https://www.postgresql.org/docs/release/14.15/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 14.16:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/14.16/
  * https://www.postgresql.org/about/news/-3015/
- Disable LLVM JIT on loongarch64</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 14.17:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/14.17/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 14.18:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/14.18/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Upgrade to 14.19:
  * https://www.postgresql.org/about/news/postgresql-176-1610-1514-1419-1322-and-18-beta-3-released-3118/
  * https://www.postgresql.org/docs/release/14.19/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1758801600">- Sync spec file from version 18.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Upgrade to 14.20:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/14.20/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 14.21:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/14.21/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 14.22 to fix two regressions in 14.21:
  * https://www.postgresql.org/docs/release/14.22/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
</package>
<package pkgid="c3414873e7ef3c156a62d5995d597737bf8b25401c2e3f85cf223bd40f79daaa0f5c5d54ce1614a232f65d145785f9da0b603ff49091fc7f930535be737cf20e" name="postgresql14-server-devel" arch="ppc64le">
  <version epoch="0" ver="14.22" rel="106.2"/>
  <changelog author="Dominique Leuenberger &lt;dimstar@opensuse.org&gt;" date="1709208000">- Use %patch -P N instead of deprecated %patchN.</changelog>
  <changelog author="Sarah Kriesch &lt;sarah.kriesch@opensuse.org&gt;" date="1709812800">- Remove constraints file because improved memory usage for s390x</changelog>
  <changelog author="Aaron Puchert &lt;aaronpuchert@alice-dsl.net&gt;" date="1714564800">- Require LLVM &lt;= 17 for now, because LLVM 18 doesn't seem to work.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1715169600">- Upgrade to 14.12 (bsc#1224051):
  * bsc#1224038, CVE-2024-4317: Restrict visibility of pg_stats_ext
    and pg_stats_ext_exprs entries to the table owner. See the
    release notes for the steps that have to be taken to fix
    existing PostgreSQL instances.
  * Fix incompatibility with LLVM 18.
  * https://www.postgresql.org/docs/release/14.12/
- Prepare for PostgreSQL 17.
- Make sure all compilation and doc generation happens in %build.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1723291200">- Upgrade to 14.13 (bsc#1229013):
  * bsc#1229013, CVE-2024-7348 PostgreSQL relation replacement
    during pg_dump executes arbitrary SQL
  * https://www.postgresql.org/about/news/p-2910/
  * https://www.postgresql.org/docs/release/14.13/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1730808000">- Sync spec file from postgresql17.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1731499200">- Upgrade to 14.14:
  * CVE-2024-10976, bsc#1233323: Ensure cached plans are marked as
    dependent on the calling role when RLS applies to a
    non-top-level table reference.
  * CVE-2024-10977, bsc#1233325: Make libpq discard error messages
    received during SSL or GSS protocol negotiation.
  * CVE-2024-10978, bsc#1233326: Fix unintended interactions
    between SET SESSION AUTHORIZATION and SET ROLE
  * CVE-2024-10979, bsc#1233327: Prevent trusted PL/Perl code from
    changing environment variables.
  * https://www.postgresql.org/about/news/p-2955/
  * https://www.postgresql.org/docs/release/14.14/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1732017600">- Upgrade to 14.15:
  * Repair ABI break for extensions that work with struct
    ResultRelInfo.
  * Restore functionality of ALTER {ROLE|DATABASE} SET role
  * Fix cases where a logical replication slot's restart_lsn could
    go backwards.
  * Avoid deleting still-needed WAL files during pg_rewind.
  * Count index scans in contrib/bloom indexes in the statistics
    views, such as the pg_stat_user_indexes.idx_scan counter.
  * Fix crash when checking to see if an index's opclass options
    have changed.
  * Avoid assertion failure caused by disconnected NFA sub-graphs
    in regular expression parsing.
  * https://www.postgresql.org/about/news/p-2965/
  * https://www.postgresql.org/docs/release/14.15/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 14.16:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/14.16/
  * https://www.postgresql.org/about/news/-3015/
- Disable LLVM JIT on loongarch64</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 14.17:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/14.17/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 14.18:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/14.18/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Upgrade to 14.19:
  * https://www.postgresql.org/about/news/postgresql-176-1610-1514-1419-1322-and-18-beta-3-released-3118/
  * https://www.postgresql.org/docs/release/14.19/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1758801600">- Sync spec file from version 18.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Upgrade to 14.20:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/14.20/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 14.21:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/14.21/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 14.22 to fix two regressions in 14.21:
  * https://www.postgresql.org/docs/release/14.22/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
</package>
<package pkgid="700461da94ff5bab0b1a86b71606d577a8ca144c74bf1c45bf309c5e2516fa944852d3525db77d0b1b1116627a692b8d343570f9e07f693bd956375f242afd48" name="postgresql14-server-devel" arch="s390x">
  <version epoch="0" ver="14.22" rel="106.2"/>
  <changelog author="Dominique Leuenberger &lt;dimstar@opensuse.org&gt;" date="1709208000">- Use %patch -P N instead of deprecated %patchN.</changelog>
  <changelog author="Sarah Kriesch &lt;sarah.kriesch@opensuse.org&gt;" date="1709812800">- Remove constraints file because improved memory usage for s390x</changelog>
  <changelog author="Aaron Puchert &lt;aaronpuchert@alice-dsl.net&gt;" date="1714564800">- Require LLVM &lt;= 17 for now, because LLVM 18 doesn't seem to work.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1715169600">- Upgrade to 14.12 (bsc#1224051):
  * bsc#1224038, CVE-2024-4317: Restrict visibility of pg_stats_ext
    and pg_stats_ext_exprs entries to the table owner. See the
    release notes for the steps that have to be taken to fix
    existing PostgreSQL instances.
  * Fix incompatibility with LLVM 18.
  * https://www.postgresql.org/docs/release/14.12/
- Prepare for PostgreSQL 17.
- Make sure all compilation and doc generation happens in %build.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1723291200">- Upgrade to 14.13 (bsc#1229013):
  * bsc#1229013, CVE-2024-7348 PostgreSQL relation replacement
    during pg_dump executes arbitrary SQL
  * https://www.postgresql.org/about/news/p-2910/
  * https://www.postgresql.org/docs/release/14.13/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1730808000">- Sync spec file from postgresql17.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1731499200">- Upgrade to 14.14:
  * CVE-2024-10976, bsc#1233323: Ensure cached plans are marked as
    dependent on the calling role when RLS applies to a
    non-top-level table reference.
  * CVE-2024-10977, bsc#1233325: Make libpq discard error messages
    received during SSL or GSS protocol negotiation.
  * CVE-2024-10978, bsc#1233326: Fix unintended interactions
    between SET SESSION AUTHORIZATION and SET ROLE
  * CVE-2024-10979, bsc#1233327: Prevent trusted PL/Perl code from
    changing environment variables.
  * https://www.postgresql.org/about/news/p-2955/
  * https://www.postgresql.org/docs/release/14.14/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1732017600">- Upgrade to 14.15:
  * Repair ABI break for extensions that work with struct
    ResultRelInfo.
  * Restore functionality of ALTER {ROLE|DATABASE} SET role
  * Fix cases where a logical replication slot's restart_lsn could
    go backwards.
  * Avoid deleting still-needed WAL files during pg_rewind.
  * Count index scans in contrib/bloom indexes in the statistics
    views, such as the pg_stat_user_indexes.idx_scan counter.
  * Fix crash when checking to see if an index's opclass options
    have changed.
  * Avoid assertion failure caused by disconnected NFA sub-graphs
    in regular expression parsing.
  * https://www.postgresql.org/about/news/p-2965/
  * https://www.postgresql.org/docs/release/14.15/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 14.16:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/14.16/
  * https://www.postgresql.org/about/news/-3015/
- Disable LLVM JIT on loongarch64</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 14.17:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/14.17/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 14.18:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/14.18/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Upgrade to 14.19:
  * https://www.postgresql.org/about/news/postgresql-176-1610-1514-1419-1322-and-18-beta-3-released-3118/
  * https://www.postgresql.org/docs/release/14.19/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1758801600">- Sync spec file from version 18.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Upgrade to 14.20:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/14.20/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 14.21:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/14.21/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 14.22 to fix two regressions in 14.21:
  * https://www.postgresql.org/docs/release/14.22/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
</package>
<package pkgid="3b54aa65b1710da0f461dda382937d2b7f97f124827d2a62fc2506cca26aab95cb720d4bb1219692610cddbc7eefc9d3cc64b3dd2961cc47f137214d38d28c86" name="postgresql14-server-devel" arch="x86_64">
  <version epoch="0" ver="14.23" rel="116.2"/>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1715169600">- Upgrade to 14.12 (bsc#1224051):
  * bsc#1224038, CVE-2024-4317: Restrict visibility of pg_stats_ext
    and pg_stats_ext_exprs entries to the table owner. See the
    release notes for the steps that have to be taken to fix
    existing PostgreSQL instances.
  * Fix incompatibility with LLVM 18.
  * https://www.postgresql.org/docs/release/14.12/
- Prepare for PostgreSQL 17.
- Make sure all compilation and doc generation happens in %build.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1723291200">- Upgrade to 14.13 (bsc#1229013):
  * bsc#1229013, CVE-2024-7348 PostgreSQL relation replacement
    during pg_dump executes arbitrary SQL
  * https://www.postgresql.org/about/news/p-2910/
  * https://www.postgresql.org/docs/release/14.13/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1730808000">- Sync spec file from postgresql17.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1731499200">- Upgrade to 14.14:
  * CVE-2024-10976, bsc#1233323: Ensure cached plans are marked as
    dependent on the calling role when RLS applies to a
    non-top-level table reference.
  * CVE-2024-10977, bsc#1233325: Make libpq discard error messages
    received during SSL or GSS protocol negotiation.
  * CVE-2024-10978, bsc#1233326: Fix unintended interactions
    between SET SESSION AUTHORIZATION and SET ROLE
  * CVE-2024-10979, bsc#1233327: Prevent trusted PL/Perl code from
    changing environment variables.
  * https://www.postgresql.org/about/news/p-2955/
  * https://www.postgresql.org/docs/release/14.14/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1732017600">- Upgrade to 14.15:
  * Repair ABI break for extensions that work with struct
    ResultRelInfo.
  * Restore functionality of ALTER {ROLE|DATABASE} SET role
  * Fix cases where a logical replication slot's restart_lsn could
    go backwards.
  * Avoid deleting still-needed WAL files during pg_rewind.
  * Count index scans in contrib/bloom indexes in the statistics
    views, such as the pg_stat_user_indexes.idx_scan counter.
  * Fix crash when checking to see if an index's opclass options
    have changed.
  * Avoid assertion failure caused by disconnected NFA sub-graphs
    in regular expression parsing.
  * https://www.postgresql.org/about/news/p-2965/
  * https://www.postgresql.org/docs/release/14.15/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 14.16:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/14.16/
  * https://www.postgresql.org/about/news/-3015/
- Disable LLVM JIT on loongarch64</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 14.17:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/14.17/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 14.18:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/14.18/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Upgrade to 14.19:
  * https://www.postgresql.org/about/news/postgresql-176-1610-1514-1419-1322-and-18-beta-3-released-3118/
  * https://www.postgresql.org/docs/release/14.19/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1758801600">- Sync spec file from version 18.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Upgrade to 14.20:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/14.20/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 14.21:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/14.21/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 14.22 to fix two regressions in 14.21:
  * https://www.postgresql.org/docs/release/14.22/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1774872000">- Get rid of update-alternatives for openSUSE/SLE 16.0 and newer
  to support immutable systems and transactional updates.
  (jsc#PED-14823)</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1777550400">- bsc#1263804: After dropping update-alternatives we have to
  package /usr/bin/pg_config as an actual symlink, not %ghost.
- Fix spelling of build conditionals.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1778673600">- Update to version 14.23:
  * bsc#1265172, CVE-2026-6472: ensure the user has CREATE
    privilege on the schema specified
  * bsc#1265173, CVE-2026-6473: integer overflows in
    memory-allocation calculations
  * bsc#1265174, CVE-2026-6474: Guard against malicious time zone
    names
  * bsc#1265175, CVE-2026-6475: Prevent path traversal in
    pg_basebackup and pg_rewind
  * bsc#1265177, CVE-2026-6477: Mark PQfn() as unsafe, and avoid
    using it within libpq
  * bsc#1265178, CVE-2026-6478: Use timing-safe string comparisons
    in authentication code
  * bsc#1265179, CVE-2026-6479: Prevent unbounded recursion while
    processing startup packets
  * bsc#1265181, CVE-2026-6637: Prevent SQL injection and buffer
    overruns in contrib/spi
  * https://www.postgresql.org/docs/release/14.23/</changelog>
</package>
<package pkgid="7d65651eb13e21a1a3569faf36c365c824fe294df2c632e92d4d792a2c8f059c33e3663337dc5507ddae19bd66fbbf95634bfd869ba45276629b836363d83247" name="postgresql14-test" arch="aarch64">
  <version epoch="0" ver="14.22" rel="106.2"/>
  <changelog author="Dominique Leuenberger &lt;dimstar@opensuse.org&gt;" date="1709208000">- Use %patch -P N instead of deprecated %patchN.</changelog>
  <changelog author="Sarah Kriesch &lt;sarah.kriesch@opensuse.org&gt;" date="1709812800">- Remove constraints file because improved memory usage for s390x</changelog>
  <changelog author="Aaron Puchert &lt;aaronpuchert@alice-dsl.net&gt;" date="1714564800">- Require LLVM &lt;= 17 for now, because LLVM 18 doesn't seem to work.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1715169600">- Upgrade to 14.12 (bsc#1224051):
  * bsc#1224038, CVE-2024-4317: Restrict visibility of pg_stats_ext
    and pg_stats_ext_exprs entries to the table owner. See the
    release notes for the steps that have to be taken to fix
    existing PostgreSQL instances.
  * Fix incompatibility with LLVM 18.
  * https://www.postgresql.org/docs/release/14.12/
- Prepare for PostgreSQL 17.
- Make sure all compilation and doc generation happens in %build.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1723291200">- Upgrade to 14.13 (bsc#1229013):
  * bsc#1229013, CVE-2024-7348 PostgreSQL relation replacement
    during pg_dump executes arbitrary SQL
  * https://www.postgresql.org/about/news/p-2910/
  * https://www.postgresql.org/docs/release/14.13/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1730808000">- Sync spec file from postgresql17.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1731499200">- Upgrade to 14.14:
  * CVE-2024-10976, bsc#1233323: Ensure cached plans are marked as
    dependent on the calling role when RLS applies to a
    non-top-level table reference.
  * CVE-2024-10977, bsc#1233325: Make libpq discard error messages
    received during SSL or GSS protocol negotiation.
  * CVE-2024-10978, bsc#1233326: Fix unintended interactions
    between SET SESSION AUTHORIZATION and SET ROLE
  * CVE-2024-10979, bsc#1233327: Prevent trusted PL/Perl code from
    changing environment variables.
  * https://www.postgresql.org/about/news/p-2955/
  * https://www.postgresql.org/docs/release/14.14/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1732017600">- Upgrade to 14.15:
  * Repair ABI break for extensions that work with struct
    ResultRelInfo.
  * Restore functionality of ALTER {ROLE|DATABASE} SET role
  * Fix cases where a logical replication slot's restart_lsn could
    go backwards.
  * Avoid deleting still-needed WAL files during pg_rewind.
  * Count index scans in contrib/bloom indexes in the statistics
    views, such as the pg_stat_user_indexes.idx_scan counter.
  * Fix crash when checking to see if an index's opclass options
    have changed.
  * Avoid assertion failure caused by disconnected NFA sub-graphs
    in regular expression parsing.
  * https://www.postgresql.org/about/news/p-2965/
  * https://www.postgresql.org/docs/release/14.15/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 14.16:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/14.16/
  * https://www.postgresql.org/about/news/-3015/
- Disable LLVM JIT on loongarch64</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 14.17:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/14.17/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 14.18:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/14.18/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Upgrade to 14.19:
  * https://www.postgresql.org/about/news/postgresql-176-1610-1514-1419-1322-and-18-beta-3-released-3118/
  * https://www.postgresql.org/docs/release/14.19/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1758801600">- Sync spec file from version 18.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Upgrade to 14.20:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/14.20/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 14.21:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/14.21/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 14.22 to fix two regressions in 14.21:
  * https://www.postgresql.org/docs/release/14.22/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
</package>
<package pkgid="7f43701fd453603fc74714e93870331ef972945dbb5e303ce8db247c87bb25b72c4690333c09ec5d3b857701a33f1a68a078b265b2526e0e64202b61b5df4ed2" name="postgresql14-test" arch="ppc64le">
  <version epoch="0" ver="14.22" rel="106.2"/>
  <changelog author="Dominique Leuenberger &lt;dimstar@opensuse.org&gt;" date="1709208000">- Use %patch -P N instead of deprecated %patchN.</changelog>
  <changelog author="Sarah Kriesch &lt;sarah.kriesch@opensuse.org&gt;" date="1709812800">- Remove constraints file because improved memory usage for s390x</changelog>
  <changelog author="Aaron Puchert &lt;aaronpuchert@alice-dsl.net&gt;" date="1714564800">- Require LLVM &lt;= 17 for now, because LLVM 18 doesn't seem to work.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1715169600">- Upgrade to 14.12 (bsc#1224051):
  * bsc#1224038, CVE-2024-4317: Restrict visibility of pg_stats_ext
    and pg_stats_ext_exprs entries to the table owner. See the
    release notes for the steps that have to be taken to fix
    existing PostgreSQL instances.
  * Fix incompatibility with LLVM 18.
  * https://www.postgresql.org/docs/release/14.12/
- Prepare for PostgreSQL 17.
- Make sure all compilation and doc generation happens in %build.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1723291200">- Upgrade to 14.13 (bsc#1229013):
  * bsc#1229013, CVE-2024-7348 PostgreSQL relation replacement
    during pg_dump executes arbitrary SQL
  * https://www.postgresql.org/about/news/p-2910/
  * https://www.postgresql.org/docs/release/14.13/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1730808000">- Sync spec file from postgresql17.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1731499200">- Upgrade to 14.14:
  * CVE-2024-10976, bsc#1233323: Ensure cached plans are marked as
    dependent on the calling role when RLS applies to a
    non-top-level table reference.
  * CVE-2024-10977, bsc#1233325: Make libpq discard error messages
    received during SSL or GSS protocol negotiation.
  * CVE-2024-10978, bsc#1233326: Fix unintended interactions
    between SET SESSION AUTHORIZATION and SET ROLE
  * CVE-2024-10979, bsc#1233327: Prevent trusted PL/Perl code from
    changing environment variables.
  * https://www.postgresql.org/about/news/p-2955/
  * https://www.postgresql.org/docs/release/14.14/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1732017600">- Upgrade to 14.15:
  * Repair ABI break for extensions that work with struct
    ResultRelInfo.
  * Restore functionality of ALTER {ROLE|DATABASE} SET role
  * Fix cases where a logical replication slot's restart_lsn could
    go backwards.
  * Avoid deleting still-needed WAL files during pg_rewind.
  * Count index scans in contrib/bloom indexes in the statistics
    views, such as the pg_stat_user_indexes.idx_scan counter.
  * Fix crash when checking to see if an index's opclass options
    have changed.
  * Avoid assertion failure caused by disconnected NFA sub-graphs
    in regular expression parsing.
  * https://www.postgresql.org/about/news/p-2965/
  * https://www.postgresql.org/docs/release/14.15/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 14.16:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/14.16/
  * https://www.postgresql.org/about/news/-3015/
- Disable LLVM JIT on loongarch64</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 14.17:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/14.17/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 14.18:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/14.18/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Upgrade to 14.19:
  * https://www.postgresql.org/about/news/postgresql-176-1610-1514-1419-1322-and-18-beta-3-released-3118/
  * https://www.postgresql.org/docs/release/14.19/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1758801600">- Sync spec file from version 18.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Upgrade to 14.20:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/14.20/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 14.21:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/14.21/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 14.22 to fix two regressions in 14.21:
  * https://www.postgresql.org/docs/release/14.22/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
</package>
<package pkgid="43fa734b9b311e21da199e4b3da5dc3069005cb8687bcae0c20bcab632894c58b5829ee5b2295ec882d5554f084084b18615e8e7f9905674d707a5706b7ab88f" name="postgresql14-test" arch="s390x">
  <version epoch="0" ver="14.22" rel="106.2"/>
  <changelog author="Dominique Leuenberger &lt;dimstar@opensuse.org&gt;" date="1709208000">- Use %patch -P N instead of deprecated %patchN.</changelog>
  <changelog author="Sarah Kriesch &lt;sarah.kriesch@opensuse.org&gt;" date="1709812800">- Remove constraints file because improved memory usage for s390x</changelog>
  <changelog author="Aaron Puchert &lt;aaronpuchert@alice-dsl.net&gt;" date="1714564800">- Require LLVM &lt;= 17 for now, because LLVM 18 doesn't seem to work.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1715169600">- Upgrade to 14.12 (bsc#1224051):
  * bsc#1224038, CVE-2024-4317: Restrict visibility of pg_stats_ext
    and pg_stats_ext_exprs entries to the table owner. See the
    release notes for the steps that have to be taken to fix
    existing PostgreSQL instances.
  * Fix incompatibility with LLVM 18.
  * https://www.postgresql.org/docs/release/14.12/
- Prepare for PostgreSQL 17.
- Make sure all compilation and doc generation happens in %build.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1723291200">- Upgrade to 14.13 (bsc#1229013):
  * bsc#1229013, CVE-2024-7348 PostgreSQL relation replacement
    during pg_dump executes arbitrary SQL
  * https://www.postgresql.org/about/news/p-2910/
  * https://www.postgresql.org/docs/release/14.13/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1730808000">- Sync spec file from postgresql17.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1731499200">- Upgrade to 14.14:
  * CVE-2024-10976, bsc#1233323: Ensure cached plans are marked as
    dependent on the calling role when RLS applies to a
    non-top-level table reference.
  * CVE-2024-10977, bsc#1233325: Make libpq discard error messages
    received during SSL or GSS protocol negotiation.
  * CVE-2024-10978, bsc#1233326: Fix unintended interactions
    between SET SESSION AUTHORIZATION and SET ROLE
  * CVE-2024-10979, bsc#1233327: Prevent trusted PL/Perl code from
    changing environment variables.
  * https://www.postgresql.org/about/news/p-2955/
  * https://www.postgresql.org/docs/release/14.14/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1732017600">- Upgrade to 14.15:
  * Repair ABI break for extensions that work with struct
    ResultRelInfo.
  * Restore functionality of ALTER {ROLE|DATABASE} SET role
  * Fix cases where a logical replication slot's restart_lsn could
    go backwards.
  * Avoid deleting still-needed WAL files during pg_rewind.
  * Count index scans in contrib/bloom indexes in the statistics
    views, such as the pg_stat_user_indexes.idx_scan counter.
  * Fix crash when checking to see if an index's opclass options
    have changed.
  * Avoid assertion failure caused by disconnected NFA sub-graphs
    in regular expression parsing.
  * https://www.postgresql.org/about/news/p-2965/
  * https://www.postgresql.org/docs/release/14.15/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 14.16:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/14.16/
  * https://www.postgresql.org/about/news/-3015/
- Disable LLVM JIT on loongarch64</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 14.17:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/14.17/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 14.18:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/14.18/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Upgrade to 14.19:
  * https://www.postgresql.org/about/news/postgresql-176-1610-1514-1419-1322-and-18-beta-3-released-3118/
  * https://www.postgresql.org/docs/release/14.19/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1758801600">- Sync spec file from version 18.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Upgrade to 14.20:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/14.20/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 14.21:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/14.21/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 14.22 to fix two regressions in 14.21:
  * https://www.postgresql.org/docs/release/14.22/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
</package>
<package pkgid="f128292a28eb8810cd22c796c9376ff92f146319152e0185bfbe56e8604a56da7a6f09fce9415e890febebd266674462892b0902bf39d8528ff2cf45b1d8132e" name="postgresql14-test" arch="x86_64">
  <version epoch="0" ver="14.23" rel="116.2"/>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1715169600">- Upgrade to 14.12 (bsc#1224051):
  * bsc#1224038, CVE-2024-4317: Restrict visibility of pg_stats_ext
    and pg_stats_ext_exprs entries to the table owner. See the
    release notes for the steps that have to be taken to fix
    existing PostgreSQL instances.
  * Fix incompatibility with LLVM 18.
  * https://www.postgresql.org/docs/release/14.12/
- Prepare for PostgreSQL 17.
- Make sure all compilation and doc generation happens in %build.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1723291200">- Upgrade to 14.13 (bsc#1229013):
  * bsc#1229013, CVE-2024-7348 PostgreSQL relation replacement
    during pg_dump executes arbitrary SQL
  * https://www.postgresql.org/about/news/p-2910/
  * https://www.postgresql.org/docs/release/14.13/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1730808000">- Sync spec file from postgresql17.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1731499200">- Upgrade to 14.14:
  * CVE-2024-10976, bsc#1233323: Ensure cached plans are marked as
    dependent on the calling role when RLS applies to a
    non-top-level table reference.
  * CVE-2024-10977, bsc#1233325: Make libpq discard error messages
    received during SSL or GSS protocol negotiation.
  * CVE-2024-10978, bsc#1233326: Fix unintended interactions
    between SET SESSION AUTHORIZATION and SET ROLE
  * CVE-2024-10979, bsc#1233327: Prevent trusted PL/Perl code from
    changing environment variables.
  * https://www.postgresql.org/about/news/p-2955/
  * https://www.postgresql.org/docs/release/14.14/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1732017600">- Upgrade to 14.15:
  * Repair ABI break for extensions that work with struct
    ResultRelInfo.
  * Restore functionality of ALTER {ROLE|DATABASE} SET role
  * Fix cases where a logical replication slot's restart_lsn could
    go backwards.
  * Avoid deleting still-needed WAL files during pg_rewind.
  * Count index scans in contrib/bloom indexes in the statistics
    views, such as the pg_stat_user_indexes.idx_scan counter.
  * Fix crash when checking to see if an index's opclass options
    have changed.
  * Avoid assertion failure caused by disconnected NFA sub-graphs
    in regular expression parsing.
  * https://www.postgresql.org/about/news/p-2965/
  * https://www.postgresql.org/docs/release/14.15/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 14.16:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/14.16/
  * https://www.postgresql.org/about/news/-3015/
- Disable LLVM JIT on loongarch64</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 14.17:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/14.17/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 14.18:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/14.18/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Upgrade to 14.19:
  * https://www.postgresql.org/about/news/postgresql-176-1610-1514-1419-1322-and-18-beta-3-released-3118/
  * https://www.postgresql.org/docs/release/14.19/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1758801600">- Sync spec file from version 18.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Upgrade to 14.20:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/14.20/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 14.21:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/14.21/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 14.22 to fix two regressions in 14.21:
  * https://www.postgresql.org/docs/release/14.22/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1774872000">- Get rid of update-alternatives for openSUSE/SLE 16.0 and newer
  to support immutable systems and transactional updates.
  (jsc#PED-14823)</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1777550400">- bsc#1263804: After dropping update-alternatives we have to
  package /usr/bin/pg_config as an actual symlink, not %ghost.
- Fix spelling of build conditionals.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1778673600">- Update to version 14.23:
  * bsc#1265172, CVE-2026-6472: ensure the user has CREATE
    privilege on the schema specified
  * bsc#1265173, CVE-2026-6473: integer overflows in
    memory-allocation calculations
  * bsc#1265174, CVE-2026-6474: Guard against malicious time zone
    names
  * bsc#1265175, CVE-2026-6475: Prevent path traversal in
    pg_basebackup and pg_rewind
  * bsc#1265177, CVE-2026-6477: Mark PQfn() as unsafe, and avoid
    using it within libpq
  * bsc#1265178, CVE-2026-6478: Use timing-safe string comparisons
    in authentication code
  * bsc#1265179, CVE-2026-6479: Prevent unbounded recursion while
    processing startup packets
  * bsc#1265181, CVE-2026-6637: Prevent SQL injection and buffer
    overruns in contrib/spi
  * https://www.postgresql.org/docs/release/14.23/</changelog>
</package>
<package pkgid="6a407024efb74d0398c0b87390e97b2a439b199cd178d7e4ca4e79df7bd3e60dd95d46465706c2f3c0174a488ac02fb8e78077920132e05a4a3dee6ebe5d4879" name="postgresql15" arch="ppc64le">
  <version epoch="0" ver="15.17" rel="86.1"/>
  <changelog author="Dominique Leuenberger &lt;dimstar@opensuse.org&gt;" date="1709208000">- Use %patch -P N instead of deprecated %patchN.</changelog>
  <changelog author="Sarah Kriesch &lt;sarah.kriesch@opensuse.org&gt;" date="1709812800">- Remove constraints file because improved memory usage for s390x</changelog>
  <changelog author="Aaron Puchert &lt;aaronpuchert@alice-dsl.net&gt;" date="1710244800">- Require LLVM &lt;= 17 for now, because LLVM 18 doesn't seem to work.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1715169600">- Upgrade to 15.7 (bsc#1224051):
  * bsc#1224038, CVE-2024-4317: Restrict visibility of pg_stats_ext
    and pg_stats_ext_exprs entries to the table owner. See the
    release notes for the steps that have to be taken to fix
    existing PostgreSQL instances.
  * Fix incompatibility with LLVM 18.
  * https://www.postgresql.org/docs/release/15.7/
- Prepare for PostgreSQL 17.
- Make sure all compilation and doc generation happens in %build.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1723291200">- Upgrade to 15.8 (bsc#1229013):
  * bsc#1229013, CVE-2024-7348 PostgreSQL relation replacement
    during pg_dump executes arbitrary SQL
  * https://www.postgresql.org/about/news/p-2910/
  * https://www.postgresql.org/docs/release/15.8/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1730808000">- Sync spec file from postgresql17.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1731499200">- Upgrade to 15.9:
  * CVE-2024-10976, bsc#1233323: Ensure cached plans are marked as
    dependent on the calling role when RLS applies to a
    non-top-level table reference.
  * CVE-2024-10977, bsc#1233325: Make libpq discard error messages
    received during SSL or GSS protocol negotiation.
  * CVE-2024-10978, bsc#1233326: Fix unintended interactions
    between SET SESSION AUTHORIZATION and SET ROLE
  * CVE-2024-10979, bsc#1233327: Prevent trusted PL/Perl code from
    changing environment variables.
  * https://www.postgresql.org/about/news/p-2955/
  * https://www.postgresql.org/docs/release/15.9/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1732017600">- Upgrade to 15.10
  * Repair ABI break for extensions that work with struct
    ResultRelInfo.
  * Restore functionality of ALTER {ROLE|DATABASE} SET role.
  * Fix cases where a logical replication slot's restart_lsn could
    go backwards.
  * Avoid deleting still-needed WAL files during pg_rewind.
  * Fix race conditions associated with dropping shared statistics
    entries.
  * Count index scans in contrib/bloom indexes in the statistics
    views, such as the pg_stat_user_indexes.idx_scan counter.
  * Fix crash when checking to see if an index's opclass options
    have changed.
  * Avoid assertion failure caused by disconnected NFA sub-graphs
    in regular expression parsing.
  * https://www.postgresql.org/about/news/p-2965/
  * https://www.postgresql.org/docs/release/15.10/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 15.11:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/15.11/
  * https://www.postgresql.org/about/news/-3015/
- Disable LLVM JIT on loongarch64</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 15.12:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/15.12/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 15.13:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/15.13/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Upgrade to 15.14:
  * https://www.postgresql.org/about/news/postgresql-176-1610-1514-1419-1322-and-18-beta-3-released-3118/
  * https://www.postgresql.org/docs/release/15.14/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1758801600">- Sync spec file from version 18.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Upgrade to 15.15:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/15.15/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 15.16:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/15.16/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 15.17 to fix two regressions in 15.16:
  * https://www.postgresql.org/docs/release/15.17/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
</package>
<package pkgid="d844a14c84f5b49388e0bf660cb2f8c0d47fc13351d930ff16b20bdb77c2ded7c8f51e4c38b4747e9af7eaaa1767f75363eb90b7e379bcb64165b6f1a5bd7b93" name="postgresql15" arch="src">
  <version epoch="0" ver="15.17" rel="86.1"/>
  <changelog author="Dominique Leuenberger &lt;dimstar@opensuse.org&gt;" date="1709208000">- Use %patch -P N instead of deprecated %patchN.</changelog>
  <changelog author="Sarah Kriesch &lt;sarah.kriesch@opensuse.org&gt;" date="1709812800">- Remove constraints file because improved memory usage for s390x</changelog>
  <changelog author="Aaron Puchert &lt;aaronpuchert@alice-dsl.net&gt;" date="1710244800">- Require LLVM &lt;= 17 for now, because LLVM 18 doesn't seem to work.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1715169600">- Upgrade to 15.7 (bsc#1224051):
  * bsc#1224038, CVE-2024-4317: Restrict visibility of pg_stats_ext
    and pg_stats_ext_exprs entries to the table owner. See the
    release notes for the steps that have to be taken to fix
    existing PostgreSQL instances.
  * Fix incompatibility with LLVM 18.
  * https://www.postgresql.org/docs/release/15.7/
- Prepare for PostgreSQL 17.
- Make sure all compilation and doc generation happens in %build.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1723291200">- Upgrade to 15.8 (bsc#1229013):
  * bsc#1229013, CVE-2024-7348 PostgreSQL relation replacement
    during pg_dump executes arbitrary SQL
  * https://www.postgresql.org/about/news/p-2910/
  * https://www.postgresql.org/docs/release/15.8/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1730808000">- Sync spec file from postgresql17.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1731499200">- Upgrade to 15.9:
  * CVE-2024-10976, bsc#1233323: Ensure cached plans are marked as
    dependent on the calling role when RLS applies to a
    non-top-level table reference.
  * CVE-2024-10977, bsc#1233325: Make libpq discard error messages
    received during SSL or GSS protocol negotiation.
  * CVE-2024-10978, bsc#1233326: Fix unintended interactions
    between SET SESSION AUTHORIZATION and SET ROLE
  * CVE-2024-10979, bsc#1233327: Prevent trusted PL/Perl code from
    changing environment variables.
  * https://www.postgresql.org/about/news/p-2955/
  * https://www.postgresql.org/docs/release/15.9/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1732017600">- Upgrade to 15.10
  * Repair ABI break for extensions that work with struct
    ResultRelInfo.
  * Restore functionality of ALTER {ROLE|DATABASE} SET role.
  * Fix cases where a logical replication slot's restart_lsn could
    go backwards.
  * Avoid deleting still-needed WAL files during pg_rewind.
  * Fix race conditions associated with dropping shared statistics
    entries.
  * Count index scans in contrib/bloom indexes in the statistics
    views, such as the pg_stat_user_indexes.idx_scan counter.
  * Fix crash when checking to see if an index's opclass options
    have changed.
  * Avoid assertion failure caused by disconnected NFA sub-graphs
    in regular expression parsing.
  * https://www.postgresql.org/about/news/p-2965/
  * https://www.postgresql.org/docs/release/15.10/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 15.11:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/15.11/
  * https://www.postgresql.org/about/news/-3015/
- Disable LLVM JIT on loongarch64</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 15.12:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/15.12/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 15.13:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/15.13/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Upgrade to 15.14:
  * https://www.postgresql.org/about/news/postgresql-176-1610-1514-1419-1322-and-18-beta-3-released-3118/
  * https://www.postgresql.org/docs/release/15.14/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1758801600">- Sync spec file from version 18.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Upgrade to 15.15:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/15.15/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 15.16:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/15.16/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 15.17 to fix two regressions in 15.16:
  * https://www.postgresql.org/docs/release/15.17/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
</package>
<package pkgid="7e84388c1877a9b05d52b1911ecd891bc767ac85d38d9db4539e362adc7c1fedb1a66b7369d3e3cb242a47441bb28361ce3b7e418dff0f1ad31cdba38979de66" name="postgresql15" arch="aarch64">
  <version epoch="0" ver="15.17" rel="87.2"/>
  <changelog author="Dominique Leuenberger &lt;dimstar@opensuse.org&gt;" date="1709208000">- Use %patch -P N instead of deprecated %patchN.</changelog>
  <changelog author="Sarah Kriesch &lt;sarah.kriesch@opensuse.org&gt;" date="1709812800">- Remove constraints file because improved memory usage for s390x</changelog>
  <changelog author="Aaron Puchert &lt;aaronpuchert@alice-dsl.net&gt;" date="1710244800">- Require LLVM &lt;= 17 for now, because LLVM 18 doesn't seem to work.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1715169600">- Upgrade to 15.7 (bsc#1224051):
  * bsc#1224038, CVE-2024-4317: Restrict visibility of pg_stats_ext
    and pg_stats_ext_exprs entries to the table owner. See the
    release notes for the steps that have to be taken to fix
    existing PostgreSQL instances.
  * Fix incompatibility with LLVM 18.
  * https://www.postgresql.org/docs/release/15.7/
- Prepare for PostgreSQL 17.
- Make sure all compilation and doc generation happens in %build.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1723291200">- Upgrade to 15.8 (bsc#1229013):
  * bsc#1229013, CVE-2024-7348 PostgreSQL relation replacement
    during pg_dump executes arbitrary SQL
  * https://www.postgresql.org/about/news/p-2910/
  * https://www.postgresql.org/docs/release/15.8/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1730808000">- Sync spec file from postgresql17.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1731499200">- Upgrade to 15.9:
  * CVE-2024-10976, bsc#1233323: Ensure cached plans are marked as
    dependent on the calling role when RLS applies to a
    non-top-level table reference.
  * CVE-2024-10977, bsc#1233325: Make libpq discard error messages
    received during SSL or GSS protocol negotiation.
  * CVE-2024-10978, bsc#1233326: Fix unintended interactions
    between SET SESSION AUTHORIZATION and SET ROLE
  * CVE-2024-10979, bsc#1233327: Prevent trusted PL/Perl code from
    changing environment variables.
  * https://www.postgresql.org/about/news/p-2955/
  * https://www.postgresql.org/docs/release/15.9/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1732017600">- Upgrade to 15.10
  * Repair ABI break for extensions that work with struct
    ResultRelInfo.
  * Restore functionality of ALTER {ROLE|DATABASE} SET role.
  * Fix cases where a logical replication slot's restart_lsn could
    go backwards.
  * Avoid deleting still-needed WAL files during pg_rewind.
  * Fix race conditions associated with dropping shared statistics
    entries.
  * Count index scans in contrib/bloom indexes in the statistics
    views, such as the pg_stat_user_indexes.idx_scan counter.
  * Fix crash when checking to see if an index's opclass options
    have changed.
  * Avoid assertion failure caused by disconnected NFA sub-graphs
    in regular expression parsing.
  * https://www.postgresql.org/about/news/p-2965/
  * https://www.postgresql.org/docs/release/15.10/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 15.11:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/15.11/
  * https://www.postgresql.org/about/news/-3015/
- Disable LLVM JIT on loongarch64</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 15.12:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/15.12/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 15.13:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/15.13/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Upgrade to 15.14:
  * https://www.postgresql.org/about/news/postgresql-176-1610-1514-1419-1322-and-18-beta-3-released-3118/
  * https://www.postgresql.org/docs/release/15.14/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1758801600">- Sync spec file from version 18.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Upgrade to 15.15:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/15.15/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 15.16:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/15.16/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 15.17 to fix two regressions in 15.16:
  * https://www.postgresql.org/docs/release/15.17/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
</package>
<package pkgid="1093a19b18706927251157eb9654b806c45e7061afa98f6d02f7903616ae8f754e847de6599554225c914f247d6635fdf4a31253d344955ac8f0513ea475bae9" name="postgresql15" arch="s390x">
  <version epoch="0" ver="15.17" rel="87.2"/>
  <changelog author="Dominique Leuenberger &lt;dimstar@opensuse.org&gt;" date="1709208000">- Use %patch -P N instead of deprecated %patchN.</changelog>
  <changelog author="Sarah Kriesch &lt;sarah.kriesch@opensuse.org&gt;" date="1709812800">- Remove constraints file because improved memory usage for s390x</changelog>
  <changelog author="Aaron Puchert &lt;aaronpuchert@alice-dsl.net&gt;" date="1710244800">- Require LLVM &lt;= 17 for now, because LLVM 18 doesn't seem to work.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1715169600">- Upgrade to 15.7 (bsc#1224051):
  * bsc#1224038, CVE-2024-4317: Restrict visibility of pg_stats_ext
    and pg_stats_ext_exprs entries to the table owner. See the
    release notes for the steps that have to be taken to fix
    existing PostgreSQL instances.
  * Fix incompatibility with LLVM 18.
  * https://www.postgresql.org/docs/release/15.7/
- Prepare for PostgreSQL 17.
- Make sure all compilation and doc generation happens in %build.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1723291200">- Upgrade to 15.8 (bsc#1229013):
  * bsc#1229013, CVE-2024-7348 PostgreSQL relation replacement
    during pg_dump executes arbitrary SQL
  * https://www.postgresql.org/about/news/p-2910/
  * https://www.postgresql.org/docs/release/15.8/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1730808000">- Sync spec file from postgresql17.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1731499200">- Upgrade to 15.9:
  * CVE-2024-10976, bsc#1233323: Ensure cached plans are marked as
    dependent on the calling role when RLS applies to a
    non-top-level table reference.
  * CVE-2024-10977, bsc#1233325: Make libpq discard error messages
    received during SSL or GSS protocol negotiation.
  * CVE-2024-10978, bsc#1233326: Fix unintended interactions
    between SET SESSION AUTHORIZATION and SET ROLE
  * CVE-2024-10979, bsc#1233327: Prevent trusted PL/Perl code from
    changing environment variables.
  * https://www.postgresql.org/about/news/p-2955/
  * https://www.postgresql.org/docs/release/15.9/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1732017600">- Upgrade to 15.10
  * Repair ABI break for extensions that work with struct
    ResultRelInfo.
  * Restore functionality of ALTER {ROLE|DATABASE} SET role.
  * Fix cases where a logical replication slot's restart_lsn could
    go backwards.
  * Avoid deleting still-needed WAL files during pg_rewind.
  * Fix race conditions associated with dropping shared statistics
    entries.
  * Count index scans in contrib/bloom indexes in the statistics
    views, such as the pg_stat_user_indexes.idx_scan counter.
  * Fix crash when checking to see if an index's opclass options
    have changed.
  * Avoid assertion failure caused by disconnected NFA sub-graphs
    in regular expression parsing.
  * https://www.postgresql.org/about/news/p-2965/
  * https://www.postgresql.org/docs/release/15.10/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 15.11:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/15.11/
  * https://www.postgresql.org/about/news/-3015/
- Disable LLVM JIT on loongarch64</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 15.12:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/15.12/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 15.13:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/15.13/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Upgrade to 15.14:
  * https://www.postgresql.org/about/news/postgresql-176-1610-1514-1419-1322-and-18-beta-3-released-3118/
  * https://www.postgresql.org/docs/release/15.14/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1758801600">- Sync spec file from version 18.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Upgrade to 15.15:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/15.15/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 15.16:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/15.16/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 15.17 to fix two regressions in 15.16:
  * https://www.postgresql.org/docs/release/15.17/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
</package>
<package pkgid="2b4572d5a0df3d55b5c59000d2ae51ff5ed3a5e25cbb67ad70ce967cb580988692edc130d10c4bd5c27bd654fdb27e414b511beb8d8b9090d30700264a452439" name="postgresql15" arch="src">
  <version epoch="0" ver="15.17" rel="87.2"/>
  <changelog author="Dominique Leuenberger &lt;dimstar@opensuse.org&gt;" date="1709208000">- Use %patch -P N instead of deprecated %patchN.</changelog>
  <changelog author="Sarah Kriesch &lt;sarah.kriesch@opensuse.org&gt;" date="1709812800">- Remove constraints file because improved memory usage for s390x</changelog>
  <changelog author="Aaron Puchert &lt;aaronpuchert@alice-dsl.net&gt;" date="1710244800">- Require LLVM &lt;= 17 for now, because LLVM 18 doesn't seem to work.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1715169600">- Upgrade to 15.7 (bsc#1224051):
  * bsc#1224038, CVE-2024-4317: Restrict visibility of pg_stats_ext
    and pg_stats_ext_exprs entries to the table owner. See the
    release notes for the steps that have to be taken to fix
    existing PostgreSQL instances.
  * Fix incompatibility with LLVM 18.
  * https://www.postgresql.org/docs/release/15.7/
- Prepare for PostgreSQL 17.
- Make sure all compilation and doc generation happens in %build.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1723291200">- Upgrade to 15.8 (bsc#1229013):
  * bsc#1229013, CVE-2024-7348 PostgreSQL relation replacement
    during pg_dump executes arbitrary SQL
  * https://www.postgresql.org/about/news/p-2910/
  * https://www.postgresql.org/docs/release/15.8/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1730808000">- Sync spec file from postgresql17.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1731499200">- Upgrade to 15.9:
  * CVE-2024-10976, bsc#1233323: Ensure cached plans are marked as
    dependent on the calling role when RLS applies to a
    non-top-level table reference.
  * CVE-2024-10977, bsc#1233325: Make libpq discard error messages
    received during SSL or GSS protocol negotiation.
  * CVE-2024-10978, bsc#1233326: Fix unintended interactions
    between SET SESSION AUTHORIZATION and SET ROLE
  * CVE-2024-10979, bsc#1233327: Prevent trusted PL/Perl code from
    changing environment variables.
  * https://www.postgresql.org/about/news/p-2955/
  * https://www.postgresql.org/docs/release/15.9/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1732017600">- Upgrade to 15.10
  * Repair ABI break for extensions that work with struct
    ResultRelInfo.
  * Restore functionality of ALTER {ROLE|DATABASE} SET role.
  * Fix cases where a logical replication slot's restart_lsn could
    go backwards.
  * Avoid deleting still-needed WAL files during pg_rewind.
  * Fix race conditions associated with dropping shared statistics
    entries.
  * Count index scans in contrib/bloom indexes in the statistics
    views, such as the pg_stat_user_indexes.idx_scan counter.
  * Fix crash when checking to see if an index's opclass options
    have changed.
  * Avoid assertion failure caused by disconnected NFA sub-graphs
    in regular expression parsing.
  * https://www.postgresql.org/about/news/p-2965/
  * https://www.postgresql.org/docs/release/15.10/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 15.11:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/15.11/
  * https://www.postgresql.org/about/news/-3015/
- Disable LLVM JIT on loongarch64</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 15.12:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/15.12/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 15.13:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/15.13/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Upgrade to 15.14:
  * https://www.postgresql.org/about/news/postgresql-176-1610-1514-1419-1322-and-18-beta-3-released-3118/
  * https://www.postgresql.org/docs/release/15.14/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1758801600">- Sync spec file from version 18.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Upgrade to 15.15:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/15.15/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 15.16:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/15.16/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 15.17 to fix two regressions in 15.16:
  * https://www.postgresql.org/docs/release/15.17/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
</package>
<package pkgid="bcd0fee5910ac6a1b1693e3b1345c22298a69c7026c64c3d72737029824c242719ab2fd459b7411b09e1c496797f5168124e9ac37b73d38090e80f3edd94e0e8" name="postgresql15" arch="src">
  <version epoch="0" ver="15.18" rel="97.2"/>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1715169600">- Upgrade to 15.7 (bsc#1224051):
  * bsc#1224038, CVE-2024-4317: Restrict visibility of pg_stats_ext
    and pg_stats_ext_exprs entries to the table owner. See the
    release notes for the steps that have to be taken to fix
    existing PostgreSQL instances.
  * Fix incompatibility with LLVM 18.
  * https://www.postgresql.org/docs/release/15.7/
- Prepare for PostgreSQL 17.
- Make sure all compilation and doc generation happens in %build.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1723291200">- Upgrade to 15.8 (bsc#1229013):
  * bsc#1229013, CVE-2024-7348 PostgreSQL relation replacement
    during pg_dump executes arbitrary SQL
  * https://www.postgresql.org/about/news/p-2910/
  * https://www.postgresql.org/docs/release/15.8/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1730808000">- Sync spec file from postgresql17.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1731499200">- Upgrade to 15.9:
  * CVE-2024-10976, bsc#1233323: Ensure cached plans are marked as
    dependent on the calling role when RLS applies to a
    non-top-level table reference.
  * CVE-2024-10977, bsc#1233325: Make libpq discard error messages
    received during SSL or GSS protocol negotiation.
  * CVE-2024-10978, bsc#1233326: Fix unintended interactions
    between SET SESSION AUTHORIZATION and SET ROLE
  * CVE-2024-10979, bsc#1233327: Prevent trusted PL/Perl code from
    changing environment variables.
  * https://www.postgresql.org/about/news/p-2955/
  * https://www.postgresql.org/docs/release/15.9/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1732017600">- Upgrade to 15.10
  * Repair ABI break for extensions that work with struct
    ResultRelInfo.
  * Restore functionality of ALTER {ROLE|DATABASE} SET role.
  * Fix cases where a logical replication slot's restart_lsn could
    go backwards.
  * Avoid deleting still-needed WAL files during pg_rewind.
  * Fix race conditions associated with dropping shared statistics
    entries.
  * Count index scans in contrib/bloom indexes in the statistics
    views, such as the pg_stat_user_indexes.idx_scan counter.
  * Fix crash when checking to see if an index's opclass options
    have changed.
  * Avoid assertion failure caused by disconnected NFA sub-graphs
    in regular expression parsing.
  * https://www.postgresql.org/about/news/p-2965/
  * https://www.postgresql.org/docs/release/15.10/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 15.11:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/15.11/
  * https://www.postgresql.org/about/news/-3015/
- Disable LLVM JIT on loongarch64</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 15.12:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/15.12/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 15.13:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/15.13/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Upgrade to 15.14:
  * https://www.postgresql.org/about/news/postgresql-176-1610-1514-1419-1322-and-18-beta-3-released-3118/
  * https://www.postgresql.org/docs/release/15.14/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1758801600">- Sync spec file from version 18.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Upgrade to 15.15:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/15.15/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 15.16:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/15.16/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 15.17 to fix two regressions in 15.16:
  * https://www.postgresql.org/docs/release/15.17/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1774872000">- Get rid of update-alternatives for openSUSE/SLE 16.0 and newer
  to support immutable systems and transactional updates.
  (jsc#PED-14823)</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1777550400">- bsc#1263804: After dropping update-alternatives we have to
  package /usr/bin/pg_config as an actual symlink, not %ghost.
- Fix spelling of build conditionals.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1778673600">- Update to version 15.18:
  * bsc#1265172, CVE-2026-6472: ensure the user has CREATE
    privilege on the schema specified
  * bsc#1265173, CVE-2026-6473: integer overflows in
    memory-allocation calculations
  * bsc#1265174, CVE-2026-6474: Guard against malicious time zone
    names
  * bsc#1265175, CVE-2026-6475: Prevent path traversal in
    pg_basebackup and pg_rewind
  * bsc#1265177, CVE-2026-6477: Mark PQfn() as unsafe, and avoid
    using it within libpq
  * bsc#1265178, CVE-2026-6478: Use timing-safe string comparisons
    in authentication code
  * bsc#1265179, CVE-2026-6479: Prevent unbounded recursion while
    processing startup packets
  * bsc#1265181, CVE-2026-6637: Prevent SQL injection and buffer
    overruns in contrib/spi
  * https://www.postgresql.org/docs/release/15.18/</changelog>
</package>
<package pkgid="f9142a3ba900d7be23453994e3a41f01007b8c2f55268f45319a19dcf3303ab75d9c72ee26b569cb9c5690f6f0a6c985a5a0c9a25fc2a68a36e87691f0e48746" name="postgresql15" arch="x86_64">
  <version epoch="0" ver="15.18" rel="97.2"/>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1715169600">- Upgrade to 15.7 (bsc#1224051):
  * bsc#1224038, CVE-2024-4317: Restrict visibility of pg_stats_ext
    and pg_stats_ext_exprs entries to the table owner. See the
    release notes for the steps that have to be taken to fix
    existing PostgreSQL instances.
  * Fix incompatibility with LLVM 18.
  * https://www.postgresql.org/docs/release/15.7/
- Prepare for PostgreSQL 17.
- Make sure all compilation and doc generation happens in %build.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1723291200">- Upgrade to 15.8 (bsc#1229013):
  * bsc#1229013, CVE-2024-7348 PostgreSQL relation replacement
    during pg_dump executes arbitrary SQL
  * https://www.postgresql.org/about/news/p-2910/
  * https://www.postgresql.org/docs/release/15.8/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1730808000">- Sync spec file from postgresql17.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1731499200">- Upgrade to 15.9:
  * CVE-2024-10976, bsc#1233323: Ensure cached plans are marked as
    dependent on the calling role when RLS applies to a
    non-top-level table reference.
  * CVE-2024-10977, bsc#1233325: Make libpq discard error messages
    received during SSL or GSS protocol negotiation.
  * CVE-2024-10978, bsc#1233326: Fix unintended interactions
    between SET SESSION AUTHORIZATION and SET ROLE
  * CVE-2024-10979, bsc#1233327: Prevent trusted PL/Perl code from
    changing environment variables.
  * https://www.postgresql.org/about/news/p-2955/
  * https://www.postgresql.org/docs/release/15.9/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1732017600">- Upgrade to 15.10
  * Repair ABI break for extensions that work with struct
    ResultRelInfo.
  * Restore functionality of ALTER {ROLE|DATABASE} SET role.
  * Fix cases where a logical replication slot's restart_lsn could
    go backwards.
  * Avoid deleting still-needed WAL files during pg_rewind.
  * Fix race conditions associated with dropping shared statistics
    entries.
  * Count index scans in contrib/bloom indexes in the statistics
    views, such as the pg_stat_user_indexes.idx_scan counter.
  * Fix crash when checking to see if an index's opclass options
    have changed.
  * Avoid assertion failure caused by disconnected NFA sub-graphs
    in regular expression parsing.
  * https://www.postgresql.org/about/news/p-2965/
  * https://www.postgresql.org/docs/release/15.10/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 15.11:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/15.11/
  * https://www.postgresql.org/about/news/-3015/
- Disable LLVM JIT on loongarch64</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 15.12:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/15.12/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 15.13:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/15.13/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Upgrade to 15.14:
  * https://www.postgresql.org/about/news/postgresql-176-1610-1514-1419-1322-and-18-beta-3-released-3118/
  * https://www.postgresql.org/docs/release/15.14/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1758801600">- Sync spec file from version 18.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Upgrade to 15.15:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/15.15/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 15.16:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/15.16/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 15.17 to fix two regressions in 15.16:
  * https://www.postgresql.org/docs/release/15.17/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1774872000">- Get rid of update-alternatives for openSUSE/SLE 16.0 and newer
  to support immutable systems and transactional updates.
  (jsc#PED-14823)</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1777550400">- bsc#1263804: After dropping update-alternatives we have to
  package /usr/bin/pg_config as an actual symlink, not %ghost.
- Fix spelling of build conditionals.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1778673600">- Update to version 15.18:
  * bsc#1265172, CVE-2026-6472: ensure the user has CREATE
    privilege on the schema specified
  * bsc#1265173, CVE-2026-6473: integer overflows in
    memory-allocation calculations
  * bsc#1265174, CVE-2026-6474: Guard against malicious time zone
    names
  * bsc#1265175, CVE-2026-6475: Prevent path traversal in
    pg_basebackup and pg_rewind
  * bsc#1265177, CVE-2026-6477: Mark PQfn() as unsafe, and avoid
    using it within libpq
  * bsc#1265178, CVE-2026-6478: Use timing-safe string comparisons
    in authentication code
  * bsc#1265179, CVE-2026-6479: Prevent unbounded recursion while
    processing startup packets
  * bsc#1265181, CVE-2026-6637: Prevent SQL injection and buffer
    overruns in contrib/spi
  * https://www.postgresql.org/docs/release/15.18/</changelog>
</package>
<package pkgid="db2336a54c39c6fcb8fe5e2d6b08acdea445a66efe2b1a697b56cd6ba60bb0b708edb9ddcbb0935667afd7406d40abac43415378215eac4b655b40ae0af6fd6f" name="postgresql15-contrib" arch="ppc64le">
  <version epoch="0" ver="15.17" rel="86.1"/>
  <changelog author="Dominique Leuenberger &lt;dimstar@opensuse.org&gt;" date="1709208000">- Use %patch -P N instead of deprecated %patchN.</changelog>
  <changelog author="Sarah Kriesch &lt;sarah.kriesch@opensuse.org&gt;" date="1709812800">- Remove constraints file because improved memory usage for s390x</changelog>
  <changelog author="Aaron Puchert &lt;aaronpuchert@alice-dsl.net&gt;" date="1710244800">- Require LLVM &lt;= 17 for now, because LLVM 18 doesn't seem to work.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1715169600">- Upgrade to 15.7 (bsc#1224051):
  * bsc#1224038, CVE-2024-4317: Restrict visibility of pg_stats_ext
    and pg_stats_ext_exprs entries to the table owner. See the
    release notes for the steps that have to be taken to fix
    existing PostgreSQL instances.
  * Fix incompatibility with LLVM 18.
  * https://www.postgresql.org/docs/release/15.7/
- Prepare for PostgreSQL 17.
- Make sure all compilation and doc generation happens in %build.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1723291200">- Upgrade to 15.8 (bsc#1229013):
  * bsc#1229013, CVE-2024-7348 PostgreSQL relation replacement
    during pg_dump executes arbitrary SQL
  * https://www.postgresql.org/about/news/p-2910/
  * https://www.postgresql.org/docs/release/15.8/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1730808000">- Sync spec file from postgresql17.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1731499200">- Upgrade to 15.9:
  * CVE-2024-10976, bsc#1233323: Ensure cached plans are marked as
    dependent on the calling role when RLS applies to a
    non-top-level table reference.
  * CVE-2024-10977, bsc#1233325: Make libpq discard error messages
    received during SSL or GSS protocol negotiation.
  * CVE-2024-10978, bsc#1233326: Fix unintended interactions
    between SET SESSION AUTHORIZATION and SET ROLE
  * CVE-2024-10979, bsc#1233327: Prevent trusted PL/Perl code from
    changing environment variables.
  * https://www.postgresql.org/about/news/p-2955/
  * https://www.postgresql.org/docs/release/15.9/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1732017600">- Upgrade to 15.10
  * Repair ABI break for extensions that work with struct
    ResultRelInfo.
  * Restore functionality of ALTER {ROLE|DATABASE} SET role.
  * Fix cases where a logical replication slot's restart_lsn could
    go backwards.
  * Avoid deleting still-needed WAL files during pg_rewind.
  * Fix race conditions associated with dropping shared statistics
    entries.
  * Count index scans in contrib/bloom indexes in the statistics
    views, such as the pg_stat_user_indexes.idx_scan counter.
  * Fix crash when checking to see if an index's opclass options
    have changed.
  * Avoid assertion failure caused by disconnected NFA sub-graphs
    in regular expression parsing.
  * https://www.postgresql.org/about/news/p-2965/
  * https://www.postgresql.org/docs/release/15.10/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 15.11:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/15.11/
  * https://www.postgresql.org/about/news/-3015/
- Disable LLVM JIT on loongarch64</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 15.12:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/15.12/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 15.13:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/15.13/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Upgrade to 15.14:
  * https://www.postgresql.org/about/news/postgresql-176-1610-1514-1419-1322-and-18-beta-3-released-3118/
  * https://www.postgresql.org/docs/release/15.14/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1758801600">- Sync spec file from version 18.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Upgrade to 15.15:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/15.15/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 15.16:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/15.16/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 15.17 to fix two regressions in 15.16:
  * https://www.postgresql.org/docs/release/15.17/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
</package>
<package pkgid="572a8933fcd858dd234dbea6c8c9f4c57846e7308a49a72f349ce0fa358764f8c065cea8dfe10799d2d7e1a0bad7b9821c70bc99f8c1b185e6ef3abee58c8f63" name="postgresql15-contrib" arch="aarch64">
  <version epoch="0" ver="15.17" rel="87.2"/>
  <changelog author="Dominique Leuenberger &lt;dimstar@opensuse.org&gt;" date="1709208000">- Use %patch -P N instead of deprecated %patchN.</changelog>
  <changelog author="Sarah Kriesch &lt;sarah.kriesch@opensuse.org&gt;" date="1709812800">- Remove constraints file because improved memory usage for s390x</changelog>
  <changelog author="Aaron Puchert &lt;aaronpuchert@alice-dsl.net&gt;" date="1710244800">- Require LLVM &lt;= 17 for now, because LLVM 18 doesn't seem to work.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1715169600">- Upgrade to 15.7 (bsc#1224051):
  * bsc#1224038, CVE-2024-4317: Restrict visibility of pg_stats_ext
    and pg_stats_ext_exprs entries to the table owner. See the
    release notes for the steps that have to be taken to fix
    existing PostgreSQL instances.
  * Fix incompatibility with LLVM 18.
  * https://www.postgresql.org/docs/release/15.7/
- Prepare for PostgreSQL 17.
- Make sure all compilation and doc generation happens in %build.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1723291200">- Upgrade to 15.8 (bsc#1229013):
  * bsc#1229013, CVE-2024-7348 PostgreSQL relation replacement
    during pg_dump executes arbitrary SQL
  * https://www.postgresql.org/about/news/p-2910/
  * https://www.postgresql.org/docs/release/15.8/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1730808000">- Sync spec file from postgresql17.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1731499200">- Upgrade to 15.9:
  * CVE-2024-10976, bsc#1233323: Ensure cached plans are marked as
    dependent on the calling role when RLS applies to a
    non-top-level table reference.
  * CVE-2024-10977, bsc#1233325: Make libpq discard error messages
    received during SSL or GSS protocol negotiation.
  * CVE-2024-10978, bsc#1233326: Fix unintended interactions
    between SET SESSION AUTHORIZATION and SET ROLE
  * CVE-2024-10979, bsc#1233327: Prevent trusted PL/Perl code from
    changing environment variables.
  * https://www.postgresql.org/about/news/p-2955/
  * https://www.postgresql.org/docs/release/15.9/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1732017600">- Upgrade to 15.10
  * Repair ABI break for extensions that work with struct
    ResultRelInfo.
  * Restore functionality of ALTER {ROLE|DATABASE} SET role.
  * Fix cases where a logical replication slot's restart_lsn could
    go backwards.
  * Avoid deleting still-needed WAL files during pg_rewind.
  * Fix race conditions associated with dropping shared statistics
    entries.
  * Count index scans in contrib/bloom indexes in the statistics
    views, such as the pg_stat_user_indexes.idx_scan counter.
  * Fix crash when checking to see if an index's opclass options
    have changed.
  * Avoid assertion failure caused by disconnected NFA sub-graphs
    in regular expression parsing.
  * https://www.postgresql.org/about/news/p-2965/
  * https://www.postgresql.org/docs/release/15.10/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 15.11:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/15.11/
  * https://www.postgresql.org/about/news/-3015/
- Disable LLVM JIT on loongarch64</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 15.12:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/15.12/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 15.13:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/15.13/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Upgrade to 15.14:
  * https://www.postgresql.org/about/news/postgresql-176-1610-1514-1419-1322-and-18-beta-3-released-3118/
  * https://www.postgresql.org/docs/release/15.14/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1758801600">- Sync spec file from version 18.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Upgrade to 15.15:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/15.15/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 15.16:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/15.16/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 15.17 to fix two regressions in 15.16:
  * https://www.postgresql.org/docs/release/15.17/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
</package>
<package pkgid="b149c92d506babd7824b3a5f86e9d928d3e7ebfeb015c4b36d29b47e1c8a31fb8ada8317c42bf5292171ce25aac22d78f17e1cbdc9b48456efe3db99b93af615" name="postgresql15-contrib" arch="s390x">
  <version epoch="0" ver="15.17" rel="87.2"/>
  <changelog author="Dominique Leuenberger &lt;dimstar@opensuse.org&gt;" date="1709208000">- Use %patch -P N instead of deprecated %patchN.</changelog>
  <changelog author="Sarah Kriesch &lt;sarah.kriesch@opensuse.org&gt;" date="1709812800">- Remove constraints file because improved memory usage for s390x</changelog>
  <changelog author="Aaron Puchert &lt;aaronpuchert@alice-dsl.net&gt;" date="1710244800">- Require LLVM &lt;= 17 for now, because LLVM 18 doesn't seem to work.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1715169600">- Upgrade to 15.7 (bsc#1224051):
  * bsc#1224038, CVE-2024-4317: Restrict visibility of pg_stats_ext
    and pg_stats_ext_exprs entries to the table owner. See the
    release notes for the steps that have to be taken to fix
    existing PostgreSQL instances.
  * Fix incompatibility with LLVM 18.
  * https://www.postgresql.org/docs/release/15.7/
- Prepare for PostgreSQL 17.
- Make sure all compilation and doc generation happens in %build.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1723291200">- Upgrade to 15.8 (bsc#1229013):
  * bsc#1229013, CVE-2024-7348 PostgreSQL relation replacement
    during pg_dump executes arbitrary SQL
  * https://www.postgresql.org/about/news/p-2910/
  * https://www.postgresql.org/docs/release/15.8/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1730808000">- Sync spec file from postgresql17.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1731499200">- Upgrade to 15.9:
  * CVE-2024-10976, bsc#1233323: Ensure cached plans are marked as
    dependent on the calling role when RLS applies to a
    non-top-level table reference.
  * CVE-2024-10977, bsc#1233325: Make libpq discard error messages
    received during SSL or GSS protocol negotiation.
  * CVE-2024-10978, bsc#1233326: Fix unintended interactions
    between SET SESSION AUTHORIZATION and SET ROLE
  * CVE-2024-10979, bsc#1233327: Prevent trusted PL/Perl code from
    changing environment variables.
  * https://www.postgresql.org/about/news/p-2955/
  * https://www.postgresql.org/docs/release/15.9/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1732017600">- Upgrade to 15.10
  * Repair ABI break for extensions that work with struct
    ResultRelInfo.
  * Restore functionality of ALTER {ROLE|DATABASE} SET role.
  * Fix cases where a logical replication slot's restart_lsn could
    go backwards.
  * Avoid deleting still-needed WAL files during pg_rewind.
  * Fix race conditions associated with dropping shared statistics
    entries.
  * Count index scans in contrib/bloom indexes in the statistics
    views, such as the pg_stat_user_indexes.idx_scan counter.
  * Fix crash when checking to see if an index's opclass options
    have changed.
  * Avoid assertion failure caused by disconnected NFA sub-graphs
    in regular expression parsing.
  * https://www.postgresql.org/about/news/p-2965/
  * https://www.postgresql.org/docs/release/15.10/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 15.11:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/15.11/
  * https://www.postgresql.org/about/news/-3015/
- Disable LLVM JIT on loongarch64</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 15.12:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/15.12/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 15.13:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/15.13/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Upgrade to 15.14:
  * https://www.postgresql.org/about/news/postgresql-176-1610-1514-1419-1322-and-18-beta-3-released-3118/
  * https://www.postgresql.org/docs/release/15.14/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1758801600">- Sync spec file from version 18.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Upgrade to 15.15:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/15.15/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 15.16:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/15.16/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 15.17 to fix two regressions in 15.16:
  * https://www.postgresql.org/docs/release/15.17/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
</package>
<package pkgid="2ed426ad5cb6b23ed6b9b7a00913985d68788eaecf5b982c0d1906330499c164e5fff726abb46a9792dde3ae1f18789bf47bd1c838e7b8fc1788426fa00e7824" name="postgresql15-contrib" arch="x86_64">
  <version epoch="0" ver="15.18" rel="97.2"/>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1715169600">- Upgrade to 15.7 (bsc#1224051):
  * bsc#1224038, CVE-2024-4317: Restrict visibility of pg_stats_ext
    and pg_stats_ext_exprs entries to the table owner. See the
    release notes for the steps that have to be taken to fix
    existing PostgreSQL instances.
  * Fix incompatibility with LLVM 18.
  * https://www.postgresql.org/docs/release/15.7/
- Prepare for PostgreSQL 17.
- Make sure all compilation and doc generation happens in %build.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1723291200">- Upgrade to 15.8 (bsc#1229013):
  * bsc#1229013, CVE-2024-7348 PostgreSQL relation replacement
    during pg_dump executes arbitrary SQL
  * https://www.postgresql.org/about/news/p-2910/
  * https://www.postgresql.org/docs/release/15.8/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1730808000">- Sync spec file from postgresql17.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1731499200">- Upgrade to 15.9:
  * CVE-2024-10976, bsc#1233323: Ensure cached plans are marked as
    dependent on the calling role when RLS applies to a
    non-top-level table reference.
  * CVE-2024-10977, bsc#1233325: Make libpq discard error messages
    received during SSL or GSS protocol negotiation.
  * CVE-2024-10978, bsc#1233326: Fix unintended interactions
    between SET SESSION AUTHORIZATION and SET ROLE
  * CVE-2024-10979, bsc#1233327: Prevent trusted PL/Perl code from
    changing environment variables.
  * https://www.postgresql.org/about/news/p-2955/
  * https://www.postgresql.org/docs/release/15.9/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1732017600">- Upgrade to 15.10
  * Repair ABI break for extensions that work with struct
    ResultRelInfo.
  * Restore functionality of ALTER {ROLE|DATABASE} SET role.
  * Fix cases where a logical replication slot's restart_lsn could
    go backwards.
  * Avoid deleting still-needed WAL files during pg_rewind.
  * Fix race conditions associated with dropping shared statistics
    entries.
  * Count index scans in contrib/bloom indexes in the statistics
    views, such as the pg_stat_user_indexes.idx_scan counter.
  * Fix crash when checking to see if an index's opclass options
    have changed.
  * Avoid assertion failure caused by disconnected NFA sub-graphs
    in regular expression parsing.
  * https://www.postgresql.org/about/news/p-2965/
  * https://www.postgresql.org/docs/release/15.10/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 15.11:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/15.11/
  * https://www.postgresql.org/about/news/-3015/
- Disable LLVM JIT on loongarch64</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 15.12:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/15.12/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 15.13:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/15.13/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Upgrade to 15.14:
  * https://www.postgresql.org/about/news/postgresql-176-1610-1514-1419-1322-and-18-beta-3-released-3118/
  * https://www.postgresql.org/docs/release/15.14/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1758801600">- Sync spec file from version 18.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Upgrade to 15.15:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/15.15/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 15.16:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/15.16/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 15.17 to fix two regressions in 15.16:
  * https://www.postgresql.org/docs/release/15.17/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1774872000">- Get rid of update-alternatives for openSUSE/SLE 16.0 and newer
  to support immutable systems and transactional updates.
  (jsc#PED-14823)</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1777550400">- bsc#1263804: After dropping update-alternatives we have to
  package /usr/bin/pg_config as an actual symlink, not %ghost.
- Fix spelling of build conditionals.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1778673600">- Update to version 15.18:
  * bsc#1265172, CVE-2026-6472: ensure the user has CREATE
    privilege on the schema specified
  * bsc#1265173, CVE-2026-6473: integer overflows in
    memory-allocation calculations
  * bsc#1265174, CVE-2026-6474: Guard against malicious time zone
    names
  * bsc#1265175, CVE-2026-6475: Prevent path traversal in
    pg_basebackup and pg_rewind
  * bsc#1265177, CVE-2026-6477: Mark PQfn() as unsafe, and avoid
    using it within libpq
  * bsc#1265178, CVE-2026-6478: Use timing-safe string comparisons
    in authentication code
  * bsc#1265179, CVE-2026-6479: Prevent unbounded recursion while
    processing startup packets
  * bsc#1265181, CVE-2026-6637: Prevent SQL injection and buffer
    overruns in contrib/spi
  * https://www.postgresql.org/docs/release/15.18/</changelog>
</package>
<package pkgid="9b890d1c5e8a289711f038c467eab006249b7821fe893825527077922b62e0fc66dbeb490f79f908450b396a138e5580e790d60d834a27c71d62e5ea83855e9f" name="postgresql15-devel" arch="ppc64le">
  <version epoch="0" ver="15.17" rel="86.1"/>
  <changelog author="Dominique Leuenberger &lt;dimstar@opensuse.org&gt;" date="1709208000">- Use %patch -P N instead of deprecated %patchN.</changelog>
  <changelog author="Sarah Kriesch &lt;sarah.kriesch@opensuse.org&gt;" date="1709812800">- Remove constraints file because improved memory usage for s390x</changelog>
  <changelog author="Aaron Puchert &lt;aaronpuchert@alice-dsl.net&gt;" date="1710244800">- Require LLVM &lt;= 17 for now, because LLVM 18 doesn't seem to work.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1715169600">- Upgrade to 15.7 (bsc#1224051):
  * bsc#1224038, CVE-2024-4317: Restrict visibility of pg_stats_ext
    and pg_stats_ext_exprs entries to the table owner. See the
    release notes for the steps that have to be taken to fix
    existing PostgreSQL instances.
  * Fix incompatibility with LLVM 18.
  * https://www.postgresql.org/docs/release/15.7/
- Prepare for PostgreSQL 17.
- Make sure all compilation and doc generation happens in %build.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1723291200">- Upgrade to 15.8 (bsc#1229013):
  * bsc#1229013, CVE-2024-7348 PostgreSQL relation replacement
    during pg_dump executes arbitrary SQL
  * https://www.postgresql.org/about/news/p-2910/
  * https://www.postgresql.org/docs/release/15.8/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1730808000">- Sync spec file from postgresql17.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1731499200">- Upgrade to 15.9:
  * CVE-2024-10976, bsc#1233323: Ensure cached plans are marked as
    dependent on the calling role when RLS applies to a
    non-top-level table reference.
  * CVE-2024-10977, bsc#1233325: Make libpq discard error messages
    received during SSL or GSS protocol negotiation.
  * CVE-2024-10978, bsc#1233326: Fix unintended interactions
    between SET SESSION AUTHORIZATION and SET ROLE
  * CVE-2024-10979, bsc#1233327: Prevent trusted PL/Perl code from
    changing environment variables.
  * https://www.postgresql.org/about/news/p-2955/
  * https://www.postgresql.org/docs/release/15.9/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1732017600">- Upgrade to 15.10
  * Repair ABI break for extensions that work with struct
    ResultRelInfo.
  * Restore functionality of ALTER {ROLE|DATABASE} SET role.
  * Fix cases where a logical replication slot's restart_lsn could
    go backwards.
  * Avoid deleting still-needed WAL files during pg_rewind.
  * Fix race conditions associated with dropping shared statistics
    entries.
  * Count index scans in contrib/bloom indexes in the statistics
    views, such as the pg_stat_user_indexes.idx_scan counter.
  * Fix crash when checking to see if an index's opclass options
    have changed.
  * Avoid assertion failure caused by disconnected NFA sub-graphs
    in regular expression parsing.
  * https://www.postgresql.org/about/news/p-2965/
  * https://www.postgresql.org/docs/release/15.10/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 15.11:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/15.11/
  * https://www.postgresql.org/about/news/-3015/
- Disable LLVM JIT on loongarch64</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 15.12:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/15.12/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 15.13:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/15.13/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Upgrade to 15.14:
  * https://www.postgresql.org/about/news/postgresql-176-1610-1514-1419-1322-and-18-beta-3-released-3118/
  * https://www.postgresql.org/docs/release/15.14/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1758801600">- Sync spec file from version 18.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Upgrade to 15.15:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/15.15/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 15.16:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/15.16/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 15.17 to fix two regressions in 15.16:
  * https://www.postgresql.org/docs/release/15.17/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
</package>
<package pkgid="4b1a8f754a5e96be8eb88525fc8db1dca888621478dcb958a0f037f8e19c1a62533ae86782339984c8e38d54ee6cd9454e0e3f989730350eed7c6ec6a13b7196" name="postgresql15-devel" arch="aarch64">
  <version epoch="0" ver="15.17" rel="87.2"/>
  <changelog author="Dominique Leuenberger &lt;dimstar@opensuse.org&gt;" date="1709208000">- Use %patch -P N instead of deprecated %patchN.</changelog>
  <changelog author="Sarah Kriesch &lt;sarah.kriesch@opensuse.org&gt;" date="1709812800">- Remove constraints file because improved memory usage for s390x</changelog>
  <changelog author="Aaron Puchert &lt;aaronpuchert@alice-dsl.net&gt;" date="1710244800">- Require LLVM &lt;= 17 for now, because LLVM 18 doesn't seem to work.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1715169600">- Upgrade to 15.7 (bsc#1224051):
  * bsc#1224038, CVE-2024-4317: Restrict visibility of pg_stats_ext
    and pg_stats_ext_exprs entries to the table owner. See the
    release notes for the steps that have to be taken to fix
    existing PostgreSQL instances.
  * Fix incompatibility with LLVM 18.
  * https://www.postgresql.org/docs/release/15.7/
- Prepare for PostgreSQL 17.
- Make sure all compilation and doc generation happens in %build.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1723291200">- Upgrade to 15.8 (bsc#1229013):
  * bsc#1229013, CVE-2024-7348 PostgreSQL relation replacement
    during pg_dump executes arbitrary SQL
  * https://www.postgresql.org/about/news/p-2910/
  * https://www.postgresql.org/docs/release/15.8/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1730808000">- Sync spec file from postgresql17.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1731499200">- Upgrade to 15.9:
  * CVE-2024-10976, bsc#1233323: Ensure cached plans are marked as
    dependent on the calling role when RLS applies to a
    non-top-level table reference.
  * CVE-2024-10977, bsc#1233325: Make libpq discard error messages
    received during SSL or GSS protocol negotiation.
  * CVE-2024-10978, bsc#1233326: Fix unintended interactions
    between SET SESSION AUTHORIZATION and SET ROLE
  * CVE-2024-10979, bsc#1233327: Prevent trusted PL/Perl code from
    changing environment variables.
  * https://www.postgresql.org/about/news/p-2955/
  * https://www.postgresql.org/docs/release/15.9/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1732017600">- Upgrade to 15.10
  * Repair ABI break for extensions that work with struct
    ResultRelInfo.
  * Restore functionality of ALTER {ROLE|DATABASE} SET role.
  * Fix cases where a logical replication slot's restart_lsn could
    go backwards.
  * Avoid deleting still-needed WAL files during pg_rewind.
  * Fix race conditions associated with dropping shared statistics
    entries.
  * Count index scans in contrib/bloom indexes in the statistics
    views, such as the pg_stat_user_indexes.idx_scan counter.
  * Fix crash when checking to see if an index's opclass options
    have changed.
  * Avoid assertion failure caused by disconnected NFA sub-graphs
    in regular expression parsing.
  * https://www.postgresql.org/about/news/p-2965/
  * https://www.postgresql.org/docs/release/15.10/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 15.11:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/15.11/
  * https://www.postgresql.org/about/news/-3015/
- Disable LLVM JIT on loongarch64</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 15.12:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/15.12/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 15.13:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/15.13/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Upgrade to 15.14:
  * https://www.postgresql.org/about/news/postgresql-176-1610-1514-1419-1322-and-18-beta-3-released-3118/
  * https://www.postgresql.org/docs/release/15.14/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1758801600">- Sync spec file from version 18.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Upgrade to 15.15:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/15.15/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 15.16:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/15.16/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 15.17 to fix two regressions in 15.16:
  * https://www.postgresql.org/docs/release/15.17/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
</package>
<package pkgid="6dd4f3472df8ea746e5494dd14d2517ad32be54676ea624dacf3583c87493f093f82c64f0d3a6743f75dff41da2cb2e0094f2eca87ac5de96613b64e7c453f2e" name="postgresql15-devel" arch="s390x">
  <version epoch="0" ver="15.17" rel="87.2"/>
  <changelog author="Dominique Leuenberger &lt;dimstar@opensuse.org&gt;" date="1709208000">- Use %patch -P N instead of deprecated %patchN.</changelog>
  <changelog author="Sarah Kriesch &lt;sarah.kriesch@opensuse.org&gt;" date="1709812800">- Remove constraints file because improved memory usage for s390x</changelog>
  <changelog author="Aaron Puchert &lt;aaronpuchert@alice-dsl.net&gt;" date="1710244800">- Require LLVM &lt;= 17 for now, because LLVM 18 doesn't seem to work.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1715169600">- Upgrade to 15.7 (bsc#1224051):
  * bsc#1224038, CVE-2024-4317: Restrict visibility of pg_stats_ext
    and pg_stats_ext_exprs entries to the table owner. See the
    release notes for the steps that have to be taken to fix
    existing PostgreSQL instances.
  * Fix incompatibility with LLVM 18.
  * https://www.postgresql.org/docs/release/15.7/
- Prepare for PostgreSQL 17.
- Make sure all compilation and doc generation happens in %build.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1723291200">- Upgrade to 15.8 (bsc#1229013):
  * bsc#1229013, CVE-2024-7348 PostgreSQL relation replacement
    during pg_dump executes arbitrary SQL
  * https://www.postgresql.org/about/news/p-2910/
  * https://www.postgresql.org/docs/release/15.8/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1730808000">- Sync spec file from postgresql17.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1731499200">- Upgrade to 15.9:
  * CVE-2024-10976, bsc#1233323: Ensure cached plans are marked as
    dependent on the calling role when RLS applies to a
    non-top-level table reference.
  * CVE-2024-10977, bsc#1233325: Make libpq discard error messages
    received during SSL or GSS protocol negotiation.
  * CVE-2024-10978, bsc#1233326: Fix unintended interactions
    between SET SESSION AUTHORIZATION and SET ROLE
  * CVE-2024-10979, bsc#1233327: Prevent trusted PL/Perl code from
    changing environment variables.
  * https://www.postgresql.org/about/news/p-2955/
  * https://www.postgresql.org/docs/release/15.9/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1732017600">- Upgrade to 15.10
  * Repair ABI break for extensions that work with struct
    ResultRelInfo.
  * Restore functionality of ALTER {ROLE|DATABASE} SET role.
  * Fix cases where a logical replication slot's restart_lsn could
    go backwards.
  * Avoid deleting still-needed WAL files during pg_rewind.
  * Fix race conditions associated with dropping shared statistics
    entries.
  * Count index scans in contrib/bloom indexes in the statistics
    views, such as the pg_stat_user_indexes.idx_scan counter.
  * Fix crash when checking to see if an index's opclass options
    have changed.
  * Avoid assertion failure caused by disconnected NFA sub-graphs
    in regular expression parsing.
  * https://www.postgresql.org/about/news/p-2965/
  * https://www.postgresql.org/docs/release/15.10/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 15.11:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/15.11/
  * https://www.postgresql.org/about/news/-3015/
- Disable LLVM JIT on loongarch64</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 15.12:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/15.12/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 15.13:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/15.13/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Upgrade to 15.14:
  * https://www.postgresql.org/about/news/postgresql-176-1610-1514-1419-1322-and-18-beta-3-released-3118/
  * https://www.postgresql.org/docs/release/15.14/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1758801600">- Sync spec file from version 18.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Upgrade to 15.15:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/15.15/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 15.16:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/15.16/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 15.17 to fix two regressions in 15.16:
  * https://www.postgresql.org/docs/release/15.17/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
</package>
<package pkgid="07c8b32237974ce73ce57e35b027fcbd5294a1998a4796cc322194d961df80166a35565557384cacc69948d1eff66f956de7f8912e91f9dd0bfd467a1f667715" name="postgresql15-devel" arch="x86_64">
  <version epoch="0" ver="15.18" rel="97.2"/>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1715169600">- Upgrade to 15.7 (bsc#1224051):
  * bsc#1224038, CVE-2024-4317: Restrict visibility of pg_stats_ext
    and pg_stats_ext_exprs entries to the table owner. See the
    release notes for the steps that have to be taken to fix
    existing PostgreSQL instances.
  * Fix incompatibility with LLVM 18.
  * https://www.postgresql.org/docs/release/15.7/
- Prepare for PostgreSQL 17.
- Make sure all compilation and doc generation happens in %build.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1723291200">- Upgrade to 15.8 (bsc#1229013):
  * bsc#1229013, CVE-2024-7348 PostgreSQL relation replacement
    during pg_dump executes arbitrary SQL
  * https://www.postgresql.org/about/news/p-2910/
  * https://www.postgresql.org/docs/release/15.8/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1730808000">- Sync spec file from postgresql17.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1731499200">- Upgrade to 15.9:
  * CVE-2024-10976, bsc#1233323: Ensure cached plans are marked as
    dependent on the calling role when RLS applies to a
    non-top-level table reference.
  * CVE-2024-10977, bsc#1233325: Make libpq discard error messages
    received during SSL or GSS protocol negotiation.
  * CVE-2024-10978, bsc#1233326: Fix unintended interactions
    between SET SESSION AUTHORIZATION and SET ROLE
  * CVE-2024-10979, bsc#1233327: Prevent trusted PL/Perl code from
    changing environment variables.
  * https://www.postgresql.org/about/news/p-2955/
  * https://www.postgresql.org/docs/release/15.9/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1732017600">- Upgrade to 15.10
  * Repair ABI break for extensions that work with struct
    ResultRelInfo.
  * Restore functionality of ALTER {ROLE|DATABASE} SET role.
  * Fix cases where a logical replication slot's restart_lsn could
    go backwards.
  * Avoid deleting still-needed WAL files during pg_rewind.
  * Fix race conditions associated with dropping shared statistics
    entries.
  * Count index scans in contrib/bloom indexes in the statistics
    views, such as the pg_stat_user_indexes.idx_scan counter.
  * Fix crash when checking to see if an index's opclass options
    have changed.
  * Avoid assertion failure caused by disconnected NFA sub-graphs
    in regular expression parsing.
  * https://www.postgresql.org/about/news/p-2965/
  * https://www.postgresql.org/docs/release/15.10/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 15.11:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/15.11/
  * https://www.postgresql.org/about/news/-3015/
- Disable LLVM JIT on loongarch64</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 15.12:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/15.12/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 15.13:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/15.13/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Upgrade to 15.14:
  * https://www.postgresql.org/about/news/postgresql-176-1610-1514-1419-1322-and-18-beta-3-released-3118/
  * https://www.postgresql.org/docs/release/15.14/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1758801600">- Sync spec file from version 18.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Upgrade to 15.15:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/15.15/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 15.16:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/15.16/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 15.17 to fix two regressions in 15.16:
  * https://www.postgresql.org/docs/release/15.17/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1774872000">- Get rid of update-alternatives for openSUSE/SLE 16.0 and newer
  to support immutable systems and transactional updates.
  (jsc#PED-14823)</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1777550400">- bsc#1263804: After dropping update-alternatives we have to
  package /usr/bin/pg_config as an actual symlink, not %ghost.
- Fix spelling of build conditionals.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1778673600">- Update to version 15.18:
  * bsc#1265172, CVE-2026-6472: ensure the user has CREATE
    privilege on the schema specified
  * bsc#1265173, CVE-2026-6473: integer overflows in
    memory-allocation calculations
  * bsc#1265174, CVE-2026-6474: Guard against malicious time zone
    names
  * bsc#1265175, CVE-2026-6475: Prevent path traversal in
    pg_basebackup and pg_rewind
  * bsc#1265177, CVE-2026-6477: Mark PQfn() as unsafe, and avoid
    using it within libpq
  * bsc#1265178, CVE-2026-6478: Use timing-safe string comparisons
    in authentication code
  * bsc#1265179, CVE-2026-6479: Prevent unbounded recursion while
    processing startup packets
  * bsc#1265181, CVE-2026-6637: Prevent SQL injection and buffer
    overruns in contrib/spi
  * https://www.postgresql.org/docs/release/15.18/</changelog>
</package>
<package pkgid="0346c742ce905349d3c965a097739d972b79f5c35e043fb5d0cc15ee6d611b7823eccf213af6703c83df27489f4e23b14c8f055b6f1c6707d63ac584c0d16e5e" name="postgresql15-docs" arch="noarch">
  <version epoch="0" ver="15.17" rel="86.1"/>
  <changelog author="Dominique Leuenberger &lt;dimstar@opensuse.org&gt;" date="1709208000">- Use %patch -P N instead of deprecated %patchN.</changelog>
  <changelog author="Sarah Kriesch &lt;sarah.kriesch@opensuse.org&gt;" date="1709812800">- Remove constraints file because improved memory usage for s390x</changelog>
  <changelog author="Aaron Puchert &lt;aaronpuchert@alice-dsl.net&gt;" date="1710244800">- Require LLVM &lt;= 17 for now, because LLVM 18 doesn't seem to work.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1715169600">- Upgrade to 15.7 (bsc#1224051):
  * bsc#1224038, CVE-2024-4317: Restrict visibility of pg_stats_ext
    and pg_stats_ext_exprs entries to the table owner. See the
    release notes for the steps that have to be taken to fix
    existing PostgreSQL instances.
  * Fix incompatibility with LLVM 18.
  * https://www.postgresql.org/docs/release/15.7/
- Prepare for PostgreSQL 17.
- Make sure all compilation and doc generation happens in %build.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1723291200">- Upgrade to 15.8 (bsc#1229013):
  * bsc#1229013, CVE-2024-7348 PostgreSQL relation replacement
    during pg_dump executes arbitrary SQL
  * https://www.postgresql.org/about/news/p-2910/
  * https://www.postgresql.org/docs/release/15.8/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1730808000">- Sync spec file from postgresql17.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1731499200">- Upgrade to 15.9:
  * CVE-2024-10976, bsc#1233323: Ensure cached plans are marked as
    dependent on the calling role when RLS applies to a
    non-top-level table reference.
  * CVE-2024-10977, bsc#1233325: Make libpq discard error messages
    received during SSL or GSS protocol negotiation.
  * CVE-2024-10978, bsc#1233326: Fix unintended interactions
    between SET SESSION AUTHORIZATION and SET ROLE
  * CVE-2024-10979, bsc#1233327: Prevent trusted PL/Perl code from
    changing environment variables.
  * https://www.postgresql.org/about/news/p-2955/
  * https://www.postgresql.org/docs/release/15.9/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1732017600">- Upgrade to 15.10
  * Repair ABI break for extensions that work with struct
    ResultRelInfo.
  * Restore functionality of ALTER {ROLE|DATABASE} SET role.
  * Fix cases where a logical replication slot's restart_lsn could
    go backwards.
  * Avoid deleting still-needed WAL files during pg_rewind.
  * Fix race conditions associated with dropping shared statistics
    entries.
  * Count index scans in contrib/bloom indexes in the statistics
    views, such as the pg_stat_user_indexes.idx_scan counter.
  * Fix crash when checking to see if an index's opclass options
    have changed.
  * Avoid assertion failure caused by disconnected NFA sub-graphs
    in regular expression parsing.
  * https://www.postgresql.org/about/news/p-2965/
  * https://www.postgresql.org/docs/release/15.10/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 15.11:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/15.11/
  * https://www.postgresql.org/about/news/-3015/
- Disable LLVM JIT on loongarch64</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 15.12:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/15.12/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 15.13:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/15.13/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Upgrade to 15.14:
  * https://www.postgresql.org/about/news/postgresql-176-1610-1514-1419-1322-and-18-beta-3-released-3118/
  * https://www.postgresql.org/docs/release/15.14/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1758801600">- Sync spec file from version 18.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Upgrade to 15.15:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/15.15/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 15.16:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/15.16/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 15.17 to fix two regressions in 15.16:
  * https://www.postgresql.org/docs/release/15.17/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
</package>
<package pkgid="4df552c33fc6217facc9d55466820221cb45ef024dbd665552918fdf68e6b5add9c3d2e30d0b6a827960fd00ebfde0b7b6005f86c75d7c5f5c6ac2d2ae3a03ff" name="postgresql15-docs" arch="noarch">
  <version epoch="0" ver="15.17" rel="87.2"/>
  <changelog author="Dominique Leuenberger &lt;dimstar@opensuse.org&gt;" date="1709208000">- Use %patch -P N instead of deprecated %patchN.</changelog>
  <changelog author="Sarah Kriesch &lt;sarah.kriesch@opensuse.org&gt;" date="1709812800">- Remove constraints file because improved memory usage for s390x</changelog>
  <changelog author="Aaron Puchert &lt;aaronpuchert@alice-dsl.net&gt;" date="1710244800">- Require LLVM &lt;= 17 for now, because LLVM 18 doesn't seem to work.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1715169600">- Upgrade to 15.7 (bsc#1224051):
  * bsc#1224038, CVE-2024-4317: Restrict visibility of pg_stats_ext
    and pg_stats_ext_exprs entries to the table owner. See the
    release notes for the steps that have to be taken to fix
    existing PostgreSQL instances.
  * Fix incompatibility with LLVM 18.
  * https://www.postgresql.org/docs/release/15.7/
- Prepare for PostgreSQL 17.
- Make sure all compilation and doc generation happens in %build.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1723291200">- Upgrade to 15.8 (bsc#1229013):
  * bsc#1229013, CVE-2024-7348 PostgreSQL relation replacement
    during pg_dump executes arbitrary SQL
  * https://www.postgresql.org/about/news/p-2910/
  * https://www.postgresql.org/docs/release/15.8/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1730808000">- Sync spec file from postgresql17.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1731499200">- Upgrade to 15.9:
  * CVE-2024-10976, bsc#1233323: Ensure cached plans are marked as
    dependent on the calling role when RLS applies to a
    non-top-level table reference.
  * CVE-2024-10977, bsc#1233325: Make libpq discard error messages
    received during SSL or GSS protocol negotiation.
  * CVE-2024-10978, bsc#1233326: Fix unintended interactions
    between SET SESSION AUTHORIZATION and SET ROLE
  * CVE-2024-10979, bsc#1233327: Prevent trusted PL/Perl code from
    changing environment variables.
  * https://www.postgresql.org/about/news/p-2955/
  * https://www.postgresql.org/docs/release/15.9/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1732017600">- Upgrade to 15.10
  * Repair ABI break for extensions that work with struct
    ResultRelInfo.
  * Restore functionality of ALTER {ROLE|DATABASE} SET role.
  * Fix cases where a logical replication slot's restart_lsn could
    go backwards.
  * Avoid deleting still-needed WAL files during pg_rewind.
  * Fix race conditions associated with dropping shared statistics
    entries.
  * Count index scans in contrib/bloom indexes in the statistics
    views, such as the pg_stat_user_indexes.idx_scan counter.
  * Fix crash when checking to see if an index's opclass options
    have changed.
  * Avoid assertion failure caused by disconnected NFA sub-graphs
    in regular expression parsing.
  * https://www.postgresql.org/about/news/p-2965/
  * https://www.postgresql.org/docs/release/15.10/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 15.11:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/15.11/
  * https://www.postgresql.org/about/news/-3015/
- Disable LLVM JIT on loongarch64</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 15.12:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/15.12/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 15.13:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/15.13/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Upgrade to 15.14:
  * https://www.postgresql.org/about/news/postgresql-176-1610-1514-1419-1322-and-18-beta-3-released-3118/
  * https://www.postgresql.org/docs/release/15.14/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1758801600">- Sync spec file from version 18.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Upgrade to 15.15:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/15.15/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 15.16:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/15.16/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 15.17 to fix two regressions in 15.16:
  * https://www.postgresql.org/docs/release/15.17/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
</package>
<package pkgid="17880f5134bed0a4f5e12babdbbe65cbf8ffb1596bb8fdc4aa545ed89cdfe5aeec56092aa678dc72470959e4b0a8deb9d8f80ceaf158b6926635777980dae9ac" name="postgresql15-docs" arch="noarch">
  <version epoch="0" ver="15.18" rel="97.2"/>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1715169600">- Upgrade to 15.7 (bsc#1224051):
  * bsc#1224038, CVE-2024-4317: Restrict visibility of pg_stats_ext
    and pg_stats_ext_exprs entries to the table owner. See the
    release notes for the steps that have to be taken to fix
    existing PostgreSQL instances.
  * Fix incompatibility with LLVM 18.
  * https://www.postgresql.org/docs/release/15.7/
- Prepare for PostgreSQL 17.
- Make sure all compilation and doc generation happens in %build.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1723291200">- Upgrade to 15.8 (bsc#1229013):
  * bsc#1229013, CVE-2024-7348 PostgreSQL relation replacement
    during pg_dump executes arbitrary SQL
  * https://www.postgresql.org/about/news/p-2910/
  * https://www.postgresql.org/docs/release/15.8/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1730808000">- Sync spec file from postgresql17.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1731499200">- Upgrade to 15.9:
  * CVE-2024-10976, bsc#1233323: Ensure cached plans are marked as
    dependent on the calling role when RLS applies to a
    non-top-level table reference.
  * CVE-2024-10977, bsc#1233325: Make libpq discard error messages
    received during SSL or GSS protocol negotiation.
  * CVE-2024-10978, bsc#1233326: Fix unintended interactions
    between SET SESSION AUTHORIZATION and SET ROLE
  * CVE-2024-10979, bsc#1233327: Prevent trusted PL/Perl code from
    changing environment variables.
  * https://www.postgresql.org/about/news/p-2955/
  * https://www.postgresql.org/docs/release/15.9/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1732017600">- Upgrade to 15.10
  * Repair ABI break for extensions that work with struct
    ResultRelInfo.
  * Restore functionality of ALTER {ROLE|DATABASE} SET role.
  * Fix cases where a logical replication slot's restart_lsn could
    go backwards.
  * Avoid deleting still-needed WAL files during pg_rewind.
  * Fix race conditions associated with dropping shared statistics
    entries.
  * Count index scans in contrib/bloom indexes in the statistics
    views, such as the pg_stat_user_indexes.idx_scan counter.
  * Fix crash when checking to see if an index's opclass options
    have changed.
  * Avoid assertion failure caused by disconnected NFA sub-graphs
    in regular expression parsing.
  * https://www.postgresql.org/about/news/p-2965/
  * https://www.postgresql.org/docs/release/15.10/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 15.11:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/15.11/
  * https://www.postgresql.org/about/news/-3015/
- Disable LLVM JIT on loongarch64</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 15.12:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/15.12/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 15.13:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/15.13/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Upgrade to 15.14:
  * https://www.postgresql.org/about/news/postgresql-176-1610-1514-1419-1322-and-18-beta-3-released-3118/
  * https://www.postgresql.org/docs/release/15.14/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1758801600">- Sync spec file from version 18.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Upgrade to 15.15:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/15.15/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 15.16:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/15.16/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 15.17 to fix two regressions in 15.16:
  * https://www.postgresql.org/docs/release/15.17/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1774872000">- Get rid of update-alternatives for openSUSE/SLE 16.0 and newer
  to support immutable systems and transactional updates.
  (jsc#PED-14823)</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1777550400">- bsc#1263804: After dropping update-alternatives we have to
  package /usr/bin/pg_config as an actual symlink, not %ghost.
- Fix spelling of build conditionals.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1778673600">- Update to version 15.18:
  * bsc#1265172, CVE-2026-6472: ensure the user has CREATE
    privilege on the schema specified
  * bsc#1265173, CVE-2026-6473: integer overflows in
    memory-allocation calculations
  * bsc#1265174, CVE-2026-6474: Guard against malicious time zone
    names
  * bsc#1265175, CVE-2026-6475: Prevent path traversal in
    pg_basebackup and pg_rewind
  * bsc#1265177, CVE-2026-6477: Mark PQfn() as unsafe, and avoid
    using it within libpq
  * bsc#1265178, CVE-2026-6478: Use timing-safe string comparisons
    in authentication code
  * bsc#1265179, CVE-2026-6479: Prevent unbounded recursion while
    processing startup packets
  * bsc#1265181, CVE-2026-6637: Prevent SQL injection and buffer
    overruns in contrib/spi
  * https://www.postgresql.org/docs/release/15.18/</changelog>
</package>
<package pkgid="3bf1974181beecd646561f8a5a1e573b59736958918c68849488b27dc3f752e4676c9d668b488fed6ac46d885575d3cd14ae405a8051206a892de413b67b89d3" name="postgresql15-llvmjit" arch="ppc64le">
  <version epoch="0" ver="15.17" rel="86.1"/>
  <changelog author="Dominique Leuenberger &lt;dimstar@opensuse.org&gt;" date="1709208000">- Use %patch -P N instead of deprecated %patchN.</changelog>
  <changelog author="Sarah Kriesch &lt;sarah.kriesch@opensuse.org&gt;" date="1709812800">- Remove constraints file because improved memory usage for s390x</changelog>
  <changelog author="Aaron Puchert &lt;aaronpuchert@alice-dsl.net&gt;" date="1710244800">- Require LLVM &lt;= 17 for now, because LLVM 18 doesn't seem to work.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1715169600">- Upgrade to 15.7 (bsc#1224051):
  * bsc#1224038, CVE-2024-4317: Restrict visibility of pg_stats_ext
    and pg_stats_ext_exprs entries to the table owner. See the
    release notes for the steps that have to be taken to fix
    existing PostgreSQL instances.
  * Fix incompatibility with LLVM 18.
  * https://www.postgresql.org/docs/release/15.7/
- Prepare for PostgreSQL 17.
- Make sure all compilation and doc generation happens in %build.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1723291200">- Upgrade to 15.8 (bsc#1229013):
  * bsc#1229013, CVE-2024-7348 PostgreSQL relation replacement
    during pg_dump executes arbitrary SQL
  * https://www.postgresql.org/about/news/p-2910/
  * https://www.postgresql.org/docs/release/15.8/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1730808000">- Sync spec file from postgresql17.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1731499200">- Upgrade to 15.9:
  * CVE-2024-10976, bsc#1233323: Ensure cached plans are marked as
    dependent on the calling role when RLS applies to a
    non-top-level table reference.
  * CVE-2024-10977, bsc#1233325: Make libpq discard error messages
    received during SSL or GSS protocol negotiation.
  * CVE-2024-10978, bsc#1233326: Fix unintended interactions
    between SET SESSION AUTHORIZATION and SET ROLE
  * CVE-2024-10979, bsc#1233327: Prevent trusted PL/Perl code from
    changing environment variables.
  * https://www.postgresql.org/about/news/p-2955/
  * https://www.postgresql.org/docs/release/15.9/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1732017600">- Upgrade to 15.10
  * Repair ABI break for extensions that work with struct
    ResultRelInfo.
  * Restore functionality of ALTER {ROLE|DATABASE} SET role.
  * Fix cases where a logical replication slot's restart_lsn could
    go backwards.
  * Avoid deleting still-needed WAL files during pg_rewind.
  * Fix race conditions associated with dropping shared statistics
    entries.
  * Count index scans in contrib/bloom indexes in the statistics
    views, such as the pg_stat_user_indexes.idx_scan counter.
  * Fix crash when checking to see if an index's opclass options
    have changed.
  * Avoid assertion failure caused by disconnected NFA sub-graphs
    in regular expression parsing.
  * https://www.postgresql.org/about/news/p-2965/
  * https://www.postgresql.org/docs/release/15.10/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 15.11:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/15.11/
  * https://www.postgresql.org/about/news/-3015/
- Disable LLVM JIT on loongarch64</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 15.12:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/15.12/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 15.13:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/15.13/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Upgrade to 15.14:
  * https://www.postgresql.org/about/news/postgresql-176-1610-1514-1419-1322-and-18-beta-3-released-3118/
  * https://www.postgresql.org/docs/release/15.14/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1758801600">- Sync spec file from version 18.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Upgrade to 15.15:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/15.15/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 15.16:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/15.16/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 15.17 to fix two regressions in 15.16:
  * https://www.postgresql.org/docs/release/15.17/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
</package>
<package pkgid="4c8893743d634ecdcbff80547e3f203d1b6e02197e93032a1480b51f0079c68138a7f74ee9c89e2047e33479604a334ede7bcf86fc538f248aee387631e8ace9" name="postgresql15-llvmjit" arch="aarch64">
  <version epoch="0" ver="15.17" rel="87.2"/>
  <changelog author="Dominique Leuenberger &lt;dimstar@opensuse.org&gt;" date="1709208000">- Use %patch -P N instead of deprecated %patchN.</changelog>
  <changelog author="Sarah Kriesch &lt;sarah.kriesch@opensuse.org&gt;" date="1709812800">- Remove constraints file because improved memory usage for s390x</changelog>
  <changelog author="Aaron Puchert &lt;aaronpuchert@alice-dsl.net&gt;" date="1710244800">- Require LLVM &lt;= 17 for now, because LLVM 18 doesn't seem to work.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1715169600">- Upgrade to 15.7 (bsc#1224051):
  * bsc#1224038, CVE-2024-4317: Restrict visibility of pg_stats_ext
    and pg_stats_ext_exprs entries to the table owner. See the
    release notes for the steps that have to be taken to fix
    existing PostgreSQL instances.
  * Fix incompatibility with LLVM 18.
  * https://www.postgresql.org/docs/release/15.7/
- Prepare for PostgreSQL 17.
- Make sure all compilation and doc generation happens in %build.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1723291200">- Upgrade to 15.8 (bsc#1229013):
  * bsc#1229013, CVE-2024-7348 PostgreSQL relation replacement
    during pg_dump executes arbitrary SQL
  * https://www.postgresql.org/about/news/p-2910/
  * https://www.postgresql.org/docs/release/15.8/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1730808000">- Sync spec file from postgresql17.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1731499200">- Upgrade to 15.9:
  * CVE-2024-10976, bsc#1233323: Ensure cached plans are marked as
    dependent on the calling role when RLS applies to a
    non-top-level table reference.
  * CVE-2024-10977, bsc#1233325: Make libpq discard error messages
    received during SSL or GSS protocol negotiation.
  * CVE-2024-10978, bsc#1233326: Fix unintended interactions
    between SET SESSION AUTHORIZATION and SET ROLE
  * CVE-2024-10979, bsc#1233327: Prevent trusted PL/Perl code from
    changing environment variables.
  * https://www.postgresql.org/about/news/p-2955/
  * https://www.postgresql.org/docs/release/15.9/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1732017600">- Upgrade to 15.10
  * Repair ABI break for extensions that work with struct
    ResultRelInfo.
  * Restore functionality of ALTER {ROLE|DATABASE} SET role.
  * Fix cases where a logical replication slot's restart_lsn could
    go backwards.
  * Avoid deleting still-needed WAL files during pg_rewind.
  * Fix race conditions associated with dropping shared statistics
    entries.
  * Count index scans in contrib/bloom indexes in the statistics
    views, such as the pg_stat_user_indexes.idx_scan counter.
  * Fix crash when checking to see if an index's opclass options
    have changed.
  * Avoid assertion failure caused by disconnected NFA sub-graphs
    in regular expression parsing.
  * https://www.postgresql.org/about/news/p-2965/
  * https://www.postgresql.org/docs/release/15.10/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 15.11:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/15.11/
  * https://www.postgresql.org/about/news/-3015/
- Disable LLVM JIT on loongarch64</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 15.12:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/15.12/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 15.13:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/15.13/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Upgrade to 15.14:
  * https://www.postgresql.org/about/news/postgresql-176-1610-1514-1419-1322-and-18-beta-3-released-3118/
  * https://www.postgresql.org/docs/release/15.14/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1758801600">- Sync spec file from version 18.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Upgrade to 15.15:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/15.15/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 15.16:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/15.16/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 15.17 to fix two regressions in 15.16:
  * https://www.postgresql.org/docs/release/15.17/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
</package>
<package pkgid="4a718e4dc91193810cbb2dc500eebcaf815933e505a1db41aea06f203b9400be7178cbf4740635390cf887d8ba7031b10a14f12f84755333e7cbd50dbf9dfb43" name="postgresql15-llvmjit" arch="s390x">
  <version epoch="0" ver="15.17" rel="87.2"/>
  <changelog author="Dominique Leuenberger &lt;dimstar@opensuse.org&gt;" date="1709208000">- Use %patch -P N instead of deprecated %patchN.</changelog>
  <changelog author="Sarah Kriesch &lt;sarah.kriesch@opensuse.org&gt;" date="1709812800">- Remove constraints file because improved memory usage for s390x</changelog>
  <changelog author="Aaron Puchert &lt;aaronpuchert@alice-dsl.net&gt;" date="1710244800">- Require LLVM &lt;= 17 for now, because LLVM 18 doesn't seem to work.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1715169600">- Upgrade to 15.7 (bsc#1224051):
  * bsc#1224038, CVE-2024-4317: Restrict visibility of pg_stats_ext
    and pg_stats_ext_exprs entries to the table owner. See the
    release notes for the steps that have to be taken to fix
    existing PostgreSQL instances.
  * Fix incompatibility with LLVM 18.
  * https://www.postgresql.org/docs/release/15.7/
- Prepare for PostgreSQL 17.
- Make sure all compilation and doc generation happens in %build.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1723291200">- Upgrade to 15.8 (bsc#1229013):
  * bsc#1229013, CVE-2024-7348 PostgreSQL relation replacement
    during pg_dump executes arbitrary SQL
  * https://www.postgresql.org/about/news/p-2910/
  * https://www.postgresql.org/docs/release/15.8/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1730808000">- Sync spec file from postgresql17.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1731499200">- Upgrade to 15.9:
  * CVE-2024-10976, bsc#1233323: Ensure cached plans are marked as
    dependent on the calling role when RLS applies to a
    non-top-level table reference.
  * CVE-2024-10977, bsc#1233325: Make libpq discard error messages
    received during SSL or GSS protocol negotiation.
  * CVE-2024-10978, bsc#1233326: Fix unintended interactions
    between SET SESSION AUTHORIZATION and SET ROLE
  * CVE-2024-10979, bsc#1233327: Prevent trusted PL/Perl code from
    changing environment variables.
  * https://www.postgresql.org/about/news/p-2955/
  * https://www.postgresql.org/docs/release/15.9/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1732017600">- Upgrade to 15.10
  * Repair ABI break for extensions that work with struct
    ResultRelInfo.
  * Restore functionality of ALTER {ROLE|DATABASE} SET role.
  * Fix cases where a logical replication slot's restart_lsn could
    go backwards.
  * Avoid deleting still-needed WAL files during pg_rewind.
  * Fix race conditions associated with dropping shared statistics
    entries.
  * Count index scans in contrib/bloom indexes in the statistics
    views, such as the pg_stat_user_indexes.idx_scan counter.
  * Fix crash when checking to see if an index's opclass options
    have changed.
  * Avoid assertion failure caused by disconnected NFA sub-graphs
    in regular expression parsing.
  * https://www.postgresql.org/about/news/p-2965/
  * https://www.postgresql.org/docs/release/15.10/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 15.11:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/15.11/
  * https://www.postgresql.org/about/news/-3015/
- Disable LLVM JIT on loongarch64</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 15.12:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/15.12/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 15.13:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/15.13/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Upgrade to 15.14:
  * https://www.postgresql.org/about/news/postgresql-176-1610-1514-1419-1322-and-18-beta-3-released-3118/
  * https://www.postgresql.org/docs/release/15.14/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1758801600">- Sync spec file from version 18.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Upgrade to 15.15:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/15.15/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 15.16:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/15.16/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 15.17 to fix two regressions in 15.16:
  * https://www.postgresql.org/docs/release/15.17/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
</package>
<package pkgid="831128f2d895113d28188be59a4a7183bdd58e0234eae98fa853a0a93bd7f272ab0405bd3271f2d18eb2b86a5b92ab7db2c58e4a55cc9f467d5014d016e55eca" name="postgresql15-llvmjit" arch="x86_64">
  <version epoch="0" ver="15.18" rel="97.2"/>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1715169600">- Upgrade to 15.7 (bsc#1224051):
  * bsc#1224038, CVE-2024-4317: Restrict visibility of pg_stats_ext
    and pg_stats_ext_exprs entries to the table owner. See the
    release notes for the steps that have to be taken to fix
    existing PostgreSQL instances.
  * Fix incompatibility with LLVM 18.
  * https://www.postgresql.org/docs/release/15.7/
- Prepare for PostgreSQL 17.
- Make sure all compilation and doc generation happens in %build.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1723291200">- Upgrade to 15.8 (bsc#1229013):
  * bsc#1229013, CVE-2024-7348 PostgreSQL relation replacement
    during pg_dump executes arbitrary SQL
  * https://www.postgresql.org/about/news/p-2910/
  * https://www.postgresql.org/docs/release/15.8/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1730808000">- Sync spec file from postgresql17.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1731499200">- Upgrade to 15.9:
  * CVE-2024-10976, bsc#1233323: Ensure cached plans are marked as
    dependent on the calling role when RLS applies to a
    non-top-level table reference.
  * CVE-2024-10977, bsc#1233325: Make libpq discard error messages
    received during SSL or GSS protocol negotiation.
  * CVE-2024-10978, bsc#1233326: Fix unintended interactions
    between SET SESSION AUTHORIZATION and SET ROLE
  * CVE-2024-10979, bsc#1233327: Prevent trusted PL/Perl code from
    changing environment variables.
  * https://www.postgresql.org/about/news/p-2955/
  * https://www.postgresql.org/docs/release/15.9/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1732017600">- Upgrade to 15.10
  * Repair ABI break for extensions that work with struct
    ResultRelInfo.
  * Restore functionality of ALTER {ROLE|DATABASE} SET role.
  * Fix cases where a logical replication slot's restart_lsn could
    go backwards.
  * Avoid deleting still-needed WAL files during pg_rewind.
  * Fix race conditions associated with dropping shared statistics
    entries.
  * Count index scans in contrib/bloom indexes in the statistics
    views, such as the pg_stat_user_indexes.idx_scan counter.
  * Fix crash when checking to see if an index's opclass options
    have changed.
  * Avoid assertion failure caused by disconnected NFA sub-graphs
    in regular expression parsing.
  * https://www.postgresql.org/about/news/p-2965/
  * https://www.postgresql.org/docs/release/15.10/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 15.11:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/15.11/
  * https://www.postgresql.org/about/news/-3015/
- Disable LLVM JIT on loongarch64</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 15.12:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/15.12/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 15.13:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/15.13/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Upgrade to 15.14:
  * https://www.postgresql.org/about/news/postgresql-176-1610-1514-1419-1322-and-18-beta-3-released-3118/
  * https://www.postgresql.org/docs/release/15.14/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1758801600">- Sync spec file from version 18.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Upgrade to 15.15:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/15.15/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 15.16:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/15.16/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 15.17 to fix two regressions in 15.16:
  * https://www.postgresql.org/docs/release/15.17/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1774872000">- Get rid of update-alternatives for openSUSE/SLE 16.0 and newer
  to support immutable systems and transactional updates.
  (jsc#PED-14823)</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1777550400">- bsc#1263804: After dropping update-alternatives we have to
  package /usr/bin/pg_config as an actual symlink, not %ghost.
- Fix spelling of build conditionals.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1778673600">- Update to version 15.18:
  * bsc#1265172, CVE-2026-6472: ensure the user has CREATE
    privilege on the schema specified
  * bsc#1265173, CVE-2026-6473: integer overflows in
    memory-allocation calculations
  * bsc#1265174, CVE-2026-6474: Guard against malicious time zone
    names
  * bsc#1265175, CVE-2026-6475: Prevent path traversal in
    pg_basebackup and pg_rewind
  * bsc#1265177, CVE-2026-6477: Mark PQfn() as unsafe, and avoid
    using it within libpq
  * bsc#1265178, CVE-2026-6478: Use timing-safe string comparisons
    in authentication code
  * bsc#1265179, CVE-2026-6479: Prevent unbounded recursion while
    processing startup packets
  * bsc#1265181, CVE-2026-6637: Prevent SQL injection and buffer
    overruns in contrib/spi
  * https://www.postgresql.org/docs/release/15.18/</changelog>
</package>
<package pkgid="e6477bc2b58bc90e826cd0fde505998d79a008e6d601a2b77723497c6cb6910cc8b19254266466ee35272242503a597c186c7b4252c2976577b56fd869e2297c" name="postgresql15-llvmjit-devel" arch="ppc64le">
  <version epoch="0" ver="15.17" rel="86.1"/>
  <changelog author="Dominique Leuenberger &lt;dimstar@opensuse.org&gt;" date="1709208000">- Use %patch -P N instead of deprecated %patchN.</changelog>
  <changelog author="Sarah Kriesch &lt;sarah.kriesch@opensuse.org&gt;" date="1709812800">- Remove constraints file because improved memory usage for s390x</changelog>
  <changelog author="Aaron Puchert &lt;aaronpuchert@alice-dsl.net&gt;" date="1710244800">- Require LLVM &lt;= 17 for now, because LLVM 18 doesn't seem to work.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1715169600">- Upgrade to 15.7 (bsc#1224051):
  * bsc#1224038, CVE-2024-4317: Restrict visibility of pg_stats_ext
    and pg_stats_ext_exprs entries to the table owner. See the
    release notes for the steps that have to be taken to fix
    existing PostgreSQL instances.
  * Fix incompatibility with LLVM 18.
  * https://www.postgresql.org/docs/release/15.7/
- Prepare for PostgreSQL 17.
- Make sure all compilation and doc generation happens in %build.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1723291200">- Upgrade to 15.8 (bsc#1229013):
  * bsc#1229013, CVE-2024-7348 PostgreSQL relation replacement
    during pg_dump executes arbitrary SQL
  * https://www.postgresql.org/about/news/p-2910/
  * https://www.postgresql.org/docs/release/15.8/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1730808000">- Sync spec file from postgresql17.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1731499200">- Upgrade to 15.9:
  * CVE-2024-10976, bsc#1233323: Ensure cached plans are marked as
    dependent on the calling role when RLS applies to a
    non-top-level table reference.
  * CVE-2024-10977, bsc#1233325: Make libpq discard error messages
    received during SSL or GSS protocol negotiation.
  * CVE-2024-10978, bsc#1233326: Fix unintended interactions
    between SET SESSION AUTHORIZATION and SET ROLE
  * CVE-2024-10979, bsc#1233327: Prevent trusted PL/Perl code from
    changing environment variables.
  * https://www.postgresql.org/about/news/p-2955/
  * https://www.postgresql.org/docs/release/15.9/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1732017600">- Upgrade to 15.10
  * Repair ABI break for extensions that work with struct
    ResultRelInfo.
  * Restore functionality of ALTER {ROLE|DATABASE} SET role.
  * Fix cases where a logical replication slot's restart_lsn could
    go backwards.
  * Avoid deleting still-needed WAL files during pg_rewind.
  * Fix race conditions associated with dropping shared statistics
    entries.
  * Count index scans in contrib/bloom indexes in the statistics
    views, such as the pg_stat_user_indexes.idx_scan counter.
  * Fix crash when checking to see if an index's opclass options
    have changed.
  * Avoid assertion failure caused by disconnected NFA sub-graphs
    in regular expression parsing.
  * https://www.postgresql.org/about/news/p-2965/
  * https://www.postgresql.org/docs/release/15.10/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 15.11:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/15.11/
  * https://www.postgresql.org/about/news/-3015/
- Disable LLVM JIT on loongarch64</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 15.12:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/15.12/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 15.13:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/15.13/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Upgrade to 15.14:
  * https://www.postgresql.org/about/news/postgresql-176-1610-1514-1419-1322-and-18-beta-3-released-3118/
  * https://www.postgresql.org/docs/release/15.14/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1758801600">- Sync spec file from version 18.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Upgrade to 15.15:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/15.15/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 15.16:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/15.16/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 15.17 to fix two regressions in 15.16:
  * https://www.postgresql.org/docs/release/15.17/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
</package>
<package pkgid="3a7178e19471dcc8afb6654903f9242cd98394514642fe1d3093c5212efa74ca8a0304574cd55da9b809bdd7d5dfe96584dace02137d0c0f0ef740e06ffa08f5" name="postgresql15-llvmjit-devel" arch="aarch64">
  <version epoch="0" ver="15.17" rel="87.2"/>
  <changelog author="Dominique Leuenberger &lt;dimstar@opensuse.org&gt;" date="1709208000">- Use %patch -P N instead of deprecated %patchN.</changelog>
  <changelog author="Sarah Kriesch &lt;sarah.kriesch@opensuse.org&gt;" date="1709812800">- Remove constraints file because improved memory usage for s390x</changelog>
  <changelog author="Aaron Puchert &lt;aaronpuchert@alice-dsl.net&gt;" date="1710244800">- Require LLVM &lt;= 17 for now, because LLVM 18 doesn't seem to work.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1715169600">- Upgrade to 15.7 (bsc#1224051):
  * bsc#1224038, CVE-2024-4317: Restrict visibility of pg_stats_ext
    and pg_stats_ext_exprs entries to the table owner. See the
    release notes for the steps that have to be taken to fix
    existing PostgreSQL instances.
  * Fix incompatibility with LLVM 18.
  * https://www.postgresql.org/docs/release/15.7/
- Prepare for PostgreSQL 17.
- Make sure all compilation and doc generation happens in %build.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1723291200">- Upgrade to 15.8 (bsc#1229013):
  * bsc#1229013, CVE-2024-7348 PostgreSQL relation replacement
    during pg_dump executes arbitrary SQL
  * https://www.postgresql.org/about/news/p-2910/
  * https://www.postgresql.org/docs/release/15.8/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1730808000">- Sync spec file from postgresql17.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1731499200">- Upgrade to 15.9:
  * CVE-2024-10976, bsc#1233323: Ensure cached plans are marked as
    dependent on the calling role when RLS applies to a
    non-top-level table reference.
  * CVE-2024-10977, bsc#1233325: Make libpq discard error messages
    received during SSL or GSS protocol negotiation.
  * CVE-2024-10978, bsc#1233326: Fix unintended interactions
    between SET SESSION AUTHORIZATION and SET ROLE
  * CVE-2024-10979, bsc#1233327: Prevent trusted PL/Perl code from
    changing environment variables.
  * https://www.postgresql.org/about/news/p-2955/
  * https://www.postgresql.org/docs/release/15.9/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1732017600">- Upgrade to 15.10
  * Repair ABI break for extensions that work with struct
    ResultRelInfo.
  * Restore functionality of ALTER {ROLE|DATABASE} SET role.
  * Fix cases where a logical replication slot's restart_lsn could
    go backwards.
  * Avoid deleting still-needed WAL files during pg_rewind.
  * Fix race conditions associated with dropping shared statistics
    entries.
  * Count index scans in contrib/bloom indexes in the statistics
    views, such as the pg_stat_user_indexes.idx_scan counter.
  * Fix crash when checking to see if an index's opclass options
    have changed.
  * Avoid assertion failure caused by disconnected NFA sub-graphs
    in regular expression parsing.
  * https://www.postgresql.org/about/news/p-2965/
  * https://www.postgresql.org/docs/release/15.10/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 15.11:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/15.11/
  * https://www.postgresql.org/about/news/-3015/
- Disable LLVM JIT on loongarch64</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 15.12:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/15.12/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 15.13:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/15.13/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Upgrade to 15.14:
  * https://www.postgresql.org/about/news/postgresql-176-1610-1514-1419-1322-and-18-beta-3-released-3118/
  * https://www.postgresql.org/docs/release/15.14/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1758801600">- Sync spec file from version 18.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Upgrade to 15.15:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/15.15/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 15.16:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/15.16/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 15.17 to fix two regressions in 15.16:
  * https://www.postgresql.org/docs/release/15.17/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
</package>
<package pkgid="69b074927c2ff465d1bb3c602a46e210ec6119434441850029d9ef70a3bf2a2104daf7bc504306ed86983976e7f6bd2dcedb048c7e61bc0d0ca97d07a3a17a82" name="postgresql15-llvmjit-devel" arch="s390x">
  <version epoch="0" ver="15.17" rel="87.2"/>
  <changelog author="Dominique Leuenberger &lt;dimstar@opensuse.org&gt;" date="1709208000">- Use %patch -P N instead of deprecated %patchN.</changelog>
  <changelog author="Sarah Kriesch &lt;sarah.kriesch@opensuse.org&gt;" date="1709812800">- Remove constraints file because improved memory usage for s390x</changelog>
  <changelog author="Aaron Puchert &lt;aaronpuchert@alice-dsl.net&gt;" date="1710244800">- Require LLVM &lt;= 17 for now, because LLVM 18 doesn't seem to work.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1715169600">- Upgrade to 15.7 (bsc#1224051):
  * bsc#1224038, CVE-2024-4317: Restrict visibility of pg_stats_ext
    and pg_stats_ext_exprs entries to the table owner. See the
    release notes for the steps that have to be taken to fix
    existing PostgreSQL instances.
  * Fix incompatibility with LLVM 18.
  * https://www.postgresql.org/docs/release/15.7/
- Prepare for PostgreSQL 17.
- Make sure all compilation and doc generation happens in %build.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1723291200">- Upgrade to 15.8 (bsc#1229013):
  * bsc#1229013, CVE-2024-7348 PostgreSQL relation replacement
    during pg_dump executes arbitrary SQL
  * https://www.postgresql.org/about/news/p-2910/
  * https://www.postgresql.org/docs/release/15.8/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1730808000">- Sync spec file from postgresql17.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1731499200">- Upgrade to 15.9:
  * CVE-2024-10976, bsc#1233323: Ensure cached plans are marked as
    dependent on the calling role when RLS applies to a
    non-top-level table reference.
  * CVE-2024-10977, bsc#1233325: Make libpq discard error messages
    received during SSL or GSS protocol negotiation.
  * CVE-2024-10978, bsc#1233326: Fix unintended interactions
    between SET SESSION AUTHORIZATION and SET ROLE
  * CVE-2024-10979, bsc#1233327: Prevent trusted PL/Perl code from
    changing environment variables.
  * https://www.postgresql.org/about/news/p-2955/
  * https://www.postgresql.org/docs/release/15.9/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1732017600">- Upgrade to 15.10
  * Repair ABI break for extensions that work with struct
    ResultRelInfo.
  * Restore functionality of ALTER {ROLE|DATABASE} SET role.
  * Fix cases where a logical replication slot's restart_lsn could
    go backwards.
  * Avoid deleting still-needed WAL files during pg_rewind.
  * Fix race conditions associated with dropping shared statistics
    entries.
  * Count index scans in contrib/bloom indexes in the statistics
    views, such as the pg_stat_user_indexes.idx_scan counter.
  * Fix crash when checking to see if an index's opclass options
    have changed.
  * Avoid assertion failure caused by disconnected NFA sub-graphs
    in regular expression parsing.
  * https://www.postgresql.org/about/news/p-2965/
  * https://www.postgresql.org/docs/release/15.10/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 15.11:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/15.11/
  * https://www.postgresql.org/about/news/-3015/
- Disable LLVM JIT on loongarch64</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 15.12:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/15.12/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 15.13:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/15.13/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Upgrade to 15.14:
  * https://www.postgresql.org/about/news/postgresql-176-1610-1514-1419-1322-and-18-beta-3-released-3118/
  * https://www.postgresql.org/docs/release/15.14/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1758801600">- Sync spec file from version 18.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Upgrade to 15.15:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/15.15/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 15.16:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/15.16/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 15.17 to fix two regressions in 15.16:
  * https://www.postgresql.org/docs/release/15.17/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
</package>
<package pkgid="6dc66f08e2aa717c8f27c7669db445bdd4824de930b8a4810444f265d2747173fed8d89a9101f3c6096001ee39aa0019c787909e8859f0f5040fe9bff4355c4c" name="postgresql15-llvmjit-devel" arch="x86_64">
  <version epoch="0" ver="15.18" rel="97.2"/>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1715169600">- Upgrade to 15.7 (bsc#1224051):
  * bsc#1224038, CVE-2024-4317: Restrict visibility of pg_stats_ext
    and pg_stats_ext_exprs entries to the table owner. See the
    release notes for the steps that have to be taken to fix
    existing PostgreSQL instances.
  * Fix incompatibility with LLVM 18.
  * https://www.postgresql.org/docs/release/15.7/
- Prepare for PostgreSQL 17.
- Make sure all compilation and doc generation happens in %build.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1723291200">- Upgrade to 15.8 (bsc#1229013):
  * bsc#1229013, CVE-2024-7348 PostgreSQL relation replacement
    during pg_dump executes arbitrary SQL
  * https://www.postgresql.org/about/news/p-2910/
  * https://www.postgresql.org/docs/release/15.8/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1730808000">- Sync spec file from postgresql17.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1731499200">- Upgrade to 15.9:
  * CVE-2024-10976, bsc#1233323: Ensure cached plans are marked as
    dependent on the calling role when RLS applies to a
    non-top-level table reference.
  * CVE-2024-10977, bsc#1233325: Make libpq discard error messages
    received during SSL or GSS protocol negotiation.
  * CVE-2024-10978, bsc#1233326: Fix unintended interactions
    between SET SESSION AUTHORIZATION and SET ROLE
  * CVE-2024-10979, bsc#1233327: Prevent trusted PL/Perl code from
    changing environment variables.
  * https://www.postgresql.org/about/news/p-2955/
  * https://www.postgresql.org/docs/release/15.9/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1732017600">- Upgrade to 15.10
  * Repair ABI break for extensions that work with struct
    ResultRelInfo.
  * Restore functionality of ALTER {ROLE|DATABASE} SET role.
  * Fix cases where a logical replication slot's restart_lsn could
    go backwards.
  * Avoid deleting still-needed WAL files during pg_rewind.
  * Fix race conditions associated with dropping shared statistics
    entries.
  * Count index scans in contrib/bloom indexes in the statistics
    views, such as the pg_stat_user_indexes.idx_scan counter.
  * Fix crash when checking to see if an index's opclass options
    have changed.
  * Avoid assertion failure caused by disconnected NFA sub-graphs
    in regular expression parsing.
  * https://www.postgresql.org/about/news/p-2965/
  * https://www.postgresql.org/docs/release/15.10/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 15.11:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/15.11/
  * https://www.postgresql.org/about/news/-3015/
- Disable LLVM JIT on loongarch64</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 15.12:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/15.12/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 15.13:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/15.13/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Upgrade to 15.14:
  * https://www.postgresql.org/about/news/postgresql-176-1610-1514-1419-1322-and-18-beta-3-released-3118/
  * https://www.postgresql.org/docs/release/15.14/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1758801600">- Sync spec file from version 18.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Upgrade to 15.15:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/15.15/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 15.16:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/15.16/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 15.17 to fix two regressions in 15.16:
  * https://www.postgresql.org/docs/release/15.17/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1774872000">- Get rid of update-alternatives for openSUSE/SLE 16.0 and newer
  to support immutable systems and transactional updates.
  (jsc#PED-14823)</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1777550400">- bsc#1263804: After dropping update-alternatives we have to
  package /usr/bin/pg_config as an actual symlink, not %ghost.
- Fix spelling of build conditionals.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1778673600">- Update to version 15.18:
  * bsc#1265172, CVE-2026-6472: ensure the user has CREATE
    privilege on the schema specified
  * bsc#1265173, CVE-2026-6473: integer overflows in
    memory-allocation calculations
  * bsc#1265174, CVE-2026-6474: Guard against malicious time zone
    names
  * bsc#1265175, CVE-2026-6475: Prevent path traversal in
    pg_basebackup and pg_rewind
  * bsc#1265177, CVE-2026-6477: Mark PQfn() as unsafe, and avoid
    using it within libpq
  * bsc#1265178, CVE-2026-6478: Use timing-safe string comparisons
    in authentication code
  * bsc#1265179, CVE-2026-6479: Prevent unbounded recursion while
    processing startup packets
  * bsc#1265181, CVE-2026-6637: Prevent SQL injection and buffer
    overruns in contrib/spi
  * https://www.postgresql.org/docs/release/15.18/</changelog>
</package>
<package pkgid="97290551f6574c017805c131957d456c875491060144eeca9522bc254386e8690f4cf13b2bdc105c577ff926b7309ef73aa6d1828339f7c3e2e0c260ac328954" name="postgresql15-plperl" arch="ppc64le">
  <version epoch="0" ver="15.17" rel="86.1"/>
  <changelog author="Dominique Leuenberger &lt;dimstar@opensuse.org&gt;" date="1709208000">- Use %patch -P N instead of deprecated %patchN.</changelog>
  <changelog author="Sarah Kriesch &lt;sarah.kriesch@opensuse.org&gt;" date="1709812800">- Remove constraints file because improved memory usage for s390x</changelog>
  <changelog author="Aaron Puchert &lt;aaronpuchert@alice-dsl.net&gt;" date="1710244800">- Require LLVM &lt;= 17 for now, because LLVM 18 doesn't seem to work.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1715169600">- Upgrade to 15.7 (bsc#1224051):
  * bsc#1224038, CVE-2024-4317: Restrict visibility of pg_stats_ext
    and pg_stats_ext_exprs entries to the table owner. See the
    release notes for the steps that have to be taken to fix
    existing PostgreSQL instances.
  * Fix incompatibility with LLVM 18.
  * https://www.postgresql.org/docs/release/15.7/
- Prepare for PostgreSQL 17.
- Make sure all compilation and doc generation happens in %build.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1723291200">- Upgrade to 15.8 (bsc#1229013):
  * bsc#1229013, CVE-2024-7348 PostgreSQL relation replacement
    during pg_dump executes arbitrary SQL
  * https://www.postgresql.org/about/news/p-2910/
  * https://www.postgresql.org/docs/release/15.8/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1730808000">- Sync spec file from postgresql17.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1731499200">- Upgrade to 15.9:
  * CVE-2024-10976, bsc#1233323: Ensure cached plans are marked as
    dependent on the calling role when RLS applies to a
    non-top-level table reference.
  * CVE-2024-10977, bsc#1233325: Make libpq discard error messages
    received during SSL or GSS protocol negotiation.
  * CVE-2024-10978, bsc#1233326: Fix unintended interactions
    between SET SESSION AUTHORIZATION and SET ROLE
  * CVE-2024-10979, bsc#1233327: Prevent trusted PL/Perl code from
    changing environment variables.
  * https://www.postgresql.org/about/news/p-2955/
  * https://www.postgresql.org/docs/release/15.9/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1732017600">- Upgrade to 15.10
  * Repair ABI break for extensions that work with struct
    ResultRelInfo.
  * Restore functionality of ALTER {ROLE|DATABASE} SET role.
  * Fix cases where a logical replication slot's restart_lsn could
    go backwards.
  * Avoid deleting still-needed WAL files during pg_rewind.
  * Fix race conditions associated with dropping shared statistics
    entries.
  * Count index scans in contrib/bloom indexes in the statistics
    views, such as the pg_stat_user_indexes.idx_scan counter.
  * Fix crash when checking to see if an index's opclass options
    have changed.
  * Avoid assertion failure caused by disconnected NFA sub-graphs
    in regular expression parsing.
  * https://www.postgresql.org/about/news/p-2965/
  * https://www.postgresql.org/docs/release/15.10/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 15.11:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/15.11/
  * https://www.postgresql.org/about/news/-3015/
- Disable LLVM JIT on loongarch64</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 15.12:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/15.12/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 15.13:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/15.13/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Upgrade to 15.14:
  * https://www.postgresql.org/about/news/postgresql-176-1610-1514-1419-1322-and-18-beta-3-released-3118/
  * https://www.postgresql.org/docs/release/15.14/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1758801600">- Sync spec file from version 18.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Upgrade to 15.15:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/15.15/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 15.16:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/15.16/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 15.17 to fix two regressions in 15.16:
  * https://www.postgresql.org/docs/release/15.17/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
</package>
<package pkgid="0fde38892c0fe53f1ed1f09e5fe6d0029190a9dabe54ceea1c9b0fd144bf7b3a997278efe4d86e23e698e7629f8c18a39ccf4770824ebc71b71002ea034dadcc" name="postgresql15-plperl" arch="aarch64">
  <version epoch="0" ver="15.17" rel="87.2"/>
  <changelog author="Dominique Leuenberger &lt;dimstar@opensuse.org&gt;" date="1709208000">- Use %patch -P N instead of deprecated %patchN.</changelog>
  <changelog author="Sarah Kriesch &lt;sarah.kriesch@opensuse.org&gt;" date="1709812800">- Remove constraints file because improved memory usage for s390x</changelog>
  <changelog author="Aaron Puchert &lt;aaronpuchert@alice-dsl.net&gt;" date="1710244800">- Require LLVM &lt;= 17 for now, because LLVM 18 doesn't seem to work.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1715169600">- Upgrade to 15.7 (bsc#1224051):
  * bsc#1224038, CVE-2024-4317: Restrict visibility of pg_stats_ext
    and pg_stats_ext_exprs entries to the table owner. See the
    release notes for the steps that have to be taken to fix
    existing PostgreSQL instances.
  * Fix incompatibility with LLVM 18.
  * https://www.postgresql.org/docs/release/15.7/
- Prepare for PostgreSQL 17.
- Make sure all compilation and doc generation happens in %build.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1723291200">- Upgrade to 15.8 (bsc#1229013):
  * bsc#1229013, CVE-2024-7348 PostgreSQL relation replacement
    during pg_dump executes arbitrary SQL
  * https://www.postgresql.org/about/news/p-2910/
  * https://www.postgresql.org/docs/release/15.8/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1730808000">- Sync spec file from postgresql17.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1731499200">- Upgrade to 15.9:
  * CVE-2024-10976, bsc#1233323: Ensure cached plans are marked as
    dependent on the calling role when RLS applies to a
    non-top-level table reference.
  * CVE-2024-10977, bsc#1233325: Make libpq discard error messages
    received during SSL or GSS protocol negotiation.
  * CVE-2024-10978, bsc#1233326: Fix unintended interactions
    between SET SESSION AUTHORIZATION and SET ROLE
  * CVE-2024-10979, bsc#1233327: Prevent trusted PL/Perl code from
    changing environment variables.
  * https://www.postgresql.org/about/news/p-2955/
  * https://www.postgresql.org/docs/release/15.9/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1732017600">- Upgrade to 15.10
  * Repair ABI break for extensions that work with struct
    ResultRelInfo.
  * Restore functionality of ALTER {ROLE|DATABASE} SET role.
  * Fix cases where a logical replication slot's restart_lsn could
    go backwards.
  * Avoid deleting still-needed WAL files during pg_rewind.
  * Fix race conditions associated with dropping shared statistics
    entries.
  * Count index scans in contrib/bloom indexes in the statistics
    views, such as the pg_stat_user_indexes.idx_scan counter.
  * Fix crash when checking to see if an index's opclass options
    have changed.
  * Avoid assertion failure caused by disconnected NFA sub-graphs
    in regular expression parsing.
  * https://www.postgresql.org/about/news/p-2965/
  * https://www.postgresql.org/docs/release/15.10/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 15.11:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/15.11/
  * https://www.postgresql.org/about/news/-3015/
- Disable LLVM JIT on loongarch64</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 15.12:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/15.12/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 15.13:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/15.13/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Upgrade to 15.14:
  * https://www.postgresql.org/about/news/postgresql-176-1610-1514-1419-1322-and-18-beta-3-released-3118/
  * https://www.postgresql.org/docs/release/15.14/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1758801600">- Sync spec file from version 18.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Upgrade to 15.15:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/15.15/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 15.16:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/15.16/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 15.17 to fix two regressions in 15.16:
  * https://www.postgresql.org/docs/release/15.17/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
</package>
<package pkgid="33d86c1548a266f592d3b4179ce98874324b1ad24e493c2f112c961d64dd3cfe367dbde16e1c62146ee4521074dcd4d387ea169dfb720d3a7d7c2797397dda51" name="postgresql15-plperl" arch="s390x">
  <version epoch="0" ver="15.17" rel="87.2"/>
  <changelog author="Dominique Leuenberger &lt;dimstar@opensuse.org&gt;" date="1709208000">- Use %patch -P N instead of deprecated %patchN.</changelog>
  <changelog author="Sarah Kriesch &lt;sarah.kriesch@opensuse.org&gt;" date="1709812800">- Remove constraints file because improved memory usage for s390x</changelog>
  <changelog author="Aaron Puchert &lt;aaronpuchert@alice-dsl.net&gt;" date="1710244800">- Require LLVM &lt;= 17 for now, because LLVM 18 doesn't seem to work.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1715169600">- Upgrade to 15.7 (bsc#1224051):
  * bsc#1224038, CVE-2024-4317: Restrict visibility of pg_stats_ext
    and pg_stats_ext_exprs entries to the table owner. See the
    release notes for the steps that have to be taken to fix
    existing PostgreSQL instances.
  * Fix incompatibility with LLVM 18.
  * https://www.postgresql.org/docs/release/15.7/
- Prepare for PostgreSQL 17.
- Make sure all compilation and doc generation happens in %build.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1723291200">- Upgrade to 15.8 (bsc#1229013):
  * bsc#1229013, CVE-2024-7348 PostgreSQL relation replacement
    during pg_dump executes arbitrary SQL
  * https://www.postgresql.org/about/news/p-2910/
  * https://www.postgresql.org/docs/release/15.8/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1730808000">- Sync spec file from postgresql17.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1731499200">- Upgrade to 15.9:
  * CVE-2024-10976, bsc#1233323: Ensure cached plans are marked as
    dependent on the calling role when RLS applies to a
    non-top-level table reference.
  * CVE-2024-10977, bsc#1233325: Make libpq discard error messages
    received during SSL or GSS protocol negotiation.
  * CVE-2024-10978, bsc#1233326: Fix unintended interactions
    between SET SESSION AUTHORIZATION and SET ROLE
  * CVE-2024-10979, bsc#1233327: Prevent trusted PL/Perl code from
    changing environment variables.
  * https://www.postgresql.org/about/news/p-2955/
  * https://www.postgresql.org/docs/release/15.9/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1732017600">- Upgrade to 15.10
  * Repair ABI break for extensions that work with struct
    ResultRelInfo.
  * Restore functionality of ALTER {ROLE|DATABASE} SET role.
  * Fix cases where a logical replication slot's restart_lsn could
    go backwards.
  * Avoid deleting still-needed WAL files during pg_rewind.
  * Fix race conditions associated with dropping shared statistics
    entries.
  * Count index scans in contrib/bloom indexes in the statistics
    views, such as the pg_stat_user_indexes.idx_scan counter.
  * Fix crash when checking to see if an index's opclass options
    have changed.
  * Avoid assertion failure caused by disconnected NFA sub-graphs
    in regular expression parsing.
  * https://www.postgresql.org/about/news/p-2965/
  * https://www.postgresql.org/docs/release/15.10/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 15.11:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/15.11/
  * https://www.postgresql.org/about/news/-3015/
- Disable LLVM JIT on loongarch64</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 15.12:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/15.12/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 15.13:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/15.13/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Upgrade to 15.14:
  * https://www.postgresql.org/about/news/postgresql-176-1610-1514-1419-1322-and-18-beta-3-released-3118/
  * https://www.postgresql.org/docs/release/15.14/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1758801600">- Sync spec file from version 18.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Upgrade to 15.15:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/15.15/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 15.16:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/15.16/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 15.17 to fix two regressions in 15.16:
  * https://www.postgresql.org/docs/release/15.17/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
</package>
<package pkgid="23c4704624c04809023124d6ea29904f2a8ddb903e72594d4b362a94991ee418a5afbaef96dea39b96f9ca7a4118aad8e4e97928472dd0f4e0c9a539957f91b3" name="postgresql15-plperl" arch="x86_64">
  <version epoch="0" ver="15.18" rel="97.2"/>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1715169600">- Upgrade to 15.7 (bsc#1224051):
  * bsc#1224038, CVE-2024-4317: Restrict visibility of pg_stats_ext
    and pg_stats_ext_exprs entries to the table owner. See the
    release notes for the steps that have to be taken to fix
    existing PostgreSQL instances.
  * Fix incompatibility with LLVM 18.
  * https://www.postgresql.org/docs/release/15.7/
- Prepare for PostgreSQL 17.
- Make sure all compilation and doc generation happens in %build.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1723291200">- Upgrade to 15.8 (bsc#1229013):
  * bsc#1229013, CVE-2024-7348 PostgreSQL relation replacement
    during pg_dump executes arbitrary SQL
  * https://www.postgresql.org/about/news/p-2910/
  * https://www.postgresql.org/docs/release/15.8/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1730808000">- Sync spec file from postgresql17.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1731499200">- Upgrade to 15.9:
  * CVE-2024-10976, bsc#1233323: Ensure cached plans are marked as
    dependent on the calling role when RLS applies to a
    non-top-level table reference.
  * CVE-2024-10977, bsc#1233325: Make libpq discard error messages
    received during SSL or GSS protocol negotiation.
  * CVE-2024-10978, bsc#1233326: Fix unintended interactions
    between SET SESSION AUTHORIZATION and SET ROLE
  * CVE-2024-10979, bsc#1233327: Prevent trusted PL/Perl code from
    changing environment variables.
  * https://www.postgresql.org/about/news/p-2955/
  * https://www.postgresql.org/docs/release/15.9/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1732017600">- Upgrade to 15.10
  * Repair ABI break for extensions that work with struct
    ResultRelInfo.
  * Restore functionality of ALTER {ROLE|DATABASE} SET role.
  * Fix cases where a logical replication slot's restart_lsn could
    go backwards.
  * Avoid deleting still-needed WAL files during pg_rewind.
  * Fix race conditions associated with dropping shared statistics
    entries.
  * Count index scans in contrib/bloom indexes in the statistics
    views, such as the pg_stat_user_indexes.idx_scan counter.
  * Fix crash when checking to see if an index's opclass options
    have changed.
  * Avoid assertion failure caused by disconnected NFA sub-graphs
    in regular expression parsing.
  * https://www.postgresql.org/about/news/p-2965/
  * https://www.postgresql.org/docs/release/15.10/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 15.11:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/15.11/
  * https://www.postgresql.org/about/news/-3015/
- Disable LLVM JIT on loongarch64</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 15.12:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/15.12/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 15.13:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/15.13/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Upgrade to 15.14:
  * https://www.postgresql.org/about/news/postgresql-176-1610-1514-1419-1322-and-18-beta-3-released-3118/
  * https://www.postgresql.org/docs/release/15.14/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1758801600">- Sync spec file from version 18.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Upgrade to 15.15:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/15.15/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 15.16:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/15.16/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 15.17 to fix two regressions in 15.16:
  * https://www.postgresql.org/docs/release/15.17/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1774872000">- Get rid of update-alternatives for openSUSE/SLE 16.0 and newer
  to support immutable systems and transactional updates.
  (jsc#PED-14823)</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1777550400">- bsc#1263804: After dropping update-alternatives we have to
  package /usr/bin/pg_config as an actual symlink, not %ghost.
- Fix spelling of build conditionals.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1778673600">- Update to version 15.18:
  * bsc#1265172, CVE-2026-6472: ensure the user has CREATE
    privilege on the schema specified
  * bsc#1265173, CVE-2026-6473: integer overflows in
    memory-allocation calculations
  * bsc#1265174, CVE-2026-6474: Guard against malicious time zone
    names
  * bsc#1265175, CVE-2026-6475: Prevent path traversal in
    pg_basebackup and pg_rewind
  * bsc#1265177, CVE-2026-6477: Mark PQfn() as unsafe, and avoid
    using it within libpq
  * bsc#1265178, CVE-2026-6478: Use timing-safe string comparisons
    in authentication code
  * bsc#1265179, CVE-2026-6479: Prevent unbounded recursion while
    processing startup packets
  * bsc#1265181, CVE-2026-6637: Prevent SQL injection and buffer
    overruns in contrib/spi
  * https://www.postgresql.org/docs/release/15.18/</changelog>
</package>
<package pkgid="747ea0b4ca299c8e1ebc024daa446055375e0d6421d21b9e3528de37b618d869b27d66693962f397d82a282ff8cdbb6453d2ba99655e80c420558fb9440ec9f9" name="postgresql15-plpython" arch="ppc64le">
  <version epoch="0" ver="15.17" rel="86.1"/>
  <changelog author="Dominique Leuenberger &lt;dimstar@opensuse.org&gt;" date="1709208000">- Use %patch -P N instead of deprecated %patchN.</changelog>
  <changelog author="Sarah Kriesch &lt;sarah.kriesch@opensuse.org&gt;" date="1709812800">- Remove constraints file because improved memory usage for s390x</changelog>
  <changelog author="Aaron Puchert &lt;aaronpuchert@alice-dsl.net&gt;" date="1710244800">- Require LLVM &lt;= 17 for now, because LLVM 18 doesn't seem to work.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1715169600">- Upgrade to 15.7 (bsc#1224051):
  * bsc#1224038, CVE-2024-4317: Restrict visibility of pg_stats_ext
    and pg_stats_ext_exprs entries to the table owner. See the
    release notes for the steps that have to be taken to fix
    existing PostgreSQL instances.
  * Fix incompatibility with LLVM 18.
  * https://www.postgresql.org/docs/release/15.7/
- Prepare for PostgreSQL 17.
- Make sure all compilation and doc generation happens in %build.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1723291200">- Upgrade to 15.8 (bsc#1229013):
  * bsc#1229013, CVE-2024-7348 PostgreSQL relation replacement
    during pg_dump executes arbitrary SQL
  * https://www.postgresql.org/about/news/p-2910/
  * https://www.postgresql.org/docs/release/15.8/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1730808000">- Sync spec file from postgresql17.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1731499200">- Upgrade to 15.9:
  * CVE-2024-10976, bsc#1233323: Ensure cached plans are marked as
    dependent on the calling role when RLS applies to a
    non-top-level table reference.
  * CVE-2024-10977, bsc#1233325: Make libpq discard error messages
    received during SSL or GSS protocol negotiation.
  * CVE-2024-10978, bsc#1233326: Fix unintended interactions
    between SET SESSION AUTHORIZATION and SET ROLE
  * CVE-2024-10979, bsc#1233327: Prevent trusted PL/Perl code from
    changing environment variables.
  * https://www.postgresql.org/about/news/p-2955/
  * https://www.postgresql.org/docs/release/15.9/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1732017600">- Upgrade to 15.10
  * Repair ABI break for extensions that work with struct
    ResultRelInfo.
  * Restore functionality of ALTER {ROLE|DATABASE} SET role.
  * Fix cases where a logical replication slot's restart_lsn could
    go backwards.
  * Avoid deleting still-needed WAL files during pg_rewind.
  * Fix race conditions associated with dropping shared statistics
    entries.
  * Count index scans in contrib/bloom indexes in the statistics
    views, such as the pg_stat_user_indexes.idx_scan counter.
  * Fix crash when checking to see if an index's opclass options
    have changed.
  * Avoid assertion failure caused by disconnected NFA sub-graphs
    in regular expression parsing.
  * https://www.postgresql.org/about/news/p-2965/
  * https://www.postgresql.org/docs/release/15.10/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 15.11:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/15.11/
  * https://www.postgresql.org/about/news/-3015/
- Disable LLVM JIT on loongarch64</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 15.12:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/15.12/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 15.13:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/15.13/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Upgrade to 15.14:
  * https://www.postgresql.org/about/news/postgresql-176-1610-1514-1419-1322-and-18-beta-3-released-3118/
  * https://www.postgresql.org/docs/release/15.14/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1758801600">- Sync spec file from version 18.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Upgrade to 15.15:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/15.15/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 15.16:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/15.16/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 15.17 to fix two regressions in 15.16:
  * https://www.postgresql.org/docs/release/15.17/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
</package>
<package pkgid="b927ba6068e3de6b31d7f2b31128c553663eec64210ada3f56e75f2b6523366e07bef7b5e0d63b9ca1b39d6162e3b186b9cdb1172479a6a94498931fe09c7fc3" name="postgresql15-plpython" arch="aarch64">
  <version epoch="0" ver="15.17" rel="87.2"/>
  <changelog author="Dominique Leuenberger &lt;dimstar@opensuse.org&gt;" date="1709208000">- Use %patch -P N instead of deprecated %patchN.</changelog>
  <changelog author="Sarah Kriesch &lt;sarah.kriesch@opensuse.org&gt;" date="1709812800">- Remove constraints file because improved memory usage for s390x</changelog>
  <changelog author="Aaron Puchert &lt;aaronpuchert@alice-dsl.net&gt;" date="1710244800">- Require LLVM &lt;= 17 for now, because LLVM 18 doesn't seem to work.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1715169600">- Upgrade to 15.7 (bsc#1224051):
  * bsc#1224038, CVE-2024-4317: Restrict visibility of pg_stats_ext
    and pg_stats_ext_exprs entries to the table owner. See the
    release notes for the steps that have to be taken to fix
    existing PostgreSQL instances.
  * Fix incompatibility with LLVM 18.
  * https://www.postgresql.org/docs/release/15.7/
- Prepare for PostgreSQL 17.
- Make sure all compilation and doc generation happens in %build.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1723291200">- Upgrade to 15.8 (bsc#1229013):
  * bsc#1229013, CVE-2024-7348 PostgreSQL relation replacement
    during pg_dump executes arbitrary SQL
  * https://www.postgresql.org/about/news/p-2910/
  * https://www.postgresql.org/docs/release/15.8/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1730808000">- Sync spec file from postgresql17.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1731499200">- Upgrade to 15.9:
  * CVE-2024-10976, bsc#1233323: Ensure cached plans are marked as
    dependent on the calling role when RLS applies to a
    non-top-level table reference.
  * CVE-2024-10977, bsc#1233325: Make libpq discard error messages
    received during SSL or GSS protocol negotiation.
  * CVE-2024-10978, bsc#1233326: Fix unintended interactions
    between SET SESSION AUTHORIZATION and SET ROLE
  * CVE-2024-10979, bsc#1233327: Prevent trusted PL/Perl code from
    changing environment variables.
  * https://www.postgresql.org/about/news/p-2955/
  * https://www.postgresql.org/docs/release/15.9/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1732017600">- Upgrade to 15.10
  * Repair ABI break for extensions that work with struct
    ResultRelInfo.
  * Restore functionality of ALTER {ROLE|DATABASE} SET role.
  * Fix cases where a logical replication slot's restart_lsn could
    go backwards.
  * Avoid deleting still-needed WAL files during pg_rewind.
  * Fix race conditions associated with dropping shared statistics
    entries.
  * Count index scans in contrib/bloom indexes in the statistics
    views, such as the pg_stat_user_indexes.idx_scan counter.
  * Fix crash when checking to see if an index's opclass options
    have changed.
  * Avoid assertion failure caused by disconnected NFA sub-graphs
    in regular expression parsing.
  * https://www.postgresql.org/about/news/p-2965/
  * https://www.postgresql.org/docs/release/15.10/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 15.11:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/15.11/
  * https://www.postgresql.org/about/news/-3015/
- Disable LLVM JIT on loongarch64</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 15.12:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/15.12/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 15.13:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/15.13/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Upgrade to 15.14:
  * https://www.postgresql.org/about/news/postgresql-176-1610-1514-1419-1322-and-18-beta-3-released-3118/
  * https://www.postgresql.org/docs/release/15.14/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1758801600">- Sync spec file from version 18.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Upgrade to 15.15:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/15.15/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 15.16:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/15.16/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 15.17 to fix two regressions in 15.16:
  * https://www.postgresql.org/docs/release/15.17/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
</package>
<package pkgid="cf1d4344ef61e52b233295a830cfb6c9efae9cfa4e2cdcd018a268e47d57429385284d0a68024f5233b746e93b6a4a758a24de176a7d164e92730f3b010d2598" name="postgresql15-plpython" arch="s390x">
  <version epoch="0" ver="15.17" rel="87.2"/>
  <changelog author="Dominique Leuenberger &lt;dimstar@opensuse.org&gt;" date="1709208000">- Use %patch -P N instead of deprecated %patchN.</changelog>
  <changelog author="Sarah Kriesch &lt;sarah.kriesch@opensuse.org&gt;" date="1709812800">- Remove constraints file because improved memory usage for s390x</changelog>
  <changelog author="Aaron Puchert &lt;aaronpuchert@alice-dsl.net&gt;" date="1710244800">- Require LLVM &lt;= 17 for now, because LLVM 18 doesn't seem to work.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1715169600">- Upgrade to 15.7 (bsc#1224051):
  * bsc#1224038, CVE-2024-4317: Restrict visibility of pg_stats_ext
    and pg_stats_ext_exprs entries to the table owner. See the
    release notes for the steps that have to be taken to fix
    existing PostgreSQL instances.
  * Fix incompatibility with LLVM 18.
  * https://www.postgresql.org/docs/release/15.7/
- Prepare for PostgreSQL 17.
- Make sure all compilation and doc generation happens in %build.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1723291200">- Upgrade to 15.8 (bsc#1229013):
  * bsc#1229013, CVE-2024-7348 PostgreSQL relation replacement
    during pg_dump executes arbitrary SQL
  * https://www.postgresql.org/about/news/p-2910/
  * https://www.postgresql.org/docs/release/15.8/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1730808000">- Sync spec file from postgresql17.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1731499200">- Upgrade to 15.9:
  * CVE-2024-10976, bsc#1233323: Ensure cached plans are marked as
    dependent on the calling role when RLS applies to a
    non-top-level table reference.
  * CVE-2024-10977, bsc#1233325: Make libpq discard error messages
    received during SSL or GSS protocol negotiation.
  * CVE-2024-10978, bsc#1233326: Fix unintended interactions
    between SET SESSION AUTHORIZATION and SET ROLE
  * CVE-2024-10979, bsc#1233327: Prevent trusted PL/Perl code from
    changing environment variables.
  * https://www.postgresql.org/about/news/p-2955/
  * https://www.postgresql.org/docs/release/15.9/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1732017600">- Upgrade to 15.10
  * Repair ABI break for extensions that work with struct
    ResultRelInfo.
  * Restore functionality of ALTER {ROLE|DATABASE} SET role.
  * Fix cases where a logical replication slot's restart_lsn could
    go backwards.
  * Avoid deleting still-needed WAL files during pg_rewind.
  * Fix race conditions associated with dropping shared statistics
    entries.
  * Count index scans in contrib/bloom indexes in the statistics
    views, such as the pg_stat_user_indexes.idx_scan counter.
  * Fix crash when checking to see if an index's opclass options
    have changed.
  * Avoid assertion failure caused by disconnected NFA sub-graphs
    in regular expression parsing.
  * https://www.postgresql.org/about/news/p-2965/
  * https://www.postgresql.org/docs/release/15.10/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 15.11:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/15.11/
  * https://www.postgresql.org/about/news/-3015/
- Disable LLVM JIT on loongarch64</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 15.12:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/15.12/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 15.13:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/15.13/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Upgrade to 15.14:
  * https://www.postgresql.org/about/news/postgresql-176-1610-1514-1419-1322-and-18-beta-3-released-3118/
  * https://www.postgresql.org/docs/release/15.14/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1758801600">- Sync spec file from version 18.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Upgrade to 15.15:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/15.15/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 15.16:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/15.16/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 15.17 to fix two regressions in 15.16:
  * https://www.postgresql.org/docs/release/15.17/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
</package>
<package pkgid="3a252f6b24f5f74813f2e4b0925e4212ab3bd783c942bf9942ef42ff1eab14a92fb6410aaba29108d3c7a57f1c12ce3e452e6d7781d3eaa745c25e786155ded2" name="postgresql15-plpython" arch="x86_64">
  <version epoch="0" ver="15.18" rel="97.2"/>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1715169600">- Upgrade to 15.7 (bsc#1224051):
  * bsc#1224038, CVE-2024-4317: Restrict visibility of pg_stats_ext
    and pg_stats_ext_exprs entries to the table owner. See the
    release notes for the steps that have to be taken to fix
    existing PostgreSQL instances.
  * Fix incompatibility with LLVM 18.
  * https://www.postgresql.org/docs/release/15.7/
- Prepare for PostgreSQL 17.
- Make sure all compilation and doc generation happens in %build.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1723291200">- Upgrade to 15.8 (bsc#1229013):
  * bsc#1229013, CVE-2024-7348 PostgreSQL relation replacement
    during pg_dump executes arbitrary SQL
  * https://www.postgresql.org/about/news/p-2910/
  * https://www.postgresql.org/docs/release/15.8/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1730808000">- Sync spec file from postgresql17.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1731499200">- Upgrade to 15.9:
  * CVE-2024-10976, bsc#1233323: Ensure cached plans are marked as
    dependent on the calling role when RLS applies to a
    non-top-level table reference.
  * CVE-2024-10977, bsc#1233325: Make libpq discard error messages
    received during SSL or GSS protocol negotiation.
  * CVE-2024-10978, bsc#1233326: Fix unintended interactions
    between SET SESSION AUTHORIZATION and SET ROLE
  * CVE-2024-10979, bsc#1233327: Prevent trusted PL/Perl code from
    changing environment variables.
  * https://www.postgresql.org/about/news/p-2955/
  * https://www.postgresql.org/docs/release/15.9/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1732017600">- Upgrade to 15.10
  * Repair ABI break for extensions that work with struct
    ResultRelInfo.
  * Restore functionality of ALTER {ROLE|DATABASE} SET role.
  * Fix cases where a logical replication slot's restart_lsn could
    go backwards.
  * Avoid deleting still-needed WAL files during pg_rewind.
  * Fix race conditions associated with dropping shared statistics
    entries.
  * Count index scans in contrib/bloom indexes in the statistics
    views, such as the pg_stat_user_indexes.idx_scan counter.
  * Fix crash when checking to see if an index's opclass options
    have changed.
  * Avoid assertion failure caused by disconnected NFA sub-graphs
    in regular expression parsing.
  * https://www.postgresql.org/about/news/p-2965/
  * https://www.postgresql.org/docs/release/15.10/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 15.11:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/15.11/
  * https://www.postgresql.org/about/news/-3015/
- Disable LLVM JIT on loongarch64</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 15.12:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/15.12/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 15.13:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/15.13/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Upgrade to 15.14:
  * https://www.postgresql.org/about/news/postgresql-176-1610-1514-1419-1322-and-18-beta-3-released-3118/
  * https://www.postgresql.org/docs/release/15.14/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1758801600">- Sync spec file from version 18.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Upgrade to 15.15:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/15.15/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 15.16:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/15.16/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 15.17 to fix two regressions in 15.16:
  * https://www.postgresql.org/docs/release/15.17/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1774872000">- Get rid of update-alternatives for openSUSE/SLE 16.0 and newer
  to support immutable systems and transactional updates.
  (jsc#PED-14823)</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1777550400">- bsc#1263804: After dropping update-alternatives we have to
  package /usr/bin/pg_config as an actual symlink, not %ghost.
- Fix spelling of build conditionals.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1778673600">- Update to version 15.18:
  * bsc#1265172, CVE-2026-6472: ensure the user has CREATE
    privilege on the schema specified
  * bsc#1265173, CVE-2026-6473: integer overflows in
    memory-allocation calculations
  * bsc#1265174, CVE-2026-6474: Guard against malicious time zone
    names
  * bsc#1265175, CVE-2026-6475: Prevent path traversal in
    pg_basebackup and pg_rewind
  * bsc#1265177, CVE-2026-6477: Mark PQfn() as unsafe, and avoid
    using it within libpq
  * bsc#1265178, CVE-2026-6478: Use timing-safe string comparisons
    in authentication code
  * bsc#1265179, CVE-2026-6479: Prevent unbounded recursion while
    processing startup packets
  * bsc#1265181, CVE-2026-6637: Prevent SQL injection and buffer
    overruns in contrib/spi
  * https://www.postgresql.org/docs/release/15.18/</changelog>
</package>
<package pkgid="845ea8a31799d6df010e304667c52f008e9640cf98c623b7c4ebe46ca107ddb0ae688617570f49b178ac1517c5fdbcf54ae92daf9b0c40ee110d88734ea935bd" name="postgresql15-pltcl" arch="ppc64le">
  <version epoch="0" ver="15.17" rel="86.1"/>
  <changelog author="Dominique Leuenberger &lt;dimstar@opensuse.org&gt;" date="1709208000">- Use %patch -P N instead of deprecated %patchN.</changelog>
  <changelog author="Sarah Kriesch &lt;sarah.kriesch@opensuse.org&gt;" date="1709812800">- Remove constraints file because improved memory usage for s390x</changelog>
  <changelog author="Aaron Puchert &lt;aaronpuchert@alice-dsl.net&gt;" date="1710244800">- Require LLVM &lt;= 17 for now, because LLVM 18 doesn't seem to work.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1715169600">- Upgrade to 15.7 (bsc#1224051):
  * bsc#1224038, CVE-2024-4317: Restrict visibility of pg_stats_ext
    and pg_stats_ext_exprs entries to the table owner. See the
    release notes for the steps that have to be taken to fix
    existing PostgreSQL instances.
  * Fix incompatibility with LLVM 18.
  * https://www.postgresql.org/docs/release/15.7/
- Prepare for PostgreSQL 17.
- Make sure all compilation and doc generation happens in %build.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1723291200">- Upgrade to 15.8 (bsc#1229013):
  * bsc#1229013, CVE-2024-7348 PostgreSQL relation replacement
    during pg_dump executes arbitrary SQL
  * https://www.postgresql.org/about/news/p-2910/
  * https://www.postgresql.org/docs/release/15.8/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1730808000">- Sync spec file from postgresql17.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1731499200">- Upgrade to 15.9:
  * CVE-2024-10976, bsc#1233323: Ensure cached plans are marked as
    dependent on the calling role when RLS applies to a
    non-top-level table reference.
  * CVE-2024-10977, bsc#1233325: Make libpq discard error messages
    received during SSL or GSS protocol negotiation.
  * CVE-2024-10978, bsc#1233326: Fix unintended interactions
    between SET SESSION AUTHORIZATION and SET ROLE
  * CVE-2024-10979, bsc#1233327: Prevent trusted PL/Perl code from
    changing environment variables.
  * https://www.postgresql.org/about/news/p-2955/
  * https://www.postgresql.org/docs/release/15.9/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1732017600">- Upgrade to 15.10
  * Repair ABI break for extensions that work with struct
    ResultRelInfo.
  * Restore functionality of ALTER {ROLE|DATABASE} SET role.
  * Fix cases where a logical replication slot's restart_lsn could
    go backwards.
  * Avoid deleting still-needed WAL files during pg_rewind.
  * Fix race conditions associated with dropping shared statistics
    entries.
  * Count index scans in contrib/bloom indexes in the statistics
    views, such as the pg_stat_user_indexes.idx_scan counter.
  * Fix crash when checking to see if an index's opclass options
    have changed.
  * Avoid assertion failure caused by disconnected NFA sub-graphs
    in regular expression parsing.
  * https://www.postgresql.org/about/news/p-2965/
  * https://www.postgresql.org/docs/release/15.10/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 15.11:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/15.11/
  * https://www.postgresql.org/about/news/-3015/
- Disable LLVM JIT on loongarch64</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 15.12:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/15.12/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 15.13:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/15.13/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Upgrade to 15.14:
  * https://www.postgresql.org/about/news/postgresql-176-1610-1514-1419-1322-and-18-beta-3-released-3118/
  * https://www.postgresql.org/docs/release/15.14/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1758801600">- Sync spec file from version 18.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Upgrade to 15.15:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/15.15/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 15.16:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/15.16/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 15.17 to fix two regressions in 15.16:
  * https://www.postgresql.org/docs/release/15.17/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
</package>
<package pkgid="c58dd675d6398e689e658010e6816c0f9500129927bafc428ea630660566cc61bc2073e3ea70b2a72c94681e842f2bce56dc052c5e184b71bc0b2da87b11f80d" name="postgresql15-pltcl" arch="aarch64">
  <version epoch="0" ver="15.17" rel="87.2"/>
  <changelog author="Dominique Leuenberger &lt;dimstar@opensuse.org&gt;" date="1709208000">- Use %patch -P N instead of deprecated %patchN.</changelog>
  <changelog author="Sarah Kriesch &lt;sarah.kriesch@opensuse.org&gt;" date="1709812800">- Remove constraints file because improved memory usage for s390x</changelog>
  <changelog author="Aaron Puchert &lt;aaronpuchert@alice-dsl.net&gt;" date="1710244800">- Require LLVM &lt;= 17 for now, because LLVM 18 doesn't seem to work.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1715169600">- Upgrade to 15.7 (bsc#1224051):
  * bsc#1224038, CVE-2024-4317: Restrict visibility of pg_stats_ext
    and pg_stats_ext_exprs entries to the table owner. See the
    release notes for the steps that have to be taken to fix
    existing PostgreSQL instances.
  * Fix incompatibility with LLVM 18.
  * https://www.postgresql.org/docs/release/15.7/
- Prepare for PostgreSQL 17.
- Make sure all compilation and doc generation happens in %build.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1723291200">- Upgrade to 15.8 (bsc#1229013):
  * bsc#1229013, CVE-2024-7348 PostgreSQL relation replacement
    during pg_dump executes arbitrary SQL
  * https://www.postgresql.org/about/news/p-2910/
  * https://www.postgresql.org/docs/release/15.8/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1730808000">- Sync spec file from postgresql17.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1731499200">- Upgrade to 15.9:
  * CVE-2024-10976, bsc#1233323: Ensure cached plans are marked as
    dependent on the calling role when RLS applies to a
    non-top-level table reference.
  * CVE-2024-10977, bsc#1233325: Make libpq discard error messages
    received during SSL or GSS protocol negotiation.
  * CVE-2024-10978, bsc#1233326: Fix unintended interactions
    between SET SESSION AUTHORIZATION and SET ROLE
  * CVE-2024-10979, bsc#1233327: Prevent trusted PL/Perl code from
    changing environment variables.
  * https://www.postgresql.org/about/news/p-2955/
  * https://www.postgresql.org/docs/release/15.9/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1732017600">- Upgrade to 15.10
  * Repair ABI break for extensions that work with struct
    ResultRelInfo.
  * Restore functionality of ALTER {ROLE|DATABASE} SET role.
  * Fix cases where a logical replication slot's restart_lsn could
    go backwards.
  * Avoid deleting still-needed WAL files during pg_rewind.
  * Fix race conditions associated with dropping shared statistics
    entries.
  * Count index scans in contrib/bloom indexes in the statistics
    views, such as the pg_stat_user_indexes.idx_scan counter.
  * Fix crash when checking to see if an index's opclass options
    have changed.
  * Avoid assertion failure caused by disconnected NFA sub-graphs
    in regular expression parsing.
  * https://www.postgresql.org/about/news/p-2965/
  * https://www.postgresql.org/docs/release/15.10/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 15.11:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/15.11/
  * https://www.postgresql.org/about/news/-3015/
- Disable LLVM JIT on loongarch64</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 15.12:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/15.12/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 15.13:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/15.13/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Upgrade to 15.14:
  * https://www.postgresql.org/about/news/postgresql-176-1610-1514-1419-1322-and-18-beta-3-released-3118/
  * https://www.postgresql.org/docs/release/15.14/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1758801600">- Sync spec file from version 18.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Upgrade to 15.15:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/15.15/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 15.16:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/15.16/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 15.17 to fix two regressions in 15.16:
  * https://www.postgresql.org/docs/release/15.17/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
</package>
<package pkgid="094a0f4526ec605f57a3715b99a381cff9e377ec951a083074ae3689bf224721c9cd4d1256394ba1611ec783e05b5abc181ec5744575a4a2a5f4c8d8b0d8d7ff" name="postgresql15-pltcl" arch="s390x">
  <version epoch="0" ver="15.17" rel="87.2"/>
  <changelog author="Dominique Leuenberger &lt;dimstar@opensuse.org&gt;" date="1709208000">- Use %patch -P N instead of deprecated %patchN.</changelog>
  <changelog author="Sarah Kriesch &lt;sarah.kriesch@opensuse.org&gt;" date="1709812800">- Remove constraints file because improved memory usage for s390x</changelog>
  <changelog author="Aaron Puchert &lt;aaronpuchert@alice-dsl.net&gt;" date="1710244800">- Require LLVM &lt;= 17 for now, because LLVM 18 doesn't seem to work.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1715169600">- Upgrade to 15.7 (bsc#1224051):
  * bsc#1224038, CVE-2024-4317: Restrict visibility of pg_stats_ext
    and pg_stats_ext_exprs entries to the table owner. See the
    release notes for the steps that have to be taken to fix
    existing PostgreSQL instances.
  * Fix incompatibility with LLVM 18.
  * https://www.postgresql.org/docs/release/15.7/
- Prepare for PostgreSQL 17.
- Make sure all compilation and doc generation happens in %build.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1723291200">- Upgrade to 15.8 (bsc#1229013):
  * bsc#1229013, CVE-2024-7348 PostgreSQL relation replacement
    during pg_dump executes arbitrary SQL
  * https://www.postgresql.org/about/news/p-2910/
  * https://www.postgresql.org/docs/release/15.8/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1730808000">- Sync spec file from postgresql17.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1731499200">- Upgrade to 15.9:
  * CVE-2024-10976, bsc#1233323: Ensure cached plans are marked as
    dependent on the calling role when RLS applies to a
    non-top-level table reference.
  * CVE-2024-10977, bsc#1233325: Make libpq discard error messages
    received during SSL or GSS protocol negotiation.
  * CVE-2024-10978, bsc#1233326: Fix unintended interactions
    between SET SESSION AUTHORIZATION and SET ROLE
  * CVE-2024-10979, bsc#1233327: Prevent trusted PL/Perl code from
    changing environment variables.
  * https://www.postgresql.org/about/news/p-2955/
  * https://www.postgresql.org/docs/release/15.9/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1732017600">- Upgrade to 15.10
  * Repair ABI break for extensions that work with struct
    ResultRelInfo.
  * Restore functionality of ALTER {ROLE|DATABASE} SET role.
  * Fix cases where a logical replication slot's restart_lsn could
    go backwards.
  * Avoid deleting still-needed WAL files during pg_rewind.
  * Fix race conditions associated with dropping shared statistics
    entries.
  * Count index scans in contrib/bloom indexes in the statistics
    views, such as the pg_stat_user_indexes.idx_scan counter.
  * Fix crash when checking to see if an index's opclass options
    have changed.
  * Avoid assertion failure caused by disconnected NFA sub-graphs
    in regular expression parsing.
  * https://www.postgresql.org/about/news/p-2965/
  * https://www.postgresql.org/docs/release/15.10/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 15.11:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/15.11/
  * https://www.postgresql.org/about/news/-3015/
- Disable LLVM JIT on loongarch64</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 15.12:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/15.12/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 15.13:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/15.13/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Upgrade to 15.14:
  * https://www.postgresql.org/about/news/postgresql-176-1610-1514-1419-1322-and-18-beta-3-released-3118/
  * https://www.postgresql.org/docs/release/15.14/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1758801600">- Sync spec file from version 18.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Upgrade to 15.15:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/15.15/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 15.16:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/15.16/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 15.17 to fix two regressions in 15.16:
  * https://www.postgresql.org/docs/release/15.17/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
</package>
<package pkgid="a0a2dc1bf1a68ec20f776b01545e4fbe51735c87a6ad3eaf3db7a3591681f6be3c9fdb36e773452f915220fe5de4306beb2b1ff293b804a5e236f363876b1224" name="postgresql15-pltcl" arch="x86_64">
  <version epoch="0" ver="15.18" rel="97.2"/>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1715169600">- Upgrade to 15.7 (bsc#1224051):
  * bsc#1224038, CVE-2024-4317: Restrict visibility of pg_stats_ext
    and pg_stats_ext_exprs entries to the table owner. See the
    release notes for the steps that have to be taken to fix
    existing PostgreSQL instances.
  * Fix incompatibility with LLVM 18.
  * https://www.postgresql.org/docs/release/15.7/
- Prepare for PostgreSQL 17.
- Make sure all compilation and doc generation happens in %build.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1723291200">- Upgrade to 15.8 (bsc#1229013):
  * bsc#1229013, CVE-2024-7348 PostgreSQL relation replacement
    during pg_dump executes arbitrary SQL
  * https://www.postgresql.org/about/news/p-2910/
  * https://www.postgresql.org/docs/release/15.8/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1730808000">- Sync spec file from postgresql17.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1731499200">- Upgrade to 15.9:
  * CVE-2024-10976, bsc#1233323: Ensure cached plans are marked as
    dependent on the calling role when RLS applies to a
    non-top-level table reference.
  * CVE-2024-10977, bsc#1233325: Make libpq discard error messages
    received during SSL or GSS protocol negotiation.
  * CVE-2024-10978, bsc#1233326: Fix unintended interactions
    between SET SESSION AUTHORIZATION and SET ROLE
  * CVE-2024-10979, bsc#1233327: Prevent trusted PL/Perl code from
    changing environment variables.
  * https://www.postgresql.org/about/news/p-2955/
  * https://www.postgresql.org/docs/release/15.9/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1732017600">- Upgrade to 15.10
  * Repair ABI break for extensions that work with struct
    ResultRelInfo.
  * Restore functionality of ALTER {ROLE|DATABASE} SET role.
  * Fix cases where a logical replication slot's restart_lsn could
    go backwards.
  * Avoid deleting still-needed WAL files during pg_rewind.
  * Fix race conditions associated with dropping shared statistics
    entries.
  * Count index scans in contrib/bloom indexes in the statistics
    views, such as the pg_stat_user_indexes.idx_scan counter.
  * Fix crash when checking to see if an index's opclass options
    have changed.
  * Avoid assertion failure caused by disconnected NFA sub-graphs
    in regular expression parsing.
  * https://www.postgresql.org/about/news/p-2965/
  * https://www.postgresql.org/docs/release/15.10/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 15.11:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/15.11/
  * https://www.postgresql.org/about/news/-3015/
- Disable LLVM JIT on loongarch64</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 15.12:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/15.12/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 15.13:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/15.13/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Upgrade to 15.14:
  * https://www.postgresql.org/about/news/postgresql-176-1610-1514-1419-1322-and-18-beta-3-released-3118/
  * https://www.postgresql.org/docs/release/15.14/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1758801600">- Sync spec file from version 18.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Upgrade to 15.15:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/15.15/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 15.16:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/15.16/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 15.17 to fix two regressions in 15.16:
  * https://www.postgresql.org/docs/release/15.17/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1774872000">- Get rid of update-alternatives for openSUSE/SLE 16.0 and newer
  to support immutable systems and transactional updates.
  (jsc#PED-14823)</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1777550400">- bsc#1263804: After dropping update-alternatives we have to
  package /usr/bin/pg_config as an actual symlink, not %ghost.
- Fix spelling of build conditionals.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1778673600">- Update to version 15.18:
  * bsc#1265172, CVE-2026-6472: ensure the user has CREATE
    privilege on the schema specified
  * bsc#1265173, CVE-2026-6473: integer overflows in
    memory-allocation calculations
  * bsc#1265174, CVE-2026-6474: Guard against malicious time zone
    names
  * bsc#1265175, CVE-2026-6475: Prevent path traversal in
    pg_basebackup and pg_rewind
  * bsc#1265177, CVE-2026-6477: Mark PQfn() as unsafe, and avoid
    using it within libpq
  * bsc#1265178, CVE-2026-6478: Use timing-safe string comparisons
    in authentication code
  * bsc#1265179, CVE-2026-6479: Prevent unbounded recursion while
    processing startup packets
  * bsc#1265181, CVE-2026-6637: Prevent SQL injection and buffer
    overruns in contrib/spi
  * https://www.postgresql.org/docs/release/15.18/</changelog>
</package>
<package pkgid="81a6f82a8858f36c85f482054e390bd4676b769e282b890d3a78bf68f31b2292082281d530832136d2e91d649997214ad214f1b4d7e4d2ff2ed3569564b402fa" name="postgresql15-server" arch="ppc64le">
  <version epoch="0" ver="15.17" rel="86.1"/>
  <changelog author="Dominique Leuenberger &lt;dimstar@opensuse.org&gt;" date="1709208000">- Use %patch -P N instead of deprecated %patchN.</changelog>
  <changelog author="Sarah Kriesch &lt;sarah.kriesch@opensuse.org&gt;" date="1709812800">- Remove constraints file because improved memory usage for s390x</changelog>
  <changelog author="Aaron Puchert &lt;aaronpuchert@alice-dsl.net&gt;" date="1710244800">- Require LLVM &lt;= 17 for now, because LLVM 18 doesn't seem to work.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1715169600">- Upgrade to 15.7 (bsc#1224051):
  * bsc#1224038, CVE-2024-4317: Restrict visibility of pg_stats_ext
    and pg_stats_ext_exprs entries to the table owner. See the
    release notes for the steps that have to be taken to fix
    existing PostgreSQL instances.
  * Fix incompatibility with LLVM 18.
  * https://www.postgresql.org/docs/release/15.7/
- Prepare for PostgreSQL 17.
- Make sure all compilation and doc generation happens in %build.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1723291200">- Upgrade to 15.8 (bsc#1229013):
  * bsc#1229013, CVE-2024-7348 PostgreSQL relation replacement
    during pg_dump executes arbitrary SQL
  * https://www.postgresql.org/about/news/p-2910/
  * https://www.postgresql.org/docs/release/15.8/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1730808000">- Sync spec file from postgresql17.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1731499200">- Upgrade to 15.9:
  * CVE-2024-10976, bsc#1233323: Ensure cached plans are marked as
    dependent on the calling role when RLS applies to a
    non-top-level table reference.
  * CVE-2024-10977, bsc#1233325: Make libpq discard error messages
    received during SSL or GSS protocol negotiation.
  * CVE-2024-10978, bsc#1233326: Fix unintended interactions
    between SET SESSION AUTHORIZATION and SET ROLE
  * CVE-2024-10979, bsc#1233327: Prevent trusted PL/Perl code from
    changing environment variables.
  * https://www.postgresql.org/about/news/p-2955/
  * https://www.postgresql.org/docs/release/15.9/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1732017600">- Upgrade to 15.10
  * Repair ABI break for extensions that work with struct
    ResultRelInfo.
  * Restore functionality of ALTER {ROLE|DATABASE} SET role.
  * Fix cases where a logical replication slot's restart_lsn could
    go backwards.
  * Avoid deleting still-needed WAL files during pg_rewind.
  * Fix race conditions associated with dropping shared statistics
    entries.
  * Count index scans in contrib/bloom indexes in the statistics
    views, such as the pg_stat_user_indexes.idx_scan counter.
  * Fix crash when checking to see if an index's opclass options
    have changed.
  * Avoid assertion failure caused by disconnected NFA sub-graphs
    in regular expression parsing.
  * https://www.postgresql.org/about/news/p-2965/
  * https://www.postgresql.org/docs/release/15.10/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 15.11:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/15.11/
  * https://www.postgresql.org/about/news/-3015/
- Disable LLVM JIT on loongarch64</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 15.12:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/15.12/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 15.13:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/15.13/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Upgrade to 15.14:
  * https://www.postgresql.org/about/news/postgresql-176-1610-1514-1419-1322-and-18-beta-3-released-3118/
  * https://www.postgresql.org/docs/release/15.14/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1758801600">- Sync spec file from version 18.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Upgrade to 15.15:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/15.15/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 15.16:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/15.16/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 15.17 to fix two regressions in 15.16:
  * https://www.postgresql.org/docs/release/15.17/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
</package>
<package pkgid="64da0ff06b204be8f60a86b1784bb83e5cbad9253ef6dc16963f1763ce94fcbd99439a1b6fd31c854f314dad94f68101ea279739530484354b05134c6c6a5428" name="postgresql15-server" arch="aarch64">
  <version epoch="0" ver="15.17" rel="87.2"/>
  <changelog author="Dominique Leuenberger &lt;dimstar@opensuse.org&gt;" date="1709208000">- Use %patch -P N instead of deprecated %patchN.</changelog>
  <changelog author="Sarah Kriesch &lt;sarah.kriesch@opensuse.org&gt;" date="1709812800">- Remove constraints file because improved memory usage for s390x</changelog>
  <changelog author="Aaron Puchert &lt;aaronpuchert@alice-dsl.net&gt;" date="1710244800">- Require LLVM &lt;= 17 for now, because LLVM 18 doesn't seem to work.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1715169600">- Upgrade to 15.7 (bsc#1224051):
  * bsc#1224038, CVE-2024-4317: Restrict visibility of pg_stats_ext
    and pg_stats_ext_exprs entries to the table owner. See the
    release notes for the steps that have to be taken to fix
    existing PostgreSQL instances.
  * Fix incompatibility with LLVM 18.
  * https://www.postgresql.org/docs/release/15.7/
- Prepare for PostgreSQL 17.
- Make sure all compilation and doc generation happens in %build.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1723291200">- Upgrade to 15.8 (bsc#1229013):
  * bsc#1229013, CVE-2024-7348 PostgreSQL relation replacement
    during pg_dump executes arbitrary SQL
  * https://www.postgresql.org/about/news/p-2910/
  * https://www.postgresql.org/docs/release/15.8/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1730808000">- Sync spec file from postgresql17.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1731499200">- Upgrade to 15.9:
  * CVE-2024-10976, bsc#1233323: Ensure cached plans are marked as
    dependent on the calling role when RLS applies to a
    non-top-level table reference.
  * CVE-2024-10977, bsc#1233325: Make libpq discard error messages
    received during SSL or GSS protocol negotiation.
  * CVE-2024-10978, bsc#1233326: Fix unintended interactions
    between SET SESSION AUTHORIZATION and SET ROLE
  * CVE-2024-10979, bsc#1233327: Prevent trusted PL/Perl code from
    changing environment variables.
  * https://www.postgresql.org/about/news/p-2955/
  * https://www.postgresql.org/docs/release/15.9/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1732017600">- Upgrade to 15.10
  * Repair ABI break for extensions that work with struct
    ResultRelInfo.
  * Restore functionality of ALTER {ROLE|DATABASE} SET role.
  * Fix cases where a logical replication slot's restart_lsn could
    go backwards.
  * Avoid deleting still-needed WAL files during pg_rewind.
  * Fix race conditions associated with dropping shared statistics
    entries.
  * Count index scans in contrib/bloom indexes in the statistics
    views, such as the pg_stat_user_indexes.idx_scan counter.
  * Fix crash when checking to see if an index's opclass options
    have changed.
  * Avoid assertion failure caused by disconnected NFA sub-graphs
    in regular expression parsing.
  * https://www.postgresql.org/about/news/p-2965/
  * https://www.postgresql.org/docs/release/15.10/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 15.11:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/15.11/
  * https://www.postgresql.org/about/news/-3015/
- Disable LLVM JIT on loongarch64</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 15.12:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/15.12/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 15.13:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/15.13/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Upgrade to 15.14:
  * https://www.postgresql.org/about/news/postgresql-176-1610-1514-1419-1322-and-18-beta-3-released-3118/
  * https://www.postgresql.org/docs/release/15.14/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1758801600">- Sync spec file from version 18.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Upgrade to 15.15:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/15.15/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 15.16:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/15.16/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 15.17 to fix two regressions in 15.16:
  * https://www.postgresql.org/docs/release/15.17/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
</package>
<package pkgid="ff6026dcaa7de8811345b65b8116548c3fbea91d7e8ab26a0341f81436ed76902445f9b9494c0a56d5c8b98d565477a0b45a1d8a1b53c1e24a4694c08d373537" name="postgresql15-server" arch="s390x">
  <version epoch="0" ver="15.17" rel="87.2"/>
  <changelog author="Dominique Leuenberger &lt;dimstar@opensuse.org&gt;" date="1709208000">- Use %patch -P N instead of deprecated %patchN.</changelog>
  <changelog author="Sarah Kriesch &lt;sarah.kriesch@opensuse.org&gt;" date="1709812800">- Remove constraints file because improved memory usage for s390x</changelog>
  <changelog author="Aaron Puchert &lt;aaronpuchert@alice-dsl.net&gt;" date="1710244800">- Require LLVM &lt;= 17 for now, because LLVM 18 doesn't seem to work.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1715169600">- Upgrade to 15.7 (bsc#1224051):
  * bsc#1224038, CVE-2024-4317: Restrict visibility of pg_stats_ext
    and pg_stats_ext_exprs entries to the table owner. See the
    release notes for the steps that have to be taken to fix
    existing PostgreSQL instances.
  * Fix incompatibility with LLVM 18.
  * https://www.postgresql.org/docs/release/15.7/
- Prepare for PostgreSQL 17.
- Make sure all compilation and doc generation happens in %build.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1723291200">- Upgrade to 15.8 (bsc#1229013):
  * bsc#1229013, CVE-2024-7348 PostgreSQL relation replacement
    during pg_dump executes arbitrary SQL
  * https://www.postgresql.org/about/news/p-2910/
  * https://www.postgresql.org/docs/release/15.8/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1730808000">- Sync spec file from postgresql17.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1731499200">- Upgrade to 15.9:
  * CVE-2024-10976, bsc#1233323: Ensure cached plans are marked as
    dependent on the calling role when RLS applies to a
    non-top-level table reference.
  * CVE-2024-10977, bsc#1233325: Make libpq discard error messages
    received during SSL or GSS protocol negotiation.
  * CVE-2024-10978, bsc#1233326: Fix unintended interactions
    between SET SESSION AUTHORIZATION and SET ROLE
  * CVE-2024-10979, bsc#1233327: Prevent trusted PL/Perl code from
    changing environment variables.
  * https://www.postgresql.org/about/news/p-2955/
  * https://www.postgresql.org/docs/release/15.9/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1732017600">- Upgrade to 15.10
  * Repair ABI break for extensions that work with struct
    ResultRelInfo.
  * Restore functionality of ALTER {ROLE|DATABASE} SET role.
  * Fix cases where a logical replication slot's restart_lsn could
    go backwards.
  * Avoid deleting still-needed WAL files during pg_rewind.
  * Fix race conditions associated with dropping shared statistics
    entries.
  * Count index scans in contrib/bloom indexes in the statistics
    views, such as the pg_stat_user_indexes.idx_scan counter.
  * Fix crash when checking to see if an index's opclass options
    have changed.
  * Avoid assertion failure caused by disconnected NFA sub-graphs
    in regular expression parsing.
  * https://www.postgresql.org/about/news/p-2965/
  * https://www.postgresql.org/docs/release/15.10/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 15.11:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/15.11/
  * https://www.postgresql.org/about/news/-3015/
- Disable LLVM JIT on loongarch64</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 15.12:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/15.12/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 15.13:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/15.13/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Upgrade to 15.14:
  * https://www.postgresql.org/about/news/postgresql-176-1610-1514-1419-1322-and-18-beta-3-released-3118/
  * https://www.postgresql.org/docs/release/15.14/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1758801600">- Sync spec file from version 18.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Upgrade to 15.15:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/15.15/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 15.16:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/15.16/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 15.17 to fix two regressions in 15.16:
  * https://www.postgresql.org/docs/release/15.17/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
</package>
<package pkgid="8d62276ad982fc2df537c0eb021d8cf645a1c95b8e887a32f32630f65d8c72a9c3e5f37465636d60c54a04e6beb79a319362a5f6904ca0c6be19af07a9db6123" name="postgresql15-server" arch="x86_64">
  <version epoch="0" ver="15.18" rel="97.2"/>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1715169600">- Upgrade to 15.7 (bsc#1224051):
  * bsc#1224038, CVE-2024-4317: Restrict visibility of pg_stats_ext
    and pg_stats_ext_exprs entries to the table owner. See the
    release notes for the steps that have to be taken to fix
    existing PostgreSQL instances.
  * Fix incompatibility with LLVM 18.
  * https://www.postgresql.org/docs/release/15.7/
- Prepare for PostgreSQL 17.
- Make sure all compilation and doc generation happens in %build.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1723291200">- Upgrade to 15.8 (bsc#1229013):
  * bsc#1229013, CVE-2024-7348 PostgreSQL relation replacement
    during pg_dump executes arbitrary SQL
  * https://www.postgresql.org/about/news/p-2910/
  * https://www.postgresql.org/docs/release/15.8/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1730808000">- Sync spec file from postgresql17.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1731499200">- Upgrade to 15.9:
  * CVE-2024-10976, bsc#1233323: Ensure cached plans are marked as
    dependent on the calling role when RLS applies to a
    non-top-level table reference.
  * CVE-2024-10977, bsc#1233325: Make libpq discard error messages
    received during SSL or GSS protocol negotiation.
  * CVE-2024-10978, bsc#1233326: Fix unintended interactions
    between SET SESSION AUTHORIZATION and SET ROLE
  * CVE-2024-10979, bsc#1233327: Prevent trusted PL/Perl code from
    changing environment variables.
  * https://www.postgresql.org/about/news/p-2955/
  * https://www.postgresql.org/docs/release/15.9/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1732017600">- Upgrade to 15.10
  * Repair ABI break for extensions that work with struct
    ResultRelInfo.
  * Restore functionality of ALTER {ROLE|DATABASE} SET role.
  * Fix cases where a logical replication slot's restart_lsn could
    go backwards.
  * Avoid deleting still-needed WAL files during pg_rewind.
  * Fix race conditions associated with dropping shared statistics
    entries.
  * Count index scans in contrib/bloom indexes in the statistics
    views, such as the pg_stat_user_indexes.idx_scan counter.
  * Fix crash when checking to see if an index's opclass options
    have changed.
  * Avoid assertion failure caused by disconnected NFA sub-graphs
    in regular expression parsing.
  * https://www.postgresql.org/about/news/p-2965/
  * https://www.postgresql.org/docs/release/15.10/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 15.11:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/15.11/
  * https://www.postgresql.org/about/news/-3015/
- Disable LLVM JIT on loongarch64</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 15.12:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/15.12/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 15.13:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/15.13/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Upgrade to 15.14:
  * https://www.postgresql.org/about/news/postgresql-176-1610-1514-1419-1322-and-18-beta-3-released-3118/
  * https://www.postgresql.org/docs/release/15.14/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1758801600">- Sync spec file from version 18.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Upgrade to 15.15:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/15.15/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 15.16:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/15.16/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 15.17 to fix two regressions in 15.16:
  * https://www.postgresql.org/docs/release/15.17/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1774872000">- Get rid of update-alternatives for openSUSE/SLE 16.0 and newer
  to support immutable systems and transactional updates.
  (jsc#PED-14823)</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1777550400">- bsc#1263804: After dropping update-alternatives we have to
  package /usr/bin/pg_config as an actual symlink, not %ghost.
- Fix spelling of build conditionals.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1778673600">- Update to version 15.18:
  * bsc#1265172, CVE-2026-6472: ensure the user has CREATE
    privilege on the schema specified
  * bsc#1265173, CVE-2026-6473: integer overflows in
    memory-allocation calculations
  * bsc#1265174, CVE-2026-6474: Guard against malicious time zone
    names
  * bsc#1265175, CVE-2026-6475: Prevent path traversal in
    pg_basebackup and pg_rewind
  * bsc#1265177, CVE-2026-6477: Mark PQfn() as unsafe, and avoid
    using it within libpq
  * bsc#1265178, CVE-2026-6478: Use timing-safe string comparisons
    in authentication code
  * bsc#1265179, CVE-2026-6479: Prevent unbounded recursion while
    processing startup packets
  * bsc#1265181, CVE-2026-6637: Prevent SQL injection and buffer
    overruns in contrib/spi
  * https://www.postgresql.org/docs/release/15.18/</changelog>
</package>
<package pkgid="95ef6f7484ef2a983f83452545f1f3dcbf222bd76a2d5eb48a1f5226ee2bfb4b59810ef3ba5eec48759557e389a04e59ada7fa18199d9f3905627f3cf21962cf" name="postgresql15-server-devel" arch="ppc64le">
  <version epoch="0" ver="15.17" rel="86.1"/>
  <changelog author="Dominique Leuenberger &lt;dimstar@opensuse.org&gt;" date="1709208000">- Use %patch -P N instead of deprecated %patchN.</changelog>
  <changelog author="Sarah Kriesch &lt;sarah.kriesch@opensuse.org&gt;" date="1709812800">- Remove constraints file because improved memory usage for s390x</changelog>
  <changelog author="Aaron Puchert &lt;aaronpuchert@alice-dsl.net&gt;" date="1710244800">- Require LLVM &lt;= 17 for now, because LLVM 18 doesn't seem to work.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1715169600">- Upgrade to 15.7 (bsc#1224051):
  * bsc#1224038, CVE-2024-4317: Restrict visibility of pg_stats_ext
    and pg_stats_ext_exprs entries to the table owner. See the
    release notes for the steps that have to be taken to fix
    existing PostgreSQL instances.
  * Fix incompatibility with LLVM 18.
  * https://www.postgresql.org/docs/release/15.7/
- Prepare for PostgreSQL 17.
- Make sure all compilation and doc generation happens in %build.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1723291200">- Upgrade to 15.8 (bsc#1229013):
  * bsc#1229013, CVE-2024-7348 PostgreSQL relation replacement
    during pg_dump executes arbitrary SQL
  * https://www.postgresql.org/about/news/p-2910/
  * https://www.postgresql.org/docs/release/15.8/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1730808000">- Sync spec file from postgresql17.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1731499200">- Upgrade to 15.9:
  * CVE-2024-10976, bsc#1233323: Ensure cached plans are marked as
    dependent on the calling role when RLS applies to a
    non-top-level table reference.
  * CVE-2024-10977, bsc#1233325: Make libpq discard error messages
    received during SSL or GSS protocol negotiation.
  * CVE-2024-10978, bsc#1233326: Fix unintended interactions
    between SET SESSION AUTHORIZATION and SET ROLE
  * CVE-2024-10979, bsc#1233327: Prevent trusted PL/Perl code from
    changing environment variables.
  * https://www.postgresql.org/about/news/p-2955/
  * https://www.postgresql.org/docs/release/15.9/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1732017600">- Upgrade to 15.10
  * Repair ABI break for extensions that work with struct
    ResultRelInfo.
  * Restore functionality of ALTER {ROLE|DATABASE} SET role.
  * Fix cases where a logical replication slot's restart_lsn could
    go backwards.
  * Avoid deleting still-needed WAL files during pg_rewind.
  * Fix race conditions associated with dropping shared statistics
    entries.
  * Count index scans in contrib/bloom indexes in the statistics
    views, such as the pg_stat_user_indexes.idx_scan counter.
  * Fix crash when checking to see if an index's opclass options
    have changed.
  * Avoid assertion failure caused by disconnected NFA sub-graphs
    in regular expression parsing.
  * https://www.postgresql.org/about/news/p-2965/
  * https://www.postgresql.org/docs/release/15.10/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 15.11:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/15.11/
  * https://www.postgresql.org/about/news/-3015/
- Disable LLVM JIT on loongarch64</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 15.12:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/15.12/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 15.13:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/15.13/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Upgrade to 15.14:
  * https://www.postgresql.org/about/news/postgresql-176-1610-1514-1419-1322-and-18-beta-3-released-3118/
  * https://www.postgresql.org/docs/release/15.14/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1758801600">- Sync spec file from version 18.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Upgrade to 15.15:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/15.15/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 15.16:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/15.16/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 15.17 to fix two regressions in 15.16:
  * https://www.postgresql.org/docs/release/15.17/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
</package>
<package pkgid="6aff1f1edb1eec2a119f9700b7796f1a0ef4517dadaae7f0a55d8342166c5ca6b269f9378392efc86c4a58278c670ee90f5ee0b2dbccd6279a12cbad901e49c5" name="postgresql15-server-devel" arch="aarch64">
  <version epoch="0" ver="15.17" rel="87.2"/>
  <changelog author="Dominique Leuenberger &lt;dimstar@opensuse.org&gt;" date="1709208000">- Use %patch -P N instead of deprecated %patchN.</changelog>
  <changelog author="Sarah Kriesch &lt;sarah.kriesch@opensuse.org&gt;" date="1709812800">- Remove constraints file because improved memory usage for s390x</changelog>
  <changelog author="Aaron Puchert &lt;aaronpuchert@alice-dsl.net&gt;" date="1710244800">- Require LLVM &lt;= 17 for now, because LLVM 18 doesn't seem to work.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1715169600">- Upgrade to 15.7 (bsc#1224051):
  * bsc#1224038, CVE-2024-4317: Restrict visibility of pg_stats_ext
    and pg_stats_ext_exprs entries to the table owner. See the
    release notes for the steps that have to be taken to fix
    existing PostgreSQL instances.
  * Fix incompatibility with LLVM 18.
  * https://www.postgresql.org/docs/release/15.7/
- Prepare for PostgreSQL 17.
- Make sure all compilation and doc generation happens in %build.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1723291200">- Upgrade to 15.8 (bsc#1229013):
  * bsc#1229013, CVE-2024-7348 PostgreSQL relation replacement
    during pg_dump executes arbitrary SQL
  * https://www.postgresql.org/about/news/p-2910/
  * https://www.postgresql.org/docs/release/15.8/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1730808000">- Sync spec file from postgresql17.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1731499200">- Upgrade to 15.9:
  * CVE-2024-10976, bsc#1233323: Ensure cached plans are marked as
    dependent on the calling role when RLS applies to a
    non-top-level table reference.
  * CVE-2024-10977, bsc#1233325: Make libpq discard error messages
    received during SSL or GSS protocol negotiation.
  * CVE-2024-10978, bsc#1233326: Fix unintended interactions
    between SET SESSION AUTHORIZATION and SET ROLE
  * CVE-2024-10979, bsc#1233327: Prevent trusted PL/Perl code from
    changing environment variables.
  * https://www.postgresql.org/about/news/p-2955/
  * https://www.postgresql.org/docs/release/15.9/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1732017600">- Upgrade to 15.10
  * Repair ABI break for extensions that work with struct
    ResultRelInfo.
  * Restore functionality of ALTER {ROLE|DATABASE} SET role.
  * Fix cases where a logical replication slot's restart_lsn could
    go backwards.
  * Avoid deleting still-needed WAL files during pg_rewind.
  * Fix race conditions associated with dropping shared statistics
    entries.
  * Count index scans in contrib/bloom indexes in the statistics
    views, such as the pg_stat_user_indexes.idx_scan counter.
  * Fix crash when checking to see if an index's opclass options
    have changed.
  * Avoid assertion failure caused by disconnected NFA sub-graphs
    in regular expression parsing.
  * https://www.postgresql.org/about/news/p-2965/
  * https://www.postgresql.org/docs/release/15.10/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 15.11:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/15.11/
  * https://www.postgresql.org/about/news/-3015/
- Disable LLVM JIT on loongarch64</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 15.12:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/15.12/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 15.13:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/15.13/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Upgrade to 15.14:
  * https://www.postgresql.org/about/news/postgresql-176-1610-1514-1419-1322-and-18-beta-3-released-3118/
  * https://www.postgresql.org/docs/release/15.14/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1758801600">- Sync spec file from version 18.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Upgrade to 15.15:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/15.15/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 15.16:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/15.16/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 15.17 to fix two regressions in 15.16:
  * https://www.postgresql.org/docs/release/15.17/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
</package>
<package pkgid="846adf786a1547ab2566055964fb43c220e00013484dcf9ef11c4a554be01804623a12554f85e78cc151089412c9994fc2a67a9b814b9d9e71070b5121352ca0" name="postgresql15-server-devel" arch="s390x">
  <version epoch="0" ver="15.17" rel="87.2"/>
  <changelog author="Dominique Leuenberger &lt;dimstar@opensuse.org&gt;" date="1709208000">- Use %patch -P N instead of deprecated %patchN.</changelog>
  <changelog author="Sarah Kriesch &lt;sarah.kriesch@opensuse.org&gt;" date="1709812800">- Remove constraints file because improved memory usage for s390x</changelog>
  <changelog author="Aaron Puchert &lt;aaronpuchert@alice-dsl.net&gt;" date="1710244800">- Require LLVM &lt;= 17 for now, because LLVM 18 doesn't seem to work.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1715169600">- Upgrade to 15.7 (bsc#1224051):
  * bsc#1224038, CVE-2024-4317: Restrict visibility of pg_stats_ext
    and pg_stats_ext_exprs entries to the table owner. See the
    release notes for the steps that have to be taken to fix
    existing PostgreSQL instances.
  * Fix incompatibility with LLVM 18.
  * https://www.postgresql.org/docs/release/15.7/
- Prepare for PostgreSQL 17.
- Make sure all compilation and doc generation happens in %build.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1723291200">- Upgrade to 15.8 (bsc#1229013):
  * bsc#1229013, CVE-2024-7348 PostgreSQL relation replacement
    during pg_dump executes arbitrary SQL
  * https://www.postgresql.org/about/news/p-2910/
  * https://www.postgresql.org/docs/release/15.8/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1730808000">- Sync spec file from postgresql17.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1731499200">- Upgrade to 15.9:
  * CVE-2024-10976, bsc#1233323: Ensure cached plans are marked as
    dependent on the calling role when RLS applies to a
    non-top-level table reference.
  * CVE-2024-10977, bsc#1233325: Make libpq discard error messages
    received during SSL or GSS protocol negotiation.
  * CVE-2024-10978, bsc#1233326: Fix unintended interactions
    between SET SESSION AUTHORIZATION and SET ROLE
  * CVE-2024-10979, bsc#1233327: Prevent trusted PL/Perl code from
    changing environment variables.
  * https://www.postgresql.org/about/news/p-2955/
  * https://www.postgresql.org/docs/release/15.9/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1732017600">- Upgrade to 15.10
  * Repair ABI break for extensions that work with struct
    ResultRelInfo.
  * Restore functionality of ALTER {ROLE|DATABASE} SET role.
  * Fix cases where a logical replication slot's restart_lsn could
    go backwards.
  * Avoid deleting still-needed WAL files during pg_rewind.
  * Fix race conditions associated with dropping shared statistics
    entries.
  * Count index scans in contrib/bloom indexes in the statistics
    views, such as the pg_stat_user_indexes.idx_scan counter.
  * Fix crash when checking to see if an index's opclass options
    have changed.
  * Avoid assertion failure caused by disconnected NFA sub-graphs
    in regular expression parsing.
  * https://www.postgresql.org/about/news/p-2965/
  * https://www.postgresql.org/docs/release/15.10/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 15.11:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/15.11/
  * https://www.postgresql.org/about/news/-3015/
- Disable LLVM JIT on loongarch64</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 15.12:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/15.12/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 15.13:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/15.13/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Upgrade to 15.14:
  * https://www.postgresql.org/about/news/postgresql-176-1610-1514-1419-1322-and-18-beta-3-released-3118/
  * https://www.postgresql.org/docs/release/15.14/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1758801600">- Sync spec file from version 18.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Upgrade to 15.15:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/15.15/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 15.16:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/15.16/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 15.17 to fix two regressions in 15.16:
  * https://www.postgresql.org/docs/release/15.17/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
</package>
<package pkgid="45afb8cc760591afb315fff4cfcbed0fd50829f39b1804549e0fa4fe013d881ecedc42670a3b0f1b3b92b9791872629803667ed74710cd3f1b593890e791c8e6" name="postgresql15-server-devel" arch="x86_64">
  <version epoch="0" ver="15.18" rel="97.2"/>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1715169600">- Upgrade to 15.7 (bsc#1224051):
  * bsc#1224038, CVE-2024-4317: Restrict visibility of pg_stats_ext
    and pg_stats_ext_exprs entries to the table owner. See the
    release notes for the steps that have to be taken to fix
    existing PostgreSQL instances.
  * Fix incompatibility with LLVM 18.
  * https://www.postgresql.org/docs/release/15.7/
- Prepare for PostgreSQL 17.
- Make sure all compilation and doc generation happens in %build.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1723291200">- Upgrade to 15.8 (bsc#1229013):
  * bsc#1229013, CVE-2024-7348 PostgreSQL relation replacement
    during pg_dump executes arbitrary SQL
  * https://www.postgresql.org/about/news/p-2910/
  * https://www.postgresql.org/docs/release/15.8/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1730808000">- Sync spec file from postgresql17.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1731499200">- Upgrade to 15.9:
  * CVE-2024-10976, bsc#1233323: Ensure cached plans are marked as
    dependent on the calling role when RLS applies to a
    non-top-level table reference.
  * CVE-2024-10977, bsc#1233325: Make libpq discard error messages
    received during SSL or GSS protocol negotiation.
  * CVE-2024-10978, bsc#1233326: Fix unintended interactions
    between SET SESSION AUTHORIZATION and SET ROLE
  * CVE-2024-10979, bsc#1233327: Prevent trusted PL/Perl code from
    changing environment variables.
  * https://www.postgresql.org/about/news/p-2955/
  * https://www.postgresql.org/docs/release/15.9/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1732017600">- Upgrade to 15.10
  * Repair ABI break for extensions that work with struct
    ResultRelInfo.
  * Restore functionality of ALTER {ROLE|DATABASE} SET role.
  * Fix cases where a logical replication slot's restart_lsn could
    go backwards.
  * Avoid deleting still-needed WAL files during pg_rewind.
  * Fix race conditions associated with dropping shared statistics
    entries.
  * Count index scans in contrib/bloom indexes in the statistics
    views, such as the pg_stat_user_indexes.idx_scan counter.
  * Fix crash when checking to see if an index's opclass options
    have changed.
  * Avoid assertion failure caused by disconnected NFA sub-graphs
    in regular expression parsing.
  * https://www.postgresql.org/about/news/p-2965/
  * https://www.postgresql.org/docs/release/15.10/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 15.11:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/15.11/
  * https://www.postgresql.org/about/news/-3015/
- Disable LLVM JIT on loongarch64</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 15.12:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/15.12/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 15.13:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/15.13/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Upgrade to 15.14:
  * https://www.postgresql.org/about/news/postgresql-176-1610-1514-1419-1322-and-18-beta-3-released-3118/
  * https://www.postgresql.org/docs/release/15.14/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1758801600">- Sync spec file from version 18.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Upgrade to 15.15:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/15.15/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 15.16:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/15.16/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 15.17 to fix two regressions in 15.16:
  * https://www.postgresql.org/docs/release/15.17/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1774872000">- Get rid of update-alternatives for openSUSE/SLE 16.0 and newer
  to support immutable systems and transactional updates.
  (jsc#PED-14823)</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1777550400">- bsc#1263804: After dropping update-alternatives we have to
  package /usr/bin/pg_config as an actual symlink, not %ghost.
- Fix spelling of build conditionals.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1778673600">- Update to version 15.18:
  * bsc#1265172, CVE-2026-6472: ensure the user has CREATE
    privilege on the schema specified
  * bsc#1265173, CVE-2026-6473: integer overflows in
    memory-allocation calculations
  * bsc#1265174, CVE-2026-6474: Guard against malicious time zone
    names
  * bsc#1265175, CVE-2026-6475: Prevent path traversal in
    pg_basebackup and pg_rewind
  * bsc#1265177, CVE-2026-6477: Mark PQfn() as unsafe, and avoid
    using it within libpq
  * bsc#1265178, CVE-2026-6478: Use timing-safe string comparisons
    in authentication code
  * bsc#1265179, CVE-2026-6479: Prevent unbounded recursion while
    processing startup packets
  * bsc#1265181, CVE-2026-6637: Prevent SQL injection and buffer
    overruns in contrib/spi
  * https://www.postgresql.org/docs/release/15.18/</changelog>
</package>
<package pkgid="b89f4f1d7395c540e76a1bfffe35f1485717d1b5de4b82a53f760143d99c5551e72d3a14c38c958803f309185aea3065094166ab6d5439f56eb1ca3dae9656ae" name="postgresql15-test" arch="ppc64le">
  <version epoch="0" ver="15.17" rel="86.1"/>
  <changelog author="Dominique Leuenberger &lt;dimstar@opensuse.org&gt;" date="1709208000">- Use %patch -P N instead of deprecated %patchN.</changelog>
  <changelog author="Sarah Kriesch &lt;sarah.kriesch@opensuse.org&gt;" date="1709812800">- Remove constraints file because improved memory usage for s390x</changelog>
  <changelog author="Aaron Puchert &lt;aaronpuchert@alice-dsl.net&gt;" date="1710244800">- Require LLVM &lt;= 17 for now, because LLVM 18 doesn't seem to work.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1715169600">- Upgrade to 15.7 (bsc#1224051):
  * bsc#1224038, CVE-2024-4317: Restrict visibility of pg_stats_ext
    and pg_stats_ext_exprs entries to the table owner. See the
    release notes for the steps that have to be taken to fix
    existing PostgreSQL instances.
  * Fix incompatibility with LLVM 18.
  * https://www.postgresql.org/docs/release/15.7/
- Prepare for PostgreSQL 17.
- Make sure all compilation and doc generation happens in %build.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1723291200">- Upgrade to 15.8 (bsc#1229013):
  * bsc#1229013, CVE-2024-7348 PostgreSQL relation replacement
    during pg_dump executes arbitrary SQL
  * https://www.postgresql.org/about/news/p-2910/
  * https://www.postgresql.org/docs/release/15.8/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1730808000">- Sync spec file from postgresql17.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1731499200">- Upgrade to 15.9:
  * CVE-2024-10976, bsc#1233323: Ensure cached plans are marked as
    dependent on the calling role when RLS applies to a
    non-top-level table reference.
  * CVE-2024-10977, bsc#1233325: Make libpq discard error messages
    received during SSL or GSS protocol negotiation.
  * CVE-2024-10978, bsc#1233326: Fix unintended interactions
    between SET SESSION AUTHORIZATION and SET ROLE
  * CVE-2024-10979, bsc#1233327: Prevent trusted PL/Perl code from
    changing environment variables.
  * https://www.postgresql.org/about/news/p-2955/
  * https://www.postgresql.org/docs/release/15.9/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1732017600">- Upgrade to 15.10
  * Repair ABI break for extensions that work with struct
    ResultRelInfo.
  * Restore functionality of ALTER {ROLE|DATABASE} SET role.
  * Fix cases where a logical replication slot's restart_lsn could
    go backwards.
  * Avoid deleting still-needed WAL files during pg_rewind.
  * Fix race conditions associated with dropping shared statistics
    entries.
  * Count index scans in contrib/bloom indexes in the statistics
    views, such as the pg_stat_user_indexes.idx_scan counter.
  * Fix crash when checking to see if an index's opclass options
    have changed.
  * Avoid assertion failure caused by disconnected NFA sub-graphs
    in regular expression parsing.
  * https://www.postgresql.org/about/news/p-2965/
  * https://www.postgresql.org/docs/release/15.10/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 15.11:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/15.11/
  * https://www.postgresql.org/about/news/-3015/
- Disable LLVM JIT on loongarch64</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 15.12:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/15.12/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 15.13:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/15.13/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Upgrade to 15.14:
  * https://www.postgresql.org/about/news/postgresql-176-1610-1514-1419-1322-and-18-beta-3-released-3118/
  * https://www.postgresql.org/docs/release/15.14/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1758801600">- Sync spec file from version 18.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Upgrade to 15.15:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/15.15/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 15.16:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/15.16/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 15.17 to fix two regressions in 15.16:
  * https://www.postgresql.org/docs/release/15.17/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
</package>
<package pkgid="f1138aef1128ba10baf146247feb515d44f0574015897016e67d174d4e5c6c67dc7de8e75ac1d382f13273329e419cec31b6042c8a63d302706eb4e4ac67b075" name="postgresql15-test" arch="aarch64">
  <version epoch="0" ver="15.17" rel="87.2"/>
  <changelog author="Dominique Leuenberger &lt;dimstar@opensuse.org&gt;" date="1709208000">- Use %patch -P N instead of deprecated %patchN.</changelog>
  <changelog author="Sarah Kriesch &lt;sarah.kriesch@opensuse.org&gt;" date="1709812800">- Remove constraints file because improved memory usage for s390x</changelog>
  <changelog author="Aaron Puchert &lt;aaronpuchert@alice-dsl.net&gt;" date="1710244800">- Require LLVM &lt;= 17 for now, because LLVM 18 doesn't seem to work.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1715169600">- Upgrade to 15.7 (bsc#1224051):
  * bsc#1224038, CVE-2024-4317: Restrict visibility of pg_stats_ext
    and pg_stats_ext_exprs entries to the table owner. See the
    release notes for the steps that have to be taken to fix
    existing PostgreSQL instances.
  * Fix incompatibility with LLVM 18.
  * https://www.postgresql.org/docs/release/15.7/
- Prepare for PostgreSQL 17.
- Make sure all compilation and doc generation happens in %build.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1723291200">- Upgrade to 15.8 (bsc#1229013):
  * bsc#1229013, CVE-2024-7348 PostgreSQL relation replacement
    during pg_dump executes arbitrary SQL
  * https://www.postgresql.org/about/news/p-2910/
  * https://www.postgresql.org/docs/release/15.8/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1730808000">- Sync spec file from postgresql17.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1731499200">- Upgrade to 15.9:
  * CVE-2024-10976, bsc#1233323: Ensure cached plans are marked as
    dependent on the calling role when RLS applies to a
    non-top-level table reference.
  * CVE-2024-10977, bsc#1233325: Make libpq discard error messages
    received during SSL or GSS protocol negotiation.
  * CVE-2024-10978, bsc#1233326: Fix unintended interactions
    between SET SESSION AUTHORIZATION and SET ROLE
  * CVE-2024-10979, bsc#1233327: Prevent trusted PL/Perl code from
    changing environment variables.
  * https://www.postgresql.org/about/news/p-2955/
  * https://www.postgresql.org/docs/release/15.9/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1732017600">- Upgrade to 15.10
  * Repair ABI break for extensions that work with struct
    ResultRelInfo.
  * Restore functionality of ALTER {ROLE|DATABASE} SET role.
  * Fix cases where a logical replication slot's restart_lsn could
    go backwards.
  * Avoid deleting still-needed WAL files during pg_rewind.
  * Fix race conditions associated with dropping shared statistics
    entries.
  * Count index scans in contrib/bloom indexes in the statistics
    views, such as the pg_stat_user_indexes.idx_scan counter.
  * Fix crash when checking to see if an index's opclass options
    have changed.
  * Avoid assertion failure caused by disconnected NFA sub-graphs
    in regular expression parsing.
  * https://www.postgresql.org/about/news/p-2965/
  * https://www.postgresql.org/docs/release/15.10/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 15.11:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/15.11/
  * https://www.postgresql.org/about/news/-3015/
- Disable LLVM JIT on loongarch64</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 15.12:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/15.12/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 15.13:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/15.13/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Upgrade to 15.14:
  * https://www.postgresql.org/about/news/postgresql-176-1610-1514-1419-1322-and-18-beta-3-released-3118/
  * https://www.postgresql.org/docs/release/15.14/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1758801600">- Sync spec file from version 18.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Upgrade to 15.15:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/15.15/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 15.16:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/15.16/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 15.17 to fix two regressions in 15.16:
  * https://www.postgresql.org/docs/release/15.17/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
</package>
<package pkgid="e7fafd6e81850b84a0a5322da3714bf3e3c734752ad20c3700e1e0384b7245848a2a0f025c9e55611c73f02a356b5fa2a65965a0c58b6e813894117894bcd654" name="postgresql15-test" arch="s390x">
  <version epoch="0" ver="15.17" rel="87.2"/>
  <changelog author="Dominique Leuenberger &lt;dimstar@opensuse.org&gt;" date="1709208000">- Use %patch -P N instead of deprecated %patchN.</changelog>
  <changelog author="Sarah Kriesch &lt;sarah.kriesch@opensuse.org&gt;" date="1709812800">- Remove constraints file because improved memory usage for s390x</changelog>
  <changelog author="Aaron Puchert &lt;aaronpuchert@alice-dsl.net&gt;" date="1710244800">- Require LLVM &lt;= 17 for now, because LLVM 18 doesn't seem to work.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1715169600">- Upgrade to 15.7 (bsc#1224051):
  * bsc#1224038, CVE-2024-4317: Restrict visibility of pg_stats_ext
    and pg_stats_ext_exprs entries to the table owner. See the
    release notes for the steps that have to be taken to fix
    existing PostgreSQL instances.
  * Fix incompatibility with LLVM 18.
  * https://www.postgresql.org/docs/release/15.7/
- Prepare for PostgreSQL 17.
- Make sure all compilation and doc generation happens in %build.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1723291200">- Upgrade to 15.8 (bsc#1229013):
  * bsc#1229013, CVE-2024-7348 PostgreSQL relation replacement
    during pg_dump executes arbitrary SQL
  * https://www.postgresql.org/about/news/p-2910/
  * https://www.postgresql.org/docs/release/15.8/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1730808000">- Sync spec file from postgresql17.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1731499200">- Upgrade to 15.9:
  * CVE-2024-10976, bsc#1233323: Ensure cached plans are marked as
    dependent on the calling role when RLS applies to a
    non-top-level table reference.
  * CVE-2024-10977, bsc#1233325: Make libpq discard error messages
    received during SSL or GSS protocol negotiation.
  * CVE-2024-10978, bsc#1233326: Fix unintended interactions
    between SET SESSION AUTHORIZATION and SET ROLE
  * CVE-2024-10979, bsc#1233327: Prevent trusted PL/Perl code from
    changing environment variables.
  * https://www.postgresql.org/about/news/p-2955/
  * https://www.postgresql.org/docs/release/15.9/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1732017600">- Upgrade to 15.10
  * Repair ABI break for extensions that work with struct
    ResultRelInfo.
  * Restore functionality of ALTER {ROLE|DATABASE} SET role.
  * Fix cases where a logical replication slot's restart_lsn could
    go backwards.
  * Avoid deleting still-needed WAL files during pg_rewind.
  * Fix race conditions associated with dropping shared statistics
    entries.
  * Count index scans in contrib/bloom indexes in the statistics
    views, such as the pg_stat_user_indexes.idx_scan counter.
  * Fix crash when checking to see if an index's opclass options
    have changed.
  * Avoid assertion failure caused by disconnected NFA sub-graphs
    in regular expression parsing.
  * https://www.postgresql.org/about/news/p-2965/
  * https://www.postgresql.org/docs/release/15.10/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 15.11:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/15.11/
  * https://www.postgresql.org/about/news/-3015/
- Disable LLVM JIT on loongarch64</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 15.12:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/15.12/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 15.13:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/15.13/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Upgrade to 15.14:
  * https://www.postgresql.org/about/news/postgresql-176-1610-1514-1419-1322-and-18-beta-3-released-3118/
  * https://www.postgresql.org/docs/release/15.14/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1758801600">- Sync spec file from version 18.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Upgrade to 15.15:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/15.15/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 15.16:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/15.16/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 15.17 to fix two regressions in 15.16:
  * https://www.postgresql.org/docs/release/15.17/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
</package>
<package pkgid="523912db575f827c3d329f289289c2d5f95ee65a07a6e3b5c189b0728771c43be92ee4159dfb1f4aaa95715fd4bf600b1ada903234bc40e957fac744389236c9" name="postgresql15-test" arch="x86_64">
  <version epoch="0" ver="15.18" rel="97.2"/>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1715169600">- Upgrade to 15.7 (bsc#1224051):
  * bsc#1224038, CVE-2024-4317: Restrict visibility of pg_stats_ext
    and pg_stats_ext_exprs entries to the table owner. See the
    release notes for the steps that have to be taken to fix
    existing PostgreSQL instances.
  * Fix incompatibility with LLVM 18.
  * https://www.postgresql.org/docs/release/15.7/
- Prepare for PostgreSQL 17.
- Make sure all compilation and doc generation happens in %build.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1723291200">- Upgrade to 15.8 (bsc#1229013):
  * bsc#1229013, CVE-2024-7348 PostgreSQL relation replacement
    during pg_dump executes arbitrary SQL
  * https://www.postgresql.org/about/news/p-2910/
  * https://www.postgresql.org/docs/release/15.8/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1730808000">- Sync spec file from postgresql17.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1731499200">- Upgrade to 15.9:
  * CVE-2024-10976, bsc#1233323: Ensure cached plans are marked as
    dependent on the calling role when RLS applies to a
    non-top-level table reference.
  * CVE-2024-10977, bsc#1233325: Make libpq discard error messages
    received during SSL or GSS protocol negotiation.
  * CVE-2024-10978, bsc#1233326: Fix unintended interactions
    between SET SESSION AUTHORIZATION and SET ROLE
  * CVE-2024-10979, bsc#1233327: Prevent trusted PL/Perl code from
    changing environment variables.
  * https://www.postgresql.org/about/news/p-2955/
  * https://www.postgresql.org/docs/release/15.9/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1732017600">- Upgrade to 15.10
  * Repair ABI break for extensions that work with struct
    ResultRelInfo.
  * Restore functionality of ALTER {ROLE|DATABASE} SET role.
  * Fix cases where a logical replication slot's restart_lsn could
    go backwards.
  * Avoid deleting still-needed WAL files during pg_rewind.
  * Fix race conditions associated with dropping shared statistics
    entries.
  * Count index scans in contrib/bloom indexes in the statistics
    views, such as the pg_stat_user_indexes.idx_scan counter.
  * Fix crash when checking to see if an index's opclass options
    have changed.
  * Avoid assertion failure caused by disconnected NFA sub-graphs
    in regular expression parsing.
  * https://www.postgresql.org/about/news/p-2965/
  * https://www.postgresql.org/docs/release/15.10/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 15.11:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/15.11/
  * https://www.postgresql.org/about/news/-3015/
- Disable LLVM JIT on loongarch64</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 15.12:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/15.12/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 15.13:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/15.13/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Upgrade to 15.14:
  * https://www.postgresql.org/about/news/postgresql-176-1610-1514-1419-1322-and-18-beta-3-released-3118/
  * https://www.postgresql.org/docs/release/15.14/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1758801600">- Sync spec file from version 18.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Upgrade to 15.15:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/15.15/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 15.16:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/15.16/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 15.17 to fix two regressions in 15.16:
  * https://www.postgresql.org/docs/release/15.17/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1774872000">- Get rid of update-alternatives for openSUSE/SLE 16.0 and newer
  to support immutable systems and transactional updates.
  (jsc#PED-14823)</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1777550400">- bsc#1263804: After dropping update-alternatives we have to
  package /usr/bin/pg_config as an actual symlink, not %ghost.
- Fix spelling of build conditionals.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1778673600">- Update to version 15.18:
  * bsc#1265172, CVE-2026-6472: ensure the user has CREATE
    privilege on the schema specified
  * bsc#1265173, CVE-2026-6473: integer overflows in
    memory-allocation calculations
  * bsc#1265174, CVE-2026-6474: Guard against malicious time zone
    names
  * bsc#1265175, CVE-2026-6475: Prevent path traversal in
    pg_basebackup and pg_rewind
  * bsc#1265177, CVE-2026-6477: Mark PQfn() as unsafe, and avoid
    using it within libpq
  * bsc#1265178, CVE-2026-6478: Use timing-safe string comparisons
    in authentication code
  * bsc#1265179, CVE-2026-6479: Prevent unbounded recursion while
    processing startup packets
  * bsc#1265181, CVE-2026-6637: Prevent SQL injection and buffer
    overruns in contrib/spi
  * https://www.postgresql.org/docs/release/15.18/</changelog>
</package>
<package pkgid="a076946d3030b1cc64c0376e1f8065cfc55f0d813510b2dd5c42dc4368611161f3a160bce417a43d1609a50f88748371a73d200a56f23240d875ac2a28b7796c" name="postgresql16" arch="aarch64">
  <version epoch="0" ver="16.13" rel="70.2"/>
  <changelog author="Aaron Puchert &lt;aaronpuchert@alice-dsl.net&gt;" date="1710244800">- Require LLVM &lt;= 17 for now, because LLVM 18 doesn't seem to work.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1715169600">- Upgrade to 16.3 (bsc#1224051):
  * bsc#1224038, CVE-2024-4317: Restrict visibility of pg_stats_ext
    and pg_stats_ext_exprs entries to the table owner. See the
    release notes for the steps that have to be taken to fix
    existing PostgreSQL instances.
  * Fix incompatibility with LLVM 18.
  * https://www.postgresql.org/docs/release/16.3/
- Prepare for PostgreSQL 17.
- Make sure all compilation and doc generation happens in %build.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1723291200">- Upgrade to 16.4 (bsc#1229013):
  * bsc#1229013, CVE-2024-7348 PostgreSQL relation replacement
    during pg_dump executes arbitrary SQL
  * https://www.postgresql.org/about/news/p-2910/
  * https://www.postgresql.org/docs/release/16.4/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1726747200">- Don't build the libs and mini flavor anymore to hand over to
  PostgreSQL 17.</changelog>
  <changelog author="Antonio Teixeira &lt;antonio.teixeira@suse.com&gt;" date="1726833600">- Pull upstream patch to fix tests with timezone 2024b
  * postgresql-testsuite-timezone-fix.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1730808000">- Sync spec file from postgresql17.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1731499200">- Upgrade to 16.5:
  * CVE-2024-10976, bsc#1233323: Ensure cached plans are marked as
    dependent on the calling role when RLS applies to a
    non-top-level table reference.
  * CVE-2024-10977, bsc#1233325: Make libpq discard error messages
    received during SSL or GSS protocol negotiation.
  * CVE-2024-10978, bsc#1233326: Fix unintended interactions
    between SET SESSION AUTHORIZATION and SET ROLE
  * CVE-2024-10979, bsc#1233327: Prevent trusted PL/Perl code from
    changing environment variables.
  * obsoletes postgresql-testsuite-timezone-fix.patch
  * https://www.postgresql.org/about/news/p-2955/
  * https://www.postgresql.org/docs/release/16.5/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1732017600">- Upgrade to 16.6:
  * Repair ABI break for extensions that work with struct
    ResultRelInfo.
  * Restore functionality of ALTER {ROLE|DATABASE} SET role.
  * Fix cases where a logical replication slot's restart_lsn could
    go backwards.
  * Avoid deleting still-needed WAL files during pg_rewind.
  * Fix race conditions associated with dropping shared statistics
    entries.
  * Count index scans in contrib/bloom indexes in the statistics
    views, such as the pg_stat_user_indexes.idx_scan counter.
  * Fix crash when checking to see if an index's opclass options
    have changed.
  * Avoid assertion failure caused by disconnected NFA sub-graphs
    in regular expression parsing.
  * https://www.postgresql.org/about/news/p-2965/
  * https://www.postgresql.org/docs/release/16.6/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 16.7:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/16.7/
  * https://www.postgresql.org/about/news/-3015/
- Disable LLVM JIT on loongarch64</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 16.8:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/16.8/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 16.9:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/16.9/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to Fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Upgrade to 16.10:
  * https://www.postgresql.org/about/news/postgresql-176-1610-1514-1419-1322-and-18-beta-3-released-3118/
  * https://www.postgresql.org/docs/release/16.10/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1758628800">- Sync spec file from version 18.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Upgrade to 16.11:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/16.11/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 16.12:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/16.12/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 16.13 to fix two regressions in 16.12:
  * https://www.postgresql.org/docs/release/16.13/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
</package>
<package pkgid="6f60eeee86e776b363aa34ab8128c633b2a7f7f431d78c34f49e4a0f0b7030d73748afc32e6ac9cc265bbfbbb8a302f80a81a75b812f2a33f84a743f0f302740" name="postgresql16" arch="ppc64le">
  <version epoch="0" ver="16.13" rel="70.2"/>
  <changelog author="Aaron Puchert &lt;aaronpuchert@alice-dsl.net&gt;" date="1710244800">- Require LLVM &lt;= 17 for now, because LLVM 18 doesn't seem to work.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1715169600">- Upgrade to 16.3 (bsc#1224051):
  * bsc#1224038, CVE-2024-4317: Restrict visibility of pg_stats_ext
    and pg_stats_ext_exprs entries to the table owner. See the
    release notes for the steps that have to be taken to fix
    existing PostgreSQL instances.
  * Fix incompatibility with LLVM 18.
  * https://www.postgresql.org/docs/release/16.3/
- Prepare for PostgreSQL 17.
- Make sure all compilation and doc generation happens in %build.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1723291200">- Upgrade to 16.4 (bsc#1229013):
  * bsc#1229013, CVE-2024-7348 PostgreSQL relation replacement
    during pg_dump executes arbitrary SQL
  * https://www.postgresql.org/about/news/p-2910/
  * https://www.postgresql.org/docs/release/16.4/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1726747200">- Don't build the libs and mini flavor anymore to hand over to
  PostgreSQL 17.</changelog>
  <changelog author="Antonio Teixeira &lt;antonio.teixeira@suse.com&gt;" date="1726833600">- Pull upstream patch to fix tests with timezone 2024b
  * postgresql-testsuite-timezone-fix.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1730808000">- Sync spec file from postgresql17.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1731499200">- Upgrade to 16.5:
  * CVE-2024-10976, bsc#1233323: Ensure cached plans are marked as
    dependent on the calling role when RLS applies to a
    non-top-level table reference.
  * CVE-2024-10977, bsc#1233325: Make libpq discard error messages
    received during SSL or GSS protocol negotiation.
  * CVE-2024-10978, bsc#1233326: Fix unintended interactions
    between SET SESSION AUTHORIZATION and SET ROLE
  * CVE-2024-10979, bsc#1233327: Prevent trusted PL/Perl code from
    changing environment variables.
  * obsoletes postgresql-testsuite-timezone-fix.patch
  * https://www.postgresql.org/about/news/p-2955/
  * https://www.postgresql.org/docs/release/16.5/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1732017600">- Upgrade to 16.6:
  * Repair ABI break for extensions that work with struct
    ResultRelInfo.
  * Restore functionality of ALTER {ROLE|DATABASE} SET role.
  * Fix cases where a logical replication slot's restart_lsn could
    go backwards.
  * Avoid deleting still-needed WAL files during pg_rewind.
  * Fix race conditions associated with dropping shared statistics
    entries.
  * Count index scans in contrib/bloom indexes in the statistics
    views, such as the pg_stat_user_indexes.idx_scan counter.
  * Fix crash when checking to see if an index's opclass options
    have changed.
  * Avoid assertion failure caused by disconnected NFA sub-graphs
    in regular expression parsing.
  * https://www.postgresql.org/about/news/p-2965/
  * https://www.postgresql.org/docs/release/16.6/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 16.7:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/16.7/
  * https://www.postgresql.org/about/news/-3015/
- Disable LLVM JIT on loongarch64</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 16.8:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/16.8/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 16.9:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/16.9/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to Fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Upgrade to 16.10:
  * https://www.postgresql.org/about/news/postgresql-176-1610-1514-1419-1322-and-18-beta-3-released-3118/
  * https://www.postgresql.org/docs/release/16.10/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1758628800">- Sync spec file from version 18.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Upgrade to 16.11:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/16.11/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 16.12:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/16.12/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 16.13 to fix two regressions in 16.12:
  * https://www.postgresql.org/docs/release/16.13/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
</package>
<package pkgid="1ba9c3a0858dc561f7453ec17771a6fe7403c9de32bc16a584447c05b381c94573ce073406c9603d244c05a66d915519b3b3e1b33c7ac3908084e9aecc25fa18" name="postgresql16" arch="s390x">
  <version epoch="0" ver="16.13" rel="70.2"/>
  <changelog author="Aaron Puchert &lt;aaronpuchert@alice-dsl.net&gt;" date="1710244800">- Require LLVM &lt;= 17 for now, because LLVM 18 doesn't seem to work.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1715169600">- Upgrade to 16.3 (bsc#1224051):
  * bsc#1224038, CVE-2024-4317: Restrict visibility of pg_stats_ext
    and pg_stats_ext_exprs entries to the table owner. See the
    release notes for the steps that have to be taken to fix
    existing PostgreSQL instances.
  * Fix incompatibility with LLVM 18.
  * https://www.postgresql.org/docs/release/16.3/
- Prepare for PostgreSQL 17.
- Make sure all compilation and doc generation happens in %build.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1723291200">- Upgrade to 16.4 (bsc#1229013):
  * bsc#1229013, CVE-2024-7348 PostgreSQL relation replacement
    during pg_dump executes arbitrary SQL
  * https://www.postgresql.org/about/news/p-2910/
  * https://www.postgresql.org/docs/release/16.4/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1726747200">- Don't build the libs and mini flavor anymore to hand over to
  PostgreSQL 17.</changelog>
  <changelog author="Antonio Teixeira &lt;antonio.teixeira@suse.com&gt;" date="1726833600">- Pull upstream patch to fix tests with timezone 2024b
  * postgresql-testsuite-timezone-fix.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1730808000">- Sync spec file from postgresql17.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1731499200">- Upgrade to 16.5:
  * CVE-2024-10976, bsc#1233323: Ensure cached plans are marked as
    dependent on the calling role when RLS applies to a
    non-top-level table reference.
  * CVE-2024-10977, bsc#1233325: Make libpq discard error messages
    received during SSL or GSS protocol negotiation.
  * CVE-2024-10978, bsc#1233326: Fix unintended interactions
    between SET SESSION AUTHORIZATION and SET ROLE
  * CVE-2024-10979, bsc#1233327: Prevent trusted PL/Perl code from
    changing environment variables.
  * obsoletes postgresql-testsuite-timezone-fix.patch
  * https://www.postgresql.org/about/news/p-2955/
  * https://www.postgresql.org/docs/release/16.5/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1732017600">- Upgrade to 16.6:
  * Repair ABI break for extensions that work with struct
    ResultRelInfo.
  * Restore functionality of ALTER {ROLE|DATABASE} SET role.
  * Fix cases where a logical replication slot's restart_lsn could
    go backwards.
  * Avoid deleting still-needed WAL files during pg_rewind.
  * Fix race conditions associated with dropping shared statistics
    entries.
  * Count index scans in contrib/bloom indexes in the statistics
    views, such as the pg_stat_user_indexes.idx_scan counter.
  * Fix crash when checking to see if an index's opclass options
    have changed.
  * Avoid assertion failure caused by disconnected NFA sub-graphs
    in regular expression parsing.
  * https://www.postgresql.org/about/news/p-2965/
  * https://www.postgresql.org/docs/release/16.6/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 16.7:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/16.7/
  * https://www.postgresql.org/about/news/-3015/
- Disable LLVM JIT on loongarch64</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 16.8:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/16.8/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 16.9:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/16.9/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to Fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Upgrade to 16.10:
  * https://www.postgresql.org/about/news/postgresql-176-1610-1514-1419-1322-and-18-beta-3-released-3118/
  * https://www.postgresql.org/docs/release/16.10/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1758628800">- Sync spec file from version 18.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Upgrade to 16.11:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/16.11/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 16.12:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/16.12/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 16.13 to fix two regressions in 16.12:
  * https://www.postgresql.org/docs/release/16.13/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
</package>
<package pkgid="a78c1a1c3a10f37f26be9a2976697d9640ed428db45ea997e1f16f71854588ab2119b6e60644b521666c1406a3213c915a4a54e2338183cc1311f085032db999" name="postgresql16" arch="src">
  <version epoch="0" ver="16.13" rel="70.2"/>
  <changelog author="Aaron Puchert &lt;aaronpuchert@alice-dsl.net&gt;" date="1710244800">- Require LLVM &lt;= 17 for now, because LLVM 18 doesn't seem to work.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1715169600">- Upgrade to 16.3 (bsc#1224051):
  * bsc#1224038, CVE-2024-4317: Restrict visibility of pg_stats_ext
    and pg_stats_ext_exprs entries to the table owner. See the
    release notes for the steps that have to be taken to fix
    existing PostgreSQL instances.
  * Fix incompatibility with LLVM 18.
  * https://www.postgresql.org/docs/release/16.3/
- Prepare for PostgreSQL 17.
- Make sure all compilation and doc generation happens in %build.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1723291200">- Upgrade to 16.4 (bsc#1229013):
  * bsc#1229013, CVE-2024-7348 PostgreSQL relation replacement
    during pg_dump executes arbitrary SQL
  * https://www.postgresql.org/about/news/p-2910/
  * https://www.postgresql.org/docs/release/16.4/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1726747200">- Don't build the libs and mini flavor anymore to hand over to
  PostgreSQL 17.</changelog>
  <changelog author="Antonio Teixeira &lt;antonio.teixeira@suse.com&gt;" date="1726833600">- Pull upstream patch to fix tests with timezone 2024b
  * postgresql-testsuite-timezone-fix.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1730808000">- Sync spec file from postgresql17.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1731499200">- Upgrade to 16.5:
  * CVE-2024-10976, bsc#1233323: Ensure cached plans are marked as
    dependent on the calling role when RLS applies to a
    non-top-level table reference.
  * CVE-2024-10977, bsc#1233325: Make libpq discard error messages
    received during SSL or GSS protocol negotiation.
  * CVE-2024-10978, bsc#1233326: Fix unintended interactions
    between SET SESSION AUTHORIZATION and SET ROLE
  * CVE-2024-10979, bsc#1233327: Prevent trusted PL/Perl code from
    changing environment variables.
  * obsoletes postgresql-testsuite-timezone-fix.patch
  * https://www.postgresql.org/about/news/p-2955/
  * https://www.postgresql.org/docs/release/16.5/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1732017600">- Upgrade to 16.6:
  * Repair ABI break for extensions that work with struct
    ResultRelInfo.
  * Restore functionality of ALTER {ROLE|DATABASE} SET role.
  * Fix cases where a logical replication slot's restart_lsn could
    go backwards.
  * Avoid deleting still-needed WAL files during pg_rewind.
  * Fix race conditions associated with dropping shared statistics
    entries.
  * Count index scans in contrib/bloom indexes in the statistics
    views, such as the pg_stat_user_indexes.idx_scan counter.
  * Fix crash when checking to see if an index's opclass options
    have changed.
  * Avoid assertion failure caused by disconnected NFA sub-graphs
    in regular expression parsing.
  * https://www.postgresql.org/about/news/p-2965/
  * https://www.postgresql.org/docs/release/16.6/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 16.7:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/16.7/
  * https://www.postgresql.org/about/news/-3015/
- Disable LLVM JIT on loongarch64</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 16.8:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/16.8/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 16.9:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/16.9/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to Fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Upgrade to 16.10:
  * https://www.postgresql.org/about/news/postgresql-176-1610-1514-1419-1322-and-18-beta-3-released-3118/
  * https://www.postgresql.org/docs/release/16.10/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1758628800">- Sync spec file from version 18.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Upgrade to 16.11:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/16.11/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 16.12:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/16.12/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 16.13 to fix two regressions in 16.12:
  * https://www.postgresql.org/docs/release/16.13/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
</package>
<package pkgid="7d281e7bfb353c5324c2d4da241ad1dcc95a8a90bfff2d67b6539cb68f123c2176c8cd5ae63fba97479cc12a79ff8afe1b7e471b310c99599578ed21a778f269" name="postgresql16" arch="src">
  <version epoch="0" ver="16.14" rel="80.2"/>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1726747200">- Don't build the libs and mini flavor anymore to hand over to
  PostgreSQL 17.</changelog>
  <changelog author="Antonio Teixeira &lt;antonio.teixeira@suse.com&gt;" date="1726833600">- Pull upstream patch to fix tests with timezone 2024b
  * postgresql-testsuite-timezone-fix.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1730808000">- Sync spec file from postgresql17.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1731499200">- Upgrade to 16.5:
  * CVE-2024-10976, bsc#1233323: Ensure cached plans are marked as
    dependent on the calling role when RLS applies to a
    non-top-level table reference.
  * CVE-2024-10977, bsc#1233325: Make libpq discard error messages
    received during SSL or GSS protocol negotiation.
  * CVE-2024-10978, bsc#1233326: Fix unintended interactions
    between SET SESSION AUTHORIZATION and SET ROLE
  * CVE-2024-10979, bsc#1233327: Prevent trusted PL/Perl code from
    changing environment variables.
  * obsoletes postgresql-testsuite-timezone-fix.patch
  * https://www.postgresql.org/about/news/p-2955/
  * https://www.postgresql.org/docs/release/16.5/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1732017600">- Upgrade to 16.6:
  * Repair ABI break for extensions that work with struct
    ResultRelInfo.
  * Restore functionality of ALTER {ROLE|DATABASE} SET role.
  * Fix cases where a logical replication slot's restart_lsn could
    go backwards.
  * Avoid deleting still-needed WAL files during pg_rewind.
  * Fix race conditions associated with dropping shared statistics
    entries.
  * Count index scans in contrib/bloom indexes in the statistics
    views, such as the pg_stat_user_indexes.idx_scan counter.
  * Fix crash when checking to see if an index's opclass options
    have changed.
  * Avoid assertion failure caused by disconnected NFA sub-graphs
    in regular expression parsing.
  * https://www.postgresql.org/about/news/p-2965/
  * https://www.postgresql.org/docs/release/16.6/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 16.7:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/16.7/
  * https://www.postgresql.org/about/news/-3015/
- Disable LLVM JIT on loongarch64</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 16.8:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/16.8/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 16.9:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/16.9/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to Fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Upgrade to 16.10:
  * https://www.postgresql.org/about/news/postgresql-176-1610-1514-1419-1322-and-18-beta-3-released-3118/
  * https://www.postgresql.org/docs/release/16.10/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1758628800">- Sync spec file from version 18.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Upgrade to 16.11:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/16.11/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 16.12:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/16.12/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 16.13 to fix two regressions in 16.12:
  * https://www.postgresql.org/docs/release/16.13/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1774872000">- Get rid of update-alternatives for openSUSE/SLE 16.0 and newer
  to support immutable systems and transactional updates.
  (jsc#PED-14824)</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1777550400">- bsc#1263804: After dropping update-alternatives we have to
  package /usr/bin/pg_config as an actual symlink, not %ghost.
- Fix spelling of build conditionals.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1778673600">- Update to version 16.13:
  * bsc#1265172, CVE-2026-6472: ensure the user has CREATE
    privilege on the schema specified
  * bsc#1265173, CVE-2026-6473: integer overflows in
    memory-allocation calculations
  * bsc#1265174, CVE-2026-6474: Guard against malicious time zone
    names
  * bsc#1265175, CVE-2026-6475: Prevent path traversal in
    pg_basebackup and pg_rewind
  * bsc#1265177, CVE-2026-6477: Mark PQfn() as unsafe, and avoid
    using it within libpq
  * bsc#1265178, CVE-2026-6478: Use timing-safe string comparisons
    in authentication code
  * bsc#1265179, CVE-2026-6479: Prevent unbounded recursion while
    processing startup packets
  * bsc#1265181, CVE-2026-6637: Prevent SQL injection and buffer
    overruns in contrib/spi
  * bsc#1265182, CVE-2026-6638: Properly quote object names in
    logical replication origin checks
  * https://www.postgresql.org/docs/release/16.13/</changelog>
</package>
<package pkgid="5c8389cc4412b289b733bf490148ddf14f5427753ea67975d89164eb35cac0e35a0531983271293fdfdc9b15329f120dbde98ef4219473e7e2f697d12ca04aad" name="postgresql16" arch="x86_64">
  <version epoch="0" ver="16.14" rel="80.2"/>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1726747200">- Don't build the libs and mini flavor anymore to hand over to
  PostgreSQL 17.</changelog>
  <changelog author="Antonio Teixeira &lt;antonio.teixeira@suse.com&gt;" date="1726833600">- Pull upstream patch to fix tests with timezone 2024b
  * postgresql-testsuite-timezone-fix.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1730808000">- Sync spec file from postgresql17.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1731499200">- Upgrade to 16.5:
  * CVE-2024-10976, bsc#1233323: Ensure cached plans are marked as
    dependent on the calling role when RLS applies to a
    non-top-level table reference.
  * CVE-2024-10977, bsc#1233325: Make libpq discard error messages
    received during SSL or GSS protocol negotiation.
  * CVE-2024-10978, bsc#1233326: Fix unintended interactions
    between SET SESSION AUTHORIZATION and SET ROLE
  * CVE-2024-10979, bsc#1233327: Prevent trusted PL/Perl code from
    changing environment variables.
  * obsoletes postgresql-testsuite-timezone-fix.patch
  * https://www.postgresql.org/about/news/p-2955/
  * https://www.postgresql.org/docs/release/16.5/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1732017600">- Upgrade to 16.6:
  * Repair ABI break for extensions that work with struct
    ResultRelInfo.
  * Restore functionality of ALTER {ROLE|DATABASE} SET role.
  * Fix cases where a logical replication slot's restart_lsn could
    go backwards.
  * Avoid deleting still-needed WAL files during pg_rewind.
  * Fix race conditions associated with dropping shared statistics
    entries.
  * Count index scans in contrib/bloom indexes in the statistics
    views, such as the pg_stat_user_indexes.idx_scan counter.
  * Fix crash when checking to see if an index's opclass options
    have changed.
  * Avoid assertion failure caused by disconnected NFA sub-graphs
    in regular expression parsing.
  * https://www.postgresql.org/about/news/p-2965/
  * https://www.postgresql.org/docs/release/16.6/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 16.7:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/16.7/
  * https://www.postgresql.org/about/news/-3015/
- Disable LLVM JIT on loongarch64</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 16.8:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/16.8/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 16.9:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/16.9/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to Fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Upgrade to 16.10:
  * https://www.postgresql.org/about/news/postgresql-176-1610-1514-1419-1322-and-18-beta-3-released-3118/
  * https://www.postgresql.org/docs/release/16.10/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1758628800">- Sync spec file from version 18.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Upgrade to 16.11:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/16.11/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 16.12:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/16.12/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 16.13 to fix two regressions in 16.12:
  * https://www.postgresql.org/docs/release/16.13/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1774872000">- Get rid of update-alternatives for openSUSE/SLE 16.0 and newer
  to support immutable systems and transactional updates.
  (jsc#PED-14824)</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1777550400">- bsc#1263804: After dropping update-alternatives we have to
  package /usr/bin/pg_config as an actual symlink, not %ghost.
- Fix spelling of build conditionals.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1778673600">- Update to version 16.13:
  * bsc#1265172, CVE-2026-6472: ensure the user has CREATE
    privilege on the schema specified
  * bsc#1265173, CVE-2026-6473: integer overflows in
    memory-allocation calculations
  * bsc#1265174, CVE-2026-6474: Guard against malicious time zone
    names
  * bsc#1265175, CVE-2026-6475: Prevent path traversal in
    pg_basebackup and pg_rewind
  * bsc#1265177, CVE-2026-6477: Mark PQfn() as unsafe, and avoid
    using it within libpq
  * bsc#1265178, CVE-2026-6478: Use timing-safe string comparisons
    in authentication code
  * bsc#1265179, CVE-2026-6479: Prevent unbounded recursion while
    processing startup packets
  * bsc#1265181, CVE-2026-6637: Prevent SQL injection and buffer
    overruns in contrib/spi
  * bsc#1265182, CVE-2026-6638: Properly quote object names in
    logical replication origin checks
  * https://www.postgresql.org/docs/release/16.13/</changelog>
</package>
<package pkgid="5939ba6bbc39a589d2f63a9caee9639c81d042a8e2edad85e09b38fbae4fa943e7cf2d5b33b3628a905b509cc2626a3a3e61459dc78e9cdd11870610b594c134" name="postgresql16-contrib" arch="aarch64">
  <version epoch="0" ver="16.13" rel="70.2"/>
  <changelog author="Aaron Puchert &lt;aaronpuchert@alice-dsl.net&gt;" date="1710244800">- Require LLVM &lt;= 17 for now, because LLVM 18 doesn't seem to work.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1715169600">- Upgrade to 16.3 (bsc#1224051):
  * bsc#1224038, CVE-2024-4317: Restrict visibility of pg_stats_ext
    and pg_stats_ext_exprs entries to the table owner. See the
    release notes for the steps that have to be taken to fix
    existing PostgreSQL instances.
  * Fix incompatibility with LLVM 18.
  * https://www.postgresql.org/docs/release/16.3/
- Prepare for PostgreSQL 17.
- Make sure all compilation and doc generation happens in %build.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1723291200">- Upgrade to 16.4 (bsc#1229013):
  * bsc#1229013, CVE-2024-7348 PostgreSQL relation replacement
    during pg_dump executes arbitrary SQL
  * https://www.postgresql.org/about/news/p-2910/
  * https://www.postgresql.org/docs/release/16.4/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1726747200">- Don't build the libs and mini flavor anymore to hand over to
  PostgreSQL 17.</changelog>
  <changelog author="Antonio Teixeira &lt;antonio.teixeira@suse.com&gt;" date="1726833600">- Pull upstream patch to fix tests with timezone 2024b
  * postgresql-testsuite-timezone-fix.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1730808000">- Sync spec file from postgresql17.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1731499200">- Upgrade to 16.5:
  * CVE-2024-10976, bsc#1233323: Ensure cached plans are marked as
    dependent on the calling role when RLS applies to a
    non-top-level table reference.
  * CVE-2024-10977, bsc#1233325: Make libpq discard error messages
    received during SSL or GSS protocol negotiation.
  * CVE-2024-10978, bsc#1233326: Fix unintended interactions
    between SET SESSION AUTHORIZATION and SET ROLE
  * CVE-2024-10979, bsc#1233327: Prevent trusted PL/Perl code from
    changing environment variables.
  * obsoletes postgresql-testsuite-timezone-fix.patch
  * https://www.postgresql.org/about/news/p-2955/
  * https://www.postgresql.org/docs/release/16.5/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1732017600">- Upgrade to 16.6:
  * Repair ABI break for extensions that work with struct
    ResultRelInfo.
  * Restore functionality of ALTER {ROLE|DATABASE} SET role.
  * Fix cases where a logical replication slot's restart_lsn could
    go backwards.
  * Avoid deleting still-needed WAL files during pg_rewind.
  * Fix race conditions associated with dropping shared statistics
    entries.
  * Count index scans in contrib/bloom indexes in the statistics
    views, such as the pg_stat_user_indexes.idx_scan counter.
  * Fix crash when checking to see if an index's opclass options
    have changed.
  * Avoid assertion failure caused by disconnected NFA sub-graphs
    in regular expression parsing.
  * https://www.postgresql.org/about/news/p-2965/
  * https://www.postgresql.org/docs/release/16.6/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 16.7:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/16.7/
  * https://www.postgresql.org/about/news/-3015/
- Disable LLVM JIT on loongarch64</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 16.8:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/16.8/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 16.9:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/16.9/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to Fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Upgrade to 16.10:
  * https://www.postgresql.org/about/news/postgresql-176-1610-1514-1419-1322-and-18-beta-3-released-3118/
  * https://www.postgresql.org/docs/release/16.10/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1758628800">- Sync spec file from version 18.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Upgrade to 16.11:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/16.11/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 16.12:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/16.12/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 16.13 to fix two regressions in 16.12:
  * https://www.postgresql.org/docs/release/16.13/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
</package>
<package pkgid="a14cb29c3c48c8ffad886643d3380ab9b1426c5c950558eb7981c13365888068d05a353b27f65928d5f50efebfa43de8184e6dd3459e817f44cf4c8e53c52af3" name="postgresql16-contrib" arch="ppc64le">
  <version epoch="0" ver="16.13" rel="70.2"/>
  <changelog author="Aaron Puchert &lt;aaronpuchert@alice-dsl.net&gt;" date="1710244800">- Require LLVM &lt;= 17 for now, because LLVM 18 doesn't seem to work.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1715169600">- Upgrade to 16.3 (bsc#1224051):
  * bsc#1224038, CVE-2024-4317: Restrict visibility of pg_stats_ext
    and pg_stats_ext_exprs entries to the table owner. See the
    release notes for the steps that have to be taken to fix
    existing PostgreSQL instances.
  * Fix incompatibility with LLVM 18.
  * https://www.postgresql.org/docs/release/16.3/
- Prepare for PostgreSQL 17.
- Make sure all compilation and doc generation happens in %build.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1723291200">- Upgrade to 16.4 (bsc#1229013):
  * bsc#1229013, CVE-2024-7348 PostgreSQL relation replacement
    during pg_dump executes arbitrary SQL
  * https://www.postgresql.org/about/news/p-2910/
  * https://www.postgresql.org/docs/release/16.4/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1726747200">- Don't build the libs and mini flavor anymore to hand over to
  PostgreSQL 17.</changelog>
  <changelog author="Antonio Teixeira &lt;antonio.teixeira@suse.com&gt;" date="1726833600">- Pull upstream patch to fix tests with timezone 2024b
  * postgresql-testsuite-timezone-fix.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1730808000">- Sync spec file from postgresql17.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1731499200">- Upgrade to 16.5:
  * CVE-2024-10976, bsc#1233323: Ensure cached plans are marked as
    dependent on the calling role when RLS applies to a
    non-top-level table reference.
  * CVE-2024-10977, bsc#1233325: Make libpq discard error messages
    received during SSL or GSS protocol negotiation.
  * CVE-2024-10978, bsc#1233326: Fix unintended interactions
    between SET SESSION AUTHORIZATION and SET ROLE
  * CVE-2024-10979, bsc#1233327: Prevent trusted PL/Perl code from
    changing environment variables.
  * obsoletes postgresql-testsuite-timezone-fix.patch
  * https://www.postgresql.org/about/news/p-2955/
  * https://www.postgresql.org/docs/release/16.5/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1732017600">- Upgrade to 16.6:
  * Repair ABI break for extensions that work with struct
    ResultRelInfo.
  * Restore functionality of ALTER {ROLE|DATABASE} SET role.
  * Fix cases where a logical replication slot's restart_lsn could
    go backwards.
  * Avoid deleting still-needed WAL files during pg_rewind.
  * Fix race conditions associated with dropping shared statistics
    entries.
  * Count index scans in contrib/bloom indexes in the statistics
    views, such as the pg_stat_user_indexes.idx_scan counter.
  * Fix crash when checking to see if an index's opclass options
    have changed.
  * Avoid assertion failure caused by disconnected NFA sub-graphs
    in regular expression parsing.
  * https://www.postgresql.org/about/news/p-2965/
  * https://www.postgresql.org/docs/release/16.6/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 16.7:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/16.7/
  * https://www.postgresql.org/about/news/-3015/
- Disable LLVM JIT on loongarch64</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 16.8:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/16.8/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 16.9:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/16.9/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to Fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Upgrade to 16.10:
  * https://www.postgresql.org/about/news/postgresql-176-1610-1514-1419-1322-and-18-beta-3-released-3118/
  * https://www.postgresql.org/docs/release/16.10/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1758628800">- Sync spec file from version 18.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Upgrade to 16.11:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/16.11/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 16.12:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/16.12/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 16.13 to fix two regressions in 16.12:
  * https://www.postgresql.org/docs/release/16.13/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
</package>
<package pkgid="0797c5edbf4df34dfcdc7b6afb85ad2a03fb4d6f9950e0837ec0088b36951089e3b1bc2f252c03cad7ab40e4bf1c89399583b523af25945ed12dcb16e30db972" name="postgresql16-contrib" arch="s390x">
  <version epoch="0" ver="16.13" rel="70.2"/>
  <changelog author="Aaron Puchert &lt;aaronpuchert@alice-dsl.net&gt;" date="1710244800">- Require LLVM &lt;= 17 for now, because LLVM 18 doesn't seem to work.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1715169600">- Upgrade to 16.3 (bsc#1224051):
  * bsc#1224038, CVE-2024-4317: Restrict visibility of pg_stats_ext
    and pg_stats_ext_exprs entries to the table owner. See the
    release notes for the steps that have to be taken to fix
    existing PostgreSQL instances.
  * Fix incompatibility with LLVM 18.
  * https://www.postgresql.org/docs/release/16.3/
- Prepare for PostgreSQL 17.
- Make sure all compilation and doc generation happens in %build.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1723291200">- Upgrade to 16.4 (bsc#1229013):
  * bsc#1229013, CVE-2024-7348 PostgreSQL relation replacement
    during pg_dump executes arbitrary SQL
  * https://www.postgresql.org/about/news/p-2910/
  * https://www.postgresql.org/docs/release/16.4/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1726747200">- Don't build the libs and mini flavor anymore to hand over to
  PostgreSQL 17.</changelog>
  <changelog author="Antonio Teixeira &lt;antonio.teixeira@suse.com&gt;" date="1726833600">- Pull upstream patch to fix tests with timezone 2024b
  * postgresql-testsuite-timezone-fix.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1730808000">- Sync spec file from postgresql17.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1731499200">- Upgrade to 16.5:
  * CVE-2024-10976, bsc#1233323: Ensure cached plans are marked as
    dependent on the calling role when RLS applies to a
    non-top-level table reference.
  * CVE-2024-10977, bsc#1233325: Make libpq discard error messages
    received during SSL or GSS protocol negotiation.
  * CVE-2024-10978, bsc#1233326: Fix unintended interactions
    between SET SESSION AUTHORIZATION and SET ROLE
  * CVE-2024-10979, bsc#1233327: Prevent trusted PL/Perl code from
    changing environment variables.
  * obsoletes postgresql-testsuite-timezone-fix.patch
  * https://www.postgresql.org/about/news/p-2955/
  * https://www.postgresql.org/docs/release/16.5/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1732017600">- Upgrade to 16.6:
  * Repair ABI break for extensions that work with struct
    ResultRelInfo.
  * Restore functionality of ALTER {ROLE|DATABASE} SET role.
  * Fix cases where a logical replication slot's restart_lsn could
    go backwards.
  * Avoid deleting still-needed WAL files during pg_rewind.
  * Fix race conditions associated with dropping shared statistics
    entries.
  * Count index scans in contrib/bloom indexes in the statistics
    views, such as the pg_stat_user_indexes.idx_scan counter.
  * Fix crash when checking to see if an index's opclass options
    have changed.
  * Avoid assertion failure caused by disconnected NFA sub-graphs
    in regular expression parsing.
  * https://www.postgresql.org/about/news/p-2965/
  * https://www.postgresql.org/docs/release/16.6/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 16.7:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/16.7/
  * https://www.postgresql.org/about/news/-3015/
- Disable LLVM JIT on loongarch64</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 16.8:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/16.8/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 16.9:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/16.9/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to Fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Upgrade to 16.10:
  * https://www.postgresql.org/about/news/postgresql-176-1610-1514-1419-1322-and-18-beta-3-released-3118/
  * https://www.postgresql.org/docs/release/16.10/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1758628800">- Sync spec file from version 18.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Upgrade to 16.11:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/16.11/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 16.12:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/16.12/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 16.13 to fix two regressions in 16.12:
  * https://www.postgresql.org/docs/release/16.13/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
</package>
<package pkgid="df1ef044454fddd29c9d993f568110f00e3cc8e033889d15aa52c9581054290ba853e86ac2bc9cd65111d122deb1cded57ccf621878a9450f3df5e17aa36b77e" name="postgresql16-contrib" arch="x86_64">
  <version epoch="0" ver="16.14" rel="80.2"/>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1726747200">- Don't build the libs and mini flavor anymore to hand over to
  PostgreSQL 17.</changelog>
  <changelog author="Antonio Teixeira &lt;antonio.teixeira@suse.com&gt;" date="1726833600">- Pull upstream patch to fix tests with timezone 2024b
  * postgresql-testsuite-timezone-fix.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1730808000">- Sync spec file from postgresql17.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1731499200">- Upgrade to 16.5:
  * CVE-2024-10976, bsc#1233323: Ensure cached plans are marked as
    dependent on the calling role when RLS applies to a
    non-top-level table reference.
  * CVE-2024-10977, bsc#1233325: Make libpq discard error messages
    received during SSL or GSS protocol negotiation.
  * CVE-2024-10978, bsc#1233326: Fix unintended interactions
    between SET SESSION AUTHORIZATION and SET ROLE
  * CVE-2024-10979, bsc#1233327: Prevent trusted PL/Perl code from
    changing environment variables.
  * obsoletes postgresql-testsuite-timezone-fix.patch
  * https://www.postgresql.org/about/news/p-2955/
  * https://www.postgresql.org/docs/release/16.5/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1732017600">- Upgrade to 16.6:
  * Repair ABI break for extensions that work with struct
    ResultRelInfo.
  * Restore functionality of ALTER {ROLE|DATABASE} SET role.
  * Fix cases where a logical replication slot's restart_lsn could
    go backwards.
  * Avoid deleting still-needed WAL files during pg_rewind.
  * Fix race conditions associated with dropping shared statistics
    entries.
  * Count index scans in contrib/bloom indexes in the statistics
    views, such as the pg_stat_user_indexes.idx_scan counter.
  * Fix crash when checking to see if an index's opclass options
    have changed.
  * Avoid assertion failure caused by disconnected NFA sub-graphs
    in regular expression parsing.
  * https://www.postgresql.org/about/news/p-2965/
  * https://www.postgresql.org/docs/release/16.6/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 16.7:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/16.7/
  * https://www.postgresql.org/about/news/-3015/
- Disable LLVM JIT on loongarch64</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 16.8:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/16.8/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 16.9:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/16.9/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to Fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Upgrade to 16.10:
  * https://www.postgresql.org/about/news/postgresql-176-1610-1514-1419-1322-and-18-beta-3-released-3118/
  * https://www.postgresql.org/docs/release/16.10/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1758628800">- Sync spec file from version 18.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Upgrade to 16.11:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/16.11/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 16.12:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/16.12/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 16.13 to fix two regressions in 16.12:
  * https://www.postgresql.org/docs/release/16.13/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1774872000">- Get rid of update-alternatives for openSUSE/SLE 16.0 and newer
  to support immutable systems and transactional updates.
  (jsc#PED-14824)</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1777550400">- bsc#1263804: After dropping update-alternatives we have to
  package /usr/bin/pg_config as an actual symlink, not %ghost.
- Fix spelling of build conditionals.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1778673600">- Update to version 16.13:
  * bsc#1265172, CVE-2026-6472: ensure the user has CREATE
    privilege on the schema specified
  * bsc#1265173, CVE-2026-6473: integer overflows in
    memory-allocation calculations
  * bsc#1265174, CVE-2026-6474: Guard against malicious time zone
    names
  * bsc#1265175, CVE-2026-6475: Prevent path traversal in
    pg_basebackup and pg_rewind
  * bsc#1265177, CVE-2026-6477: Mark PQfn() as unsafe, and avoid
    using it within libpq
  * bsc#1265178, CVE-2026-6478: Use timing-safe string comparisons
    in authentication code
  * bsc#1265179, CVE-2026-6479: Prevent unbounded recursion while
    processing startup packets
  * bsc#1265181, CVE-2026-6637: Prevent SQL injection and buffer
    overruns in contrib/spi
  * bsc#1265182, CVE-2026-6638: Properly quote object names in
    logical replication origin checks
  * https://www.postgresql.org/docs/release/16.13/</changelog>
</package>
<package pkgid="b174dc85f31ae03a4b686cb70be2a8e4dcb0f1f7a50eb43be2b3fda0e8d7986babe67a0e29ac80c4cd92d25de0211d75d6c3e1b1be6aa6b03110459d8de11d23" name="postgresql16-devel" arch="aarch64">
  <version epoch="0" ver="16.13" rel="70.2"/>
  <changelog author="Aaron Puchert &lt;aaronpuchert@alice-dsl.net&gt;" date="1710244800">- Require LLVM &lt;= 17 for now, because LLVM 18 doesn't seem to work.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1715169600">- Upgrade to 16.3 (bsc#1224051):
  * bsc#1224038, CVE-2024-4317: Restrict visibility of pg_stats_ext
    and pg_stats_ext_exprs entries to the table owner. See the
    release notes for the steps that have to be taken to fix
    existing PostgreSQL instances.
  * Fix incompatibility with LLVM 18.
  * https://www.postgresql.org/docs/release/16.3/
- Prepare for PostgreSQL 17.
- Make sure all compilation and doc generation happens in %build.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1723291200">- Upgrade to 16.4 (bsc#1229013):
  * bsc#1229013, CVE-2024-7348 PostgreSQL relation replacement
    during pg_dump executes arbitrary SQL
  * https://www.postgresql.org/about/news/p-2910/
  * https://www.postgresql.org/docs/release/16.4/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1726747200">- Don't build the libs and mini flavor anymore to hand over to
  PostgreSQL 17.</changelog>
  <changelog author="Antonio Teixeira &lt;antonio.teixeira@suse.com&gt;" date="1726833600">- Pull upstream patch to fix tests with timezone 2024b
  * postgresql-testsuite-timezone-fix.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1730808000">- Sync spec file from postgresql17.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1731499200">- Upgrade to 16.5:
  * CVE-2024-10976, bsc#1233323: Ensure cached plans are marked as
    dependent on the calling role when RLS applies to a
    non-top-level table reference.
  * CVE-2024-10977, bsc#1233325: Make libpq discard error messages
    received during SSL or GSS protocol negotiation.
  * CVE-2024-10978, bsc#1233326: Fix unintended interactions
    between SET SESSION AUTHORIZATION and SET ROLE
  * CVE-2024-10979, bsc#1233327: Prevent trusted PL/Perl code from
    changing environment variables.
  * obsoletes postgresql-testsuite-timezone-fix.patch
  * https://www.postgresql.org/about/news/p-2955/
  * https://www.postgresql.org/docs/release/16.5/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1732017600">- Upgrade to 16.6:
  * Repair ABI break for extensions that work with struct
    ResultRelInfo.
  * Restore functionality of ALTER {ROLE|DATABASE} SET role.
  * Fix cases where a logical replication slot's restart_lsn could
    go backwards.
  * Avoid deleting still-needed WAL files during pg_rewind.
  * Fix race conditions associated with dropping shared statistics
    entries.
  * Count index scans in contrib/bloom indexes in the statistics
    views, such as the pg_stat_user_indexes.idx_scan counter.
  * Fix crash when checking to see if an index's opclass options
    have changed.
  * Avoid assertion failure caused by disconnected NFA sub-graphs
    in regular expression parsing.
  * https://www.postgresql.org/about/news/p-2965/
  * https://www.postgresql.org/docs/release/16.6/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 16.7:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/16.7/
  * https://www.postgresql.org/about/news/-3015/
- Disable LLVM JIT on loongarch64</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 16.8:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/16.8/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 16.9:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/16.9/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to Fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Upgrade to 16.10:
  * https://www.postgresql.org/about/news/postgresql-176-1610-1514-1419-1322-and-18-beta-3-released-3118/
  * https://www.postgresql.org/docs/release/16.10/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1758628800">- Sync spec file from version 18.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Upgrade to 16.11:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/16.11/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 16.12:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/16.12/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 16.13 to fix two regressions in 16.12:
  * https://www.postgresql.org/docs/release/16.13/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
</package>
<package pkgid="00d68ee09fc38d616e946170078286e491e1cae35eaa673c8fbb80bae439b5eb9809edb54fd0da01e724b1c1b08b810e73d05456c77f7db244b61f5775c50a22" name="postgresql16-devel" arch="ppc64le">
  <version epoch="0" ver="16.13" rel="70.2"/>
  <changelog author="Aaron Puchert &lt;aaronpuchert@alice-dsl.net&gt;" date="1710244800">- Require LLVM &lt;= 17 for now, because LLVM 18 doesn't seem to work.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1715169600">- Upgrade to 16.3 (bsc#1224051):
  * bsc#1224038, CVE-2024-4317: Restrict visibility of pg_stats_ext
    and pg_stats_ext_exprs entries to the table owner. See the
    release notes for the steps that have to be taken to fix
    existing PostgreSQL instances.
  * Fix incompatibility with LLVM 18.
  * https://www.postgresql.org/docs/release/16.3/
- Prepare for PostgreSQL 17.
- Make sure all compilation and doc generation happens in %build.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1723291200">- Upgrade to 16.4 (bsc#1229013):
  * bsc#1229013, CVE-2024-7348 PostgreSQL relation replacement
    during pg_dump executes arbitrary SQL
  * https://www.postgresql.org/about/news/p-2910/
  * https://www.postgresql.org/docs/release/16.4/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1726747200">- Don't build the libs and mini flavor anymore to hand over to
  PostgreSQL 17.</changelog>
  <changelog author="Antonio Teixeira &lt;antonio.teixeira@suse.com&gt;" date="1726833600">- Pull upstream patch to fix tests with timezone 2024b
  * postgresql-testsuite-timezone-fix.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1730808000">- Sync spec file from postgresql17.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1731499200">- Upgrade to 16.5:
  * CVE-2024-10976, bsc#1233323: Ensure cached plans are marked as
    dependent on the calling role when RLS applies to a
    non-top-level table reference.
  * CVE-2024-10977, bsc#1233325: Make libpq discard error messages
    received during SSL or GSS protocol negotiation.
  * CVE-2024-10978, bsc#1233326: Fix unintended interactions
    between SET SESSION AUTHORIZATION and SET ROLE
  * CVE-2024-10979, bsc#1233327: Prevent trusted PL/Perl code from
    changing environment variables.
  * obsoletes postgresql-testsuite-timezone-fix.patch
  * https://www.postgresql.org/about/news/p-2955/
  * https://www.postgresql.org/docs/release/16.5/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1732017600">- Upgrade to 16.6:
  * Repair ABI break for extensions that work with struct
    ResultRelInfo.
  * Restore functionality of ALTER {ROLE|DATABASE} SET role.
  * Fix cases where a logical replication slot's restart_lsn could
    go backwards.
  * Avoid deleting still-needed WAL files during pg_rewind.
  * Fix race conditions associated with dropping shared statistics
    entries.
  * Count index scans in contrib/bloom indexes in the statistics
    views, such as the pg_stat_user_indexes.idx_scan counter.
  * Fix crash when checking to see if an index's opclass options
    have changed.
  * Avoid assertion failure caused by disconnected NFA sub-graphs
    in regular expression parsing.
  * https://www.postgresql.org/about/news/p-2965/
  * https://www.postgresql.org/docs/release/16.6/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 16.7:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/16.7/
  * https://www.postgresql.org/about/news/-3015/
- Disable LLVM JIT on loongarch64</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 16.8:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/16.8/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 16.9:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/16.9/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to Fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Upgrade to 16.10:
  * https://www.postgresql.org/about/news/postgresql-176-1610-1514-1419-1322-and-18-beta-3-released-3118/
  * https://www.postgresql.org/docs/release/16.10/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1758628800">- Sync spec file from version 18.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Upgrade to 16.11:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/16.11/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 16.12:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/16.12/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 16.13 to fix two regressions in 16.12:
  * https://www.postgresql.org/docs/release/16.13/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
</package>
<package pkgid="73a8b3567140f703347348c710824096fb0c1c0f2ac93f7ecf23236253f8dc5790f280dccb5952373c32f16a8e2e1b2905421a492fb1cf728d1fe1cafe24df50" name="postgresql16-devel" arch="s390x">
  <version epoch="0" ver="16.13" rel="70.2"/>
  <changelog author="Aaron Puchert &lt;aaronpuchert@alice-dsl.net&gt;" date="1710244800">- Require LLVM &lt;= 17 for now, because LLVM 18 doesn't seem to work.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1715169600">- Upgrade to 16.3 (bsc#1224051):
  * bsc#1224038, CVE-2024-4317: Restrict visibility of pg_stats_ext
    and pg_stats_ext_exprs entries to the table owner. See the
    release notes for the steps that have to be taken to fix
    existing PostgreSQL instances.
  * Fix incompatibility with LLVM 18.
  * https://www.postgresql.org/docs/release/16.3/
- Prepare for PostgreSQL 17.
- Make sure all compilation and doc generation happens in %build.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1723291200">- Upgrade to 16.4 (bsc#1229013):
  * bsc#1229013, CVE-2024-7348 PostgreSQL relation replacement
    during pg_dump executes arbitrary SQL
  * https://www.postgresql.org/about/news/p-2910/
  * https://www.postgresql.org/docs/release/16.4/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1726747200">- Don't build the libs and mini flavor anymore to hand over to
  PostgreSQL 17.</changelog>
  <changelog author="Antonio Teixeira &lt;antonio.teixeira@suse.com&gt;" date="1726833600">- Pull upstream patch to fix tests with timezone 2024b
  * postgresql-testsuite-timezone-fix.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1730808000">- Sync spec file from postgresql17.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1731499200">- Upgrade to 16.5:
  * CVE-2024-10976, bsc#1233323: Ensure cached plans are marked as
    dependent on the calling role when RLS applies to a
    non-top-level table reference.
  * CVE-2024-10977, bsc#1233325: Make libpq discard error messages
    received during SSL or GSS protocol negotiation.
  * CVE-2024-10978, bsc#1233326: Fix unintended interactions
    between SET SESSION AUTHORIZATION and SET ROLE
  * CVE-2024-10979, bsc#1233327: Prevent trusted PL/Perl code from
    changing environment variables.
  * obsoletes postgresql-testsuite-timezone-fix.patch
  * https://www.postgresql.org/about/news/p-2955/
  * https://www.postgresql.org/docs/release/16.5/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1732017600">- Upgrade to 16.6:
  * Repair ABI break for extensions that work with struct
    ResultRelInfo.
  * Restore functionality of ALTER {ROLE|DATABASE} SET role.
  * Fix cases where a logical replication slot's restart_lsn could
    go backwards.
  * Avoid deleting still-needed WAL files during pg_rewind.
  * Fix race conditions associated with dropping shared statistics
    entries.
  * Count index scans in contrib/bloom indexes in the statistics
    views, such as the pg_stat_user_indexes.idx_scan counter.
  * Fix crash when checking to see if an index's opclass options
    have changed.
  * Avoid assertion failure caused by disconnected NFA sub-graphs
    in regular expression parsing.
  * https://www.postgresql.org/about/news/p-2965/
  * https://www.postgresql.org/docs/release/16.6/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 16.7:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/16.7/
  * https://www.postgresql.org/about/news/-3015/
- Disable LLVM JIT on loongarch64</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 16.8:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/16.8/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 16.9:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/16.9/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to Fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Upgrade to 16.10:
  * https://www.postgresql.org/about/news/postgresql-176-1610-1514-1419-1322-and-18-beta-3-released-3118/
  * https://www.postgresql.org/docs/release/16.10/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1758628800">- Sync spec file from version 18.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Upgrade to 16.11:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/16.11/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 16.12:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/16.12/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 16.13 to fix two regressions in 16.12:
  * https://www.postgresql.org/docs/release/16.13/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
</package>
<package pkgid="46364704290af18c341985135d7c2e954f9bf2e3467a6c46c93658cf78dff022b642925e09d1a0cc7fb079abdc96cfa0282e5885d9634ee3e322c04a1ad638a6" name="postgresql16-devel" arch="x86_64">
  <version epoch="0" ver="16.14" rel="80.2"/>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1726747200">- Don't build the libs and mini flavor anymore to hand over to
  PostgreSQL 17.</changelog>
  <changelog author="Antonio Teixeira &lt;antonio.teixeira@suse.com&gt;" date="1726833600">- Pull upstream patch to fix tests with timezone 2024b
  * postgresql-testsuite-timezone-fix.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1730808000">- Sync spec file from postgresql17.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1731499200">- Upgrade to 16.5:
  * CVE-2024-10976, bsc#1233323: Ensure cached plans are marked as
    dependent on the calling role when RLS applies to a
    non-top-level table reference.
  * CVE-2024-10977, bsc#1233325: Make libpq discard error messages
    received during SSL or GSS protocol negotiation.
  * CVE-2024-10978, bsc#1233326: Fix unintended interactions
    between SET SESSION AUTHORIZATION and SET ROLE
  * CVE-2024-10979, bsc#1233327: Prevent trusted PL/Perl code from
    changing environment variables.
  * obsoletes postgresql-testsuite-timezone-fix.patch
  * https://www.postgresql.org/about/news/p-2955/
  * https://www.postgresql.org/docs/release/16.5/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1732017600">- Upgrade to 16.6:
  * Repair ABI break for extensions that work with struct
    ResultRelInfo.
  * Restore functionality of ALTER {ROLE|DATABASE} SET role.
  * Fix cases where a logical replication slot's restart_lsn could
    go backwards.
  * Avoid deleting still-needed WAL files during pg_rewind.
  * Fix race conditions associated with dropping shared statistics
    entries.
  * Count index scans in contrib/bloom indexes in the statistics
    views, such as the pg_stat_user_indexes.idx_scan counter.
  * Fix crash when checking to see if an index's opclass options
    have changed.
  * Avoid assertion failure caused by disconnected NFA sub-graphs
    in regular expression parsing.
  * https://www.postgresql.org/about/news/p-2965/
  * https://www.postgresql.org/docs/release/16.6/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 16.7:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/16.7/
  * https://www.postgresql.org/about/news/-3015/
- Disable LLVM JIT on loongarch64</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 16.8:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/16.8/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 16.9:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/16.9/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to Fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Upgrade to 16.10:
  * https://www.postgresql.org/about/news/postgresql-176-1610-1514-1419-1322-and-18-beta-3-released-3118/
  * https://www.postgresql.org/docs/release/16.10/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1758628800">- Sync spec file from version 18.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Upgrade to 16.11:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/16.11/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 16.12:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/16.12/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 16.13 to fix two regressions in 16.12:
  * https://www.postgresql.org/docs/release/16.13/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1774872000">- Get rid of update-alternatives for openSUSE/SLE 16.0 and newer
  to support immutable systems and transactional updates.
  (jsc#PED-14824)</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1777550400">- bsc#1263804: After dropping update-alternatives we have to
  package /usr/bin/pg_config as an actual symlink, not %ghost.
- Fix spelling of build conditionals.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1778673600">- Update to version 16.13:
  * bsc#1265172, CVE-2026-6472: ensure the user has CREATE
    privilege on the schema specified
  * bsc#1265173, CVE-2026-6473: integer overflows in
    memory-allocation calculations
  * bsc#1265174, CVE-2026-6474: Guard against malicious time zone
    names
  * bsc#1265175, CVE-2026-6475: Prevent path traversal in
    pg_basebackup and pg_rewind
  * bsc#1265177, CVE-2026-6477: Mark PQfn() as unsafe, and avoid
    using it within libpq
  * bsc#1265178, CVE-2026-6478: Use timing-safe string comparisons
    in authentication code
  * bsc#1265179, CVE-2026-6479: Prevent unbounded recursion while
    processing startup packets
  * bsc#1265181, CVE-2026-6637: Prevent SQL injection and buffer
    overruns in contrib/spi
  * bsc#1265182, CVE-2026-6638: Properly quote object names in
    logical replication origin checks
  * https://www.postgresql.org/docs/release/16.13/</changelog>
</package>
<package pkgid="0c3e76d17c3b193749c34250bc78a90806cd31b6f7752ecfbb9dd39bc5434c437388eb4841f123bd7db41445162f5f4028c83fe3d287c5ad34c021e5baddfa24" name="postgresql16-docs" arch="noarch">
  <version epoch="0" ver="16.13" rel="70.2"/>
  <changelog author="Aaron Puchert &lt;aaronpuchert@alice-dsl.net&gt;" date="1710244800">- Require LLVM &lt;= 17 for now, because LLVM 18 doesn't seem to work.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1715169600">- Upgrade to 16.3 (bsc#1224051):
  * bsc#1224038, CVE-2024-4317: Restrict visibility of pg_stats_ext
    and pg_stats_ext_exprs entries to the table owner. See the
    release notes for the steps that have to be taken to fix
    existing PostgreSQL instances.
  * Fix incompatibility with LLVM 18.
  * https://www.postgresql.org/docs/release/16.3/
- Prepare for PostgreSQL 17.
- Make sure all compilation and doc generation happens in %build.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1723291200">- Upgrade to 16.4 (bsc#1229013):
  * bsc#1229013, CVE-2024-7348 PostgreSQL relation replacement
    during pg_dump executes arbitrary SQL
  * https://www.postgresql.org/about/news/p-2910/
  * https://www.postgresql.org/docs/release/16.4/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1726747200">- Don't build the libs and mini flavor anymore to hand over to
  PostgreSQL 17.</changelog>
  <changelog author="Antonio Teixeira &lt;antonio.teixeira@suse.com&gt;" date="1726833600">- Pull upstream patch to fix tests with timezone 2024b
  * postgresql-testsuite-timezone-fix.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1730808000">- Sync spec file from postgresql17.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1731499200">- Upgrade to 16.5:
  * CVE-2024-10976, bsc#1233323: Ensure cached plans are marked as
    dependent on the calling role when RLS applies to a
    non-top-level table reference.
  * CVE-2024-10977, bsc#1233325: Make libpq discard error messages
    received during SSL or GSS protocol negotiation.
  * CVE-2024-10978, bsc#1233326: Fix unintended interactions
    between SET SESSION AUTHORIZATION and SET ROLE
  * CVE-2024-10979, bsc#1233327: Prevent trusted PL/Perl code from
    changing environment variables.
  * obsoletes postgresql-testsuite-timezone-fix.patch
  * https://www.postgresql.org/about/news/p-2955/
  * https://www.postgresql.org/docs/release/16.5/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1732017600">- Upgrade to 16.6:
  * Repair ABI break for extensions that work with struct
    ResultRelInfo.
  * Restore functionality of ALTER {ROLE|DATABASE} SET role.
  * Fix cases where a logical replication slot's restart_lsn could
    go backwards.
  * Avoid deleting still-needed WAL files during pg_rewind.
  * Fix race conditions associated with dropping shared statistics
    entries.
  * Count index scans in contrib/bloom indexes in the statistics
    views, such as the pg_stat_user_indexes.idx_scan counter.
  * Fix crash when checking to see if an index's opclass options
    have changed.
  * Avoid assertion failure caused by disconnected NFA sub-graphs
    in regular expression parsing.
  * https://www.postgresql.org/about/news/p-2965/
  * https://www.postgresql.org/docs/release/16.6/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 16.7:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/16.7/
  * https://www.postgresql.org/about/news/-3015/
- Disable LLVM JIT on loongarch64</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 16.8:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/16.8/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 16.9:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/16.9/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to Fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Upgrade to 16.10:
  * https://www.postgresql.org/about/news/postgresql-176-1610-1514-1419-1322-and-18-beta-3-released-3118/
  * https://www.postgresql.org/docs/release/16.10/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1758628800">- Sync spec file from version 18.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Upgrade to 16.11:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/16.11/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 16.12:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/16.12/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 16.13 to fix two regressions in 16.12:
  * https://www.postgresql.org/docs/release/16.13/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
</package>
<package pkgid="7ae674be90e22ec9ef6e627d21225af9b76c034415ea236cbe32628a5e3c9d1d08c9dbb00bcbf73ffcf59ea56b29fac8eba526c791a793a117786439ce448877" name="postgresql16-docs" arch="noarch">
  <version epoch="0" ver="16.14" rel="80.2"/>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1726747200">- Don't build the libs and mini flavor anymore to hand over to
  PostgreSQL 17.</changelog>
  <changelog author="Antonio Teixeira &lt;antonio.teixeira@suse.com&gt;" date="1726833600">- Pull upstream patch to fix tests with timezone 2024b
  * postgresql-testsuite-timezone-fix.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1730808000">- Sync spec file from postgresql17.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1731499200">- Upgrade to 16.5:
  * CVE-2024-10976, bsc#1233323: Ensure cached plans are marked as
    dependent on the calling role when RLS applies to a
    non-top-level table reference.
  * CVE-2024-10977, bsc#1233325: Make libpq discard error messages
    received during SSL or GSS protocol negotiation.
  * CVE-2024-10978, bsc#1233326: Fix unintended interactions
    between SET SESSION AUTHORIZATION and SET ROLE
  * CVE-2024-10979, bsc#1233327: Prevent trusted PL/Perl code from
    changing environment variables.
  * obsoletes postgresql-testsuite-timezone-fix.patch
  * https://www.postgresql.org/about/news/p-2955/
  * https://www.postgresql.org/docs/release/16.5/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1732017600">- Upgrade to 16.6:
  * Repair ABI break for extensions that work with struct
    ResultRelInfo.
  * Restore functionality of ALTER {ROLE|DATABASE} SET role.
  * Fix cases where a logical replication slot's restart_lsn could
    go backwards.
  * Avoid deleting still-needed WAL files during pg_rewind.
  * Fix race conditions associated with dropping shared statistics
    entries.
  * Count index scans in contrib/bloom indexes in the statistics
    views, such as the pg_stat_user_indexes.idx_scan counter.
  * Fix crash when checking to see if an index's opclass options
    have changed.
  * Avoid assertion failure caused by disconnected NFA sub-graphs
    in regular expression parsing.
  * https://www.postgresql.org/about/news/p-2965/
  * https://www.postgresql.org/docs/release/16.6/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 16.7:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/16.7/
  * https://www.postgresql.org/about/news/-3015/
- Disable LLVM JIT on loongarch64</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 16.8:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/16.8/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 16.9:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/16.9/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to Fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Upgrade to 16.10:
  * https://www.postgresql.org/about/news/postgresql-176-1610-1514-1419-1322-and-18-beta-3-released-3118/
  * https://www.postgresql.org/docs/release/16.10/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1758628800">- Sync spec file from version 18.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Upgrade to 16.11:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/16.11/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 16.12:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/16.12/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 16.13 to fix two regressions in 16.12:
  * https://www.postgresql.org/docs/release/16.13/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1774872000">- Get rid of update-alternatives for openSUSE/SLE 16.0 and newer
  to support immutable systems and transactional updates.
  (jsc#PED-14824)</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1777550400">- bsc#1263804: After dropping update-alternatives we have to
  package /usr/bin/pg_config as an actual symlink, not %ghost.
- Fix spelling of build conditionals.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1778673600">- Update to version 16.13:
  * bsc#1265172, CVE-2026-6472: ensure the user has CREATE
    privilege on the schema specified
  * bsc#1265173, CVE-2026-6473: integer overflows in
    memory-allocation calculations
  * bsc#1265174, CVE-2026-6474: Guard against malicious time zone
    names
  * bsc#1265175, CVE-2026-6475: Prevent path traversal in
    pg_basebackup and pg_rewind
  * bsc#1265177, CVE-2026-6477: Mark PQfn() as unsafe, and avoid
    using it within libpq
  * bsc#1265178, CVE-2026-6478: Use timing-safe string comparisons
    in authentication code
  * bsc#1265179, CVE-2026-6479: Prevent unbounded recursion while
    processing startup packets
  * bsc#1265181, CVE-2026-6637: Prevent SQL injection and buffer
    overruns in contrib/spi
  * bsc#1265182, CVE-2026-6638: Properly quote object names in
    logical replication origin checks
  * https://www.postgresql.org/docs/release/16.13/</changelog>
</package>
<package pkgid="2b2208abb7abadf8661c91509bddc26ff19aa13d41d276d3314c191ec5c9ce07a7fe4c9aa42a80cabe6d55fd20d3484425fcca457ebdcdfd66360ce5f2852f05" name="postgresql16-llvmjit" arch="aarch64">
  <version epoch="0" ver="16.13" rel="70.2"/>
  <changelog author="Aaron Puchert &lt;aaronpuchert@alice-dsl.net&gt;" date="1710244800">- Require LLVM &lt;= 17 for now, because LLVM 18 doesn't seem to work.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1715169600">- Upgrade to 16.3 (bsc#1224051):
  * bsc#1224038, CVE-2024-4317: Restrict visibility of pg_stats_ext
    and pg_stats_ext_exprs entries to the table owner. See the
    release notes for the steps that have to be taken to fix
    existing PostgreSQL instances.
  * Fix incompatibility with LLVM 18.
  * https://www.postgresql.org/docs/release/16.3/
- Prepare for PostgreSQL 17.
- Make sure all compilation and doc generation happens in %build.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1723291200">- Upgrade to 16.4 (bsc#1229013):
  * bsc#1229013, CVE-2024-7348 PostgreSQL relation replacement
    during pg_dump executes arbitrary SQL
  * https://www.postgresql.org/about/news/p-2910/
  * https://www.postgresql.org/docs/release/16.4/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1726747200">- Don't build the libs and mini flavor anymore to hand over to
  PostgreSQL 17.</changelog>
  <changelog author="Antonio Teixeira &lt;antonio.teixeira@suse.com&gt;" date="1726833600">- Pull upstream patch to fix tests with timezone 2024b
  * postgresql-testsuite-timezone-fix.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1730808000">- Sync spec file from postgresql17.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1731499200">- Upgrade to 16.5:
  * CVE-2024-10976, bsc#1233323: Ensure cached plans are marked as
    dependent on the calling role when RLS applies to a
    non-top-level table reference.
  * CVE-2024-10977, bsc#1233325: Make libpq discard error messages
    received during SSL or GSS protocol negotiation.
  * CVE-2024-10978, bsc#1233326: Fix unintended interactions
    between SET SESSION AUTHORIZATION and SET ROLE
  * CVE-2024-10979, bsc#1233327: Prevent trusted PL/Perl code from
    changing environment variables.
  * obsoletes postgresql-testsuite-timezone-fix.patch
  * https://www.postgresql.org/about/news/p-2955/
  * https://www.postgresql.org/docs/release/16.5/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1732017600">- Upgrade to 16.6:
  * Repair ABI break for extensions that work with struct
    ResultRelInfo.
  * Restore functionality of ALTER {ROLE|DATABASE} SET role.
  * Fix cases where a logical replication slot's restart_lsn could
    go backwards.
  * Avoid deleting still-needed WAL files during pg_rewind.
  * Fix race conditions associated with dropping shared statistics
    entries.
  * Count index scans in contrib/bloom indexes in the statistics
    views, such as the pg_stat_user_indexes.idx_scan counter.
  * Fix crash when checking to see if an index's opclass options
    have changed.
  * Avoid assertion failure caused by disconnected NFA sub-graphs
    in regular expression parsing.
  * https://www.postgresql.org/about/news/p-2965/
  * https://www.postgresql.org/docs/release/16.6/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 16.7:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/16.7/
  * https://www.postgresql.org/about/news/-3015/
- Disable LLVM JIT on loongarch64</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 16.8:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/16.8/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 16.9:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/16.9/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to Fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Upgrade to 16.10:
  * https://www.postgresql.org/about/news/postgresql-176-1610-1514-1419-1322-and-18-beta-3-released-3118/
  * https://www.postgresql.org/docs/release/16.10/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1758628800">- Sync spec file from version 18.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Upgrade to 16.11:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/16.11/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 16.12:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/16.12/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 16.13 to fix two regressions in 16.12:
  * https://www.postgresql.org/docs/release/16.13/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
</package>
<package pkgid="658c087318aa087b793f23484ee64962fef703905f5cd968b51553bfd8df2b2ab0c417f9431e0ee5ef9e3d7d2cb9587f1d1a4683d5a88b57dd0a22437e651463" name="postgresql16-llvmjit" arch="ppc64le">
  <version epoch="0" ver="16.13" rel="70.2"/>
  <changelog author="Aaron Puchert &lt;aaronpuchert@alice-dsl.net&gt;" date="1710244800">- Require LLVM &lt;= 17 for now, because LLVM 18 doesn't seem to work.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1715169600">- Upgrade to 16.3 (bsc#1224051):
  * bsc#1224038, CVE-2024-4317: Restrict visibility of pg_stats_ext
    and pg_stats_ext_exprs entries to the table owner. See the
    release notes for the steps that have to be taken to fix
    existing PostgreSQL instances.
  * Fix incompatibility with LLVM 18.
  * https://www.postgresql.org/docs/release/16.3/
- Prepare for PostgreSQL 17.
- Make sure all compilation and doc generation happens in %build.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1723291200">- Upgrade to 16.4 (bsc#1229013):
  * bsc#1229013, CVE-2024-7348 PostgreSQL relation replacement
    during pg_dump executes arbitrary SQL
  * https://www.postgresql.org/about/news/p-2910/
  * https://www.postgresql.org/docs/release/16.4/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1726747200">- Don't build the libs and mini flavor anymore to hand over to
  PostgreSQL 17.</changelog>
  <changelog author="Antonio Teixeira &lt;antonio.teixeira@suse.com&gt;" date="1726833600">- Pull upstream patch to fix tests with timezone 2024b
  * postgresql-testsuite-timezone-fix.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1730808000">- Sync spec file from postgresql17.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1731499200">- Upgrade to 16.5:
  * CVE-2024-10976, bsc#1233323: Ensure cached plans are marked as
    dependent on the calling role when RLS applies to a
    non-top-level table reference.
  * CVE-2024-10977, bsc#1233325: Make libpq discard error messages
    received during SSL or GSS protocol negotiation.
  * CVE-2024-10978, bsc#1233326: Fix unintended interactions
    between SET SESSION AUTHORIZATION and SET ROLE
  * CVE-2024-10979, bsc#1233327: Prevent trusted PL/Perl code from
    changing environment variables.
  * obsoletes postgresql-testsuite-timezone-fix.patch
  * https://www.postgresql.org/about/news/p-2955/
  * https://www.postgresql.org/docs/release/16.5/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1732017600">- Upgrade to 16.6:
  * Repair ABI break for extensions that work with struct
    ResultRelInfo.
  * Restore functionality of ALTER {ROLE|DATABASE} SET role.
  * Fix cases where a logical replication slot's restart_lsn could
    go backwards.
  * Avoid deleting still-needed WAL files during pg_rewind.
  * Fix race conditions associated with dropping shared statistics
    entries.
  * Count index scans in contrib/bloom indexes in the statistics
    views, such as the pg_stat_user_indexes.idx_scan counter.
  * Fix crash when checking to see if an index's opclass options
    have changed.
  * Avoid assertion failure caused by disconnected NFA sub-graphs
    in regular expression parsing.
  * https://www.postgresql.org/about/news/p-2965/
  * https://www.postgresql.org/docs/release/16.6/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 16.7:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/16.7/
  * https://www.postgresql.org/about/news/-3015/
- Disable LLVM JIT on loongarch64</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 16.8:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/16.8/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 16.9:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/16.9/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to Fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Upgrade to 16.10:
  * https://www.postgresql.org/about/news/postgresql-176-1610-1514-1419-1322-and-18-beta-3-released-3118/
  * https://www.postgresql.org/docs/release/16.10/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1758628800">- Sync spec file from version 18.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Upgrade to 16.11:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/16.11/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 16.12:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/16.12/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 16.13 to fix two regressions in 16.12:
  * https://www.postgresql.org/docs/release/16.13/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
</package>
<package pkgid="bcecc788f11d7170a1d4417a75dc0811655cdef72162638056419d3beaa0498c31562a55a5a631c23dfeb440f18b869033fd0dab900916dbe172cae125b30c70" name="postgresql16-llvmjit" arch="s390x">
  <version epoch="0" ver="16.13" rel="70.2"/>
  <changelog author="Aaron Puchert &lt;aaronpuchert@alice-dsl.net&gt;" date="1710244800">- Require LLVM &lt;= 17 for now, because LLVM 18 doesn't seem to work.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1715169600">- Upgrade to 16.3 (bsc#1224051):
  * bsc#1224038, CVE-2024-4317: Restrict visibility of pg_stats_ext
    and pg_stats_ext_exprs entries to the table owner. See the
    release notes for the steps that have to be taken to fix
    existing PostgreSQL instances.
  * Fix incompatibility with LLVM 18.
  * https://www.postgresql.org/docs/release/16.3/
- Prepare for PostgreSQL 17.
- Make sure all compilation and doc generation happens in %build.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1723291200">- Upgrade to 16.4 (bsc#1229013):
  * bsc#1229013, CVE-2024-7348 PostgreSQL relation replacement
    during pg_dump executes arbitrary SQL
  * https://www.postgresql.org/about/news/p-2910/
  * https://www.postgresql.org/docs/release/16.4/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1726747200">- Don't build the libs and mini flavor anymore to hand over to
  PostgreSQL 17.</changelog>
  <changelog author="Antonio Teixeira &lt;antonio.teixeira@suse.com&gt;" date="1726833600">- Pull upstream patch to fix tests with timezone 2024b
  * postgresql-testsuite-timezone-fix.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1730808000">- Sync spec file from postgresql17.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1731499200">- Upgrade to 16.5:
  * CVE-2024-10976, bsc#1233323: Ensure cached plans are marked as
    dependent on the calling role when RLS applies to a
    non-top-level table reference.
  * CVE-2024-10977, bsc#1233325: Make libpq discard error messages
    received during SSL or GSS protocol negotiation.
  * CVE-2024-10978, bsc#1233326: Fix unintended interactions
    between SET SESSION AUTHORIZATION and SET ROLE
  * CVE-2024-10979, bsc#1233327: Prevent trusted PL/Perl code from
    changing environment variables.
  * obsoletes postgresql-testsuite-timezone-fix.patch
  * https://www.postgresql.org/about/news/p-2955/
  * https://www.postgresql.org/docs/release/16.5/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1732017600">- Upgrade to 16.6:
  * Repair ABI break for extensions that work with struct
    ResultRelInfo.
  * Restore functionality of ALTER {ROLE|DATABASE} SET role.
  * Fix cases where a logical replication slot's restart_lsn could
    go backwards.
  * Avoid deleting still-needed WAL files during pg_rewind.
  * Fix race conditions associated with dropping shared statistics
    entries.
  * Count index scans in contrib/bloom indexes in the statistics
    views, such as the pg_stat_user_indexes.idx_scan counter.
  * Fix crash when checking to see if an index's opclass options
    have changed.
  * Avoid assertion failure caused by disconnected NFA sub-graphs
    in regular expression parsing.
  * https://www.postgresql.org/about/news/p-2965/
  * https://www.postgresql.org/docs/release/16.6/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 16.7:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/16.7/
  * https://www.postgresql.org/about/news/-3015/
- Disable LLVM JIT on loongarch64</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 16.8:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/16.8/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 16.9:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/16.9/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to Fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Upgrade to 16.10:
  * https://www.postgresql.org/about/news/postgresql-176-1610-1514-1419-1322-and-18-beta-3-released-3118/
  * https://www.postgresql.org/docs/release/16.10/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1758628800">- Sync spec file from version 18.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Upgrade to 16.11:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/16.11/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 16.12:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/16.12/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 16.13 to fix two regressions in 16.12:
  * https://www.postgresql.org/docs/release/16.13/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
</package>
<package pkgid="2689459364407d414503d769b8d2d10db3c7c156492b5868963192d5a77e803f0584d1a839e7180690dcd211896c8d79b9d86a342640a874bdbbbca410e30c21" name="postgresql16-llvmjit" arch="x86_64">
  <version epoch="0" ver="16.14" rel="80.2"/>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1726747200">- Don't build the libs and mini flavor anymore to hand over to
  PostgreSQL 17.</changelog>
  <changelog author="Antonio Teixeira &lt;antonio.teixeira@suse.com&gt;" date="1726833600">- Pull upstream patch to fix tests with timezone 2024b
  * postgresql-testsuite-timezone-fix.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1730808000">- Sync spec file from postgresql17.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1731499200">- Upgrade to 16.5:
  * CVE-2024-10976, bsc#1233323: Ensure cached plans are marked as
    dependent on the calling role when RLS applies to a
    non-top-level table reference.
  * CVE-2024-10977, bsc#1233325: Make libpq discard error messages
    received during SSL or GSS protocol negotiation.
  * CVE-2024-10978, bsc#1233326: Fix unintended interactions
    between SET SESSION AUTHORIZATION and SET ROLE
  * CVE-2024-10979, bsc#1233327: Prevent trusted PL/Perl code from
    changing environment variables.
  * obsoletes postgresql-testsuite-timezone-fix.patch
  * https://www.postgresql.org/about/news/p-2955/
  * https://www.postgresql.org/docs/release/16.5/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1732017600">- Upgrade to 16.6:
  * Repair ABI break for extensions that work with struct
    ResultRelInfo.
  * Restore functionality of ALTER {ROLE|DATABASE} SET role.
  * Fix cases where a logical replication slot's restart_lsn could
    go backwards.
  * Avoid deleting still-needed WAL files during pg_rewind.
  * Fix race conditions associated with dropping shared statistics
    entries.
  * Count index scans in contrib/bloom indexes in the statistics
    views, such as the pg_stat_user_indexes.idx_scan counter.
  * Fix crash when checking to see if an index's opclass options
    have changed.
  * Avoid assertion failure caused by disconnected NFA sub-graphs
    in regular expression parsing.
  * https://www.postgresql.org/about/news/p-2965/
  * https://www.postgresql.org/docs/release/16.6/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 16.7:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/16.7/
  * https://www.postgresql.org/about/news/-3015/
- Disable LLVM JIT on loongarch64</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 16.8:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/16.8/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 16.9:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/16.9/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to Fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Upgrade to 16.10:
  * https://www.postgresql.org/about/news/postgresql-176-1610-1514-1419-1322-and-18-beta-3-released-3118/
  * https://www.postgresql.org/docs/release/16.10/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1758628800">- Sync spec file from version 18.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Upgrade to 16.11:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/16.11/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 16.12:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/16.12/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 16.13 to fix two regressions in 16.12:
  * https://www.postgresql.org/docs/release/16.13/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1774872000">- Get rid of update-alternatives for openSUSE/SLE 16.0 and newer
  to support immutable systems and transactional updates.
  (jsc#PED-14824)</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1777550400">- bsc#1263804: After dropping update-alternatives we have to
  package /usr/bin/pg_config as an actual symlink, not %ghost.
- Fix spelling of build conditionals.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1778673600">- Update to version 16.13:
  * bsc#1265172, CVE-2026-6472: ensure the user has CREATE
    privilege on the schema specified
  * bsc#1265173, CVE-2026-6473: integer overflows in
    memory-allocation calculations
  * bsc#1265174, CVE-2026-6474: Guard against malicious time zone
    names
  * bsc#1265175, CVE-2026-6475: Prevent path traversal in
    pg_basebackup and pg_rewind
  * bsc#1265177, CVE-2026-6477: Mark PQfn() as unsafe, and avoid
    using it within libpq
  * bsc#1265178, CVE-2026-6478: Use timing-safe string comparisons
    in authentication code
  * bsc#1265179, CVE-2026-6479: Prevent unbounded recursion while
    processing startup packets
  * bsc#1265181, CVE-2026-6637: Prevent SQL injection and buffer
    overruns in contrib/spi
  * bsc#1265182, CVE-2026-6638: Properly quote object names in
    logical replication origin checks
  * https://www.postgresql.org/docs/release/16.13/</changelog>
</package>
<package pkgid="d6d447d55cb79a5e9f423e35b3dce5af80e39a841b65f9413255d89df5de33ed9758e15a6a9ec61b13584b4f84e6d1058d87f15f310345eb73c8a072401d1540" name="postgresql16-llvmjit-devel" arch="aarch64">
  <version epoch="0" ver="16.13" rel="70.2"/>
  <changelog author="Aaron Puchert &lt;aaronpuchert@alice-dsl.net&gt;" date="1710244800">- Require LLVM &lt;= 17 for now, because LLVM 18 doesn't seem to work.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1715169600">- Upgrade to 16.3 (bsc#1224051):
  * bsc#1224038, CVE-2024-4317: Restrict visibility of pg_stats_ext
    and pg_stats_ext_exprs entries to the table owner. See the
    release notes for the steps that have to be taken to fix
    existing PostgreSQL instances.
  * Fix incompatibility with LLVM 18.
  * https://www.postgresql.org/docs/release/16.3/
- Prepare for PostgreSQL 17.
- Make sure all compilation and doc generation happens in %build.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1723291200">- Upgrade to 16.4 (bsc#1229013):
  * bsc#1229013, CVE-2024-7348 PostgreSQL relation replacement
    during pg_dump executes arbitrary SQL
  * https://www.postgresql.org/about/news/p-2910/
  * https://www.postgresql.org/docs/release/16.4/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1726747200">- Don't build the libs and mini flavor anymore to hand over to
  PostgreSQL 17.</changelog>
  <changelog author="Antonio Teixeira &lt;antonio.teixeira@suse.com&gt;" date="1726833600">- Pull upstream patch to fix tests with timezone 2024b
  * postgresql-testsuite-timezone-fix.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1730808000">- Sync spec file from postgresql17.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1731499200">- Upgrade to 16.5:
  * CVE-2024-10976, bsc#1233323: Ensure cached plans are marked as
    dependent on the calling role when RLS applies to a
    non-top-level table reference.
  * CVE-2024-10977, bsc#1233325: Make libpq discard error messages
    received during SSL or GSS protocol negotiation.
  * CVE-2024-10978, bsc#1233326: Fix unintended interactions
    between SET SESSION AUTHORIZATION and SET ROLE
  * CVE-2024-10979, bsc#1233327: Prevent trusted PL/Perl code from
    changing environment variables.
  * obsoletes postgresql-testsuite-timezone-fix.patch
  * https://www.postgresql.org/about/news/p-2955/
  * https://www.postgresql.org/docs/release/16.5/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1732017600">- Upgrade to 16.6:
  * Repair ABI break for extensions that work with struct
    ResultRelInfo.
  * Restore functionality of ALTER {ROLE|DATABASE} SET role.
  * Fix cases where a logical replication slot's restart_lsn could
    go backwards.
  * Avoid deleting still-needed WAL files during pg_rewind.
  * Fix race conditions associated with dropping shared statistics
    entries.
  * Count index scans in contrib/bloom indexes in the statistics
    views, such as the pg_stat_user_indexes.idx_scan counter.
  * Fix crash when checking to see if an index's opclass options
    have changed.
  * Avoid assertion failure caused by disconnected NFA sub-graphs
    in regular expression parsing.
  * https://www.postgresql.org/about/news/p-2965/
  * https://www.postgresql.org/docs/release/16.6/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 16.7:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/16.7/
  * https://www.postgresql.org/about/news/-3015/
- Disable LLVM JIT on loongarch64</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 16.8:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/16.8/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 16.9:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/16.9/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to Fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Upgrade to 16.10:
  * https://www.postgresql.org/about/news/postgresql-176-1610-1514-1419-1322-and-18-beta-3-released-3118/
  * https://www.postgresql.org/docs/release/16.10/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1758628800">- Sync spec file from version 18.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Upgrade to 16.11:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/16.11/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 16.12:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/16.12/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 16.13 to fix two regressions in 16.12:
  * https://www.postgresql.org/docs/release/16.13/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
</package>
<package pkgid="3fc11f988dc233ff303a12c8595a72145e8a56206f8aa695a19a2b0e00a0096016c1d8067b26783ec6a140ed15981b7245998aeefcf3d419497a4b83ae6dc1e8" name="postgresql16-llvmjit-devel" arch="ppc64le">
  <version epoch="0" ver="16.13" rel="70.2"/>
  <changelog author="Aaron Puchert &lt;aaronpuchert@alice-dsl.net&gt;" date="1710244800">- Require LLVM &lt;= 17 for now, because LLVM 18 doesn't seem to work.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1715169600">- Upgrade to 16.3 (bsc#1224051):
  * bsc#1224038, CVE-2024-4317: Restrict visibility of pg_stats_ext
    and pg_stats_ext_exprs entries to the table owner. See the
    release notes for the steps that have to be taken to fix
    existing PostgreSQL instances.
  * Fix incompatibility with LLVM 18.
  * https://www.postgresql.org/docs/release/16.3/
- Prepare for PostgreSQL 17.
- Make sure all compilation and doc generation happens in %build.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1723291200">- Upgrade to 16.4 (bsc#1229013):
  * bsc#1229013, CVE-2024-7348 PostgreSQL relation replacement
    during pg_dump executes arbitrary SQL
  * https://www.postgresql.org/about/news/p-2910/
  * https://www.postgresql.org/docs/release/16.4/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1726747200">- Don't build the libs and mini flavor anymore to hand over to
  PostgreSQL 17.</changelog>
  <changelog author="Antonio Teixeira &lt;antonio.teixeira@suse.com&gt;" date="1726833600">- Pull upstream patch to fix tests with timezone 2024b
  * postgresql-testsuite-timezone-fix.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1730808000">- Sync spec file from postgresql17.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1731499200">- Upgrade to 16.5:
  * CVE-2024-10976, bsc#1233323: Ensure cached plans are marked as
    dependent on the calling role when RLS applies to a
    non-top-level table reference.
  * CVE-2024-10977, bsc#1233325: Make libpq discard error messages
    received during SSL or GSS protocol negotiation.
  * CVE-2024-10978, bsc#1233326: Fix unintended interactions
    between SET SESSION AUTHORIZATION and SET ROLE
  * CVE-2024-10979, bsc#1233327: Prevent trusted PL/Perl code from
    changing environment variables.
  * obsoletes postgresql-testsuite-timezone-fix.patch
  * https://www.postgresql.org/about/news/p-2955/
  * https://www.postgresql.org/docs/release/16.5/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1732017600">- Upgrade to 16.6:
  * Repair ABI break for extensions that work with struct
    ResultRelInfo.
  * Restore functionality of ALTER {ROLE|DATABASE} SET role.
  * Fix cases where a logical replication slot's restart_lsn could
    go backwards.
  * Avoid deleting still-needed WAL files during pg_rewind.
  * Fix race conditions associated with dropping shared statistics
    entries.
  * Count index scans in contrib/bloom indexes in the statistics
    views, such as the pg_stat_user_indexes.idx_scan counter.
  * Fix crash when checking to see if an index's opclass options
    have changed.
  * Avoid assertion failure caused by disconnected NFA sub-graphs
    in regular expression parsing.
  * https://www.postgresql.org/about/news/p-2965/
  * https://www.postgresql.org/docs/release/16.6/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 16.7:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/16.7/
  * https://www.postgresql.org/about/news/-3015/
- Disable LLVM JIT on loongarch64</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 16.8:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/16.8/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 16.9:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/16.9/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to Fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Upgrade to 16.10:
  * https://www.postgresql.org/about/news/postgresql-176-1610-1514-1419-1322-and-18-beta-3-released-3118/
  * https://www.postgresql.org/docs/release/16.10/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1758628800">- Sync spec file from version 18.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Upgrade to 16.11:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/16.11/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 16.12:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/16.12/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 16.13 to fix two regressions in 16.12:
  * https://www.postgresql.org/docs/release/16.13/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
</package>
<package pkgid="f56de099ad55855a47ccf581c7de2b76774ecda8d3b0df55b8b21c9756250a99d0dd6ba94e286a97624873b77929e28ebcf239439c50274acb8e2c4e3eaf86b6" name="postgresql16-llvmjit-devel" arch="s390x">
  <version epoch="0" ver="16.13" rel="70.2"/>
  <changelog author="Aaron Puchert &lt;aaronpuchert@alice-dsl.net&gt;" date="1710244800">- Require LLVM &lt;= 17 for now, because LLVM 18 doesn't seem to work.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1715169600">- Upgrade to 16.3 (bsc#1224051):
  * bsc#1224038, CVE-2024-4317: Restrict visibility of pg_stats_ext
    and pg_stats_ext_exprs entries to the table owner. See the
    release notes for the steps that have to be taken to fix
    existing PostgreSQL instances.
  * Fix incompatibility with LLVM 18.
  * https://www.postgresql.org/docs/release/16.3/
- Prepare for PostgreSQL 17.
- Make sure all compilation and doc generation happens in %build.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1723291200">- Upgrade to 16.4 (bsc#1229013):
  * bsc#1229013, CVE-2024-7348 PostgreSQL relation replacement
    during pg_dump executes arbitrary SQL
  * https://www.postgresql.org/about/news/p-2910/
  * https://www.postgresql.org/docs/release/16.4/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1726747200">- Don't build the libs and mini flavor anymore to hand over to
  PostgreSQL 17.</changelog>
  <changelog author="Antonio Teixeira &lt;antonio.teixeira@suse.com&gt;" date="1726833600">- Pull upstream patch to fix tests with timezone 2024b
  * postgresql-testsuite-timezone-fix.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1730808000">- Sync spec file from postgresql17.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1731499200">- Upgrade to 16.5:
  * CVE-2024-10976, bsc#1233323: Ensure cached plans are marked as
    dependent on the calling role when RLS applies to a
    non-top-level table reference.
  * CVE-2024-10977, bsc#1233325: Make libpq discard error messages
    received during SSL or GSS protocol negotiation.
  * CVE-2024-10978, bsc#1233326: Fix unintended interactions
    between SET SESSION AUTHORIZATION and SET ROLE
  * CVE-2024-10979, bsc#1233327: Prevent trusted PL/Perl code from
    changing environment variables.
  * obsoletes postgresql-testsuite-timezone-fix.patch
  * https://www.postgresql.org/about/news/p-2955/
  * https://www.postgresql.org/docs/release/16.5/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1732017600">- Upgrade to 16.6:
  * Repair ABI break for extensions that work with struct
    ResultRelInfo.
  * Restore functionality of ALTER {ROLE|DATABASE} SET role.
  * Fix cases where a logical replication slot's restart_lsn could
    go backwards.
  * Avoid deleting still-needed WAL files during pg_rewind.
  * Fix race conditions associated with dropping shared statistics
    entries.
  * Count index scans in contrib/bloom indexes in the statistics
    views, such as the pg_stat_user_indexes.idx_scan counter.
  * Fix crash when checking to see if an index's opclass options
    have changed.
  * Avoid assertion failure caused by disconnected NFA sub-graphs
    in regular expression parsing.
  * https://www.postgresql.org/about/news/p-2965/
  * https://www.postgresql.org/docs/release/16.6/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 16.7:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/16.7/
  * https://www.postgresql.org/about/news/-3015/
- Disable LLVM JIT on loongarch64</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 16.8:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/16.8/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 16.9:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/16.9/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to Fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Upgrade to 16.10:
  * https://www.postgresql.org/about/news/postgresql-176-1610-1514-1419-1322-and-18-beta-3-released-3118/
  * https://www.postgresql.org/docs/release/16.10/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1758628800">- Sync spec file from version 18.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Upgrade to 16.11:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/16.11/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 16.12:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/16.12/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 16.13 to fix two regressions in 16.12:
  * https://www.postgresql.org/docs/release/16.13/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
</package>
<package pkgid="708d8dda185bbd51034eec7a56f7cf384498d70f349c68f8147bbbd82d6829e281ad99390969e67c4455bcaf5a9de1bc76ff497cf73c7b32d5d601d39902230b" name="postgresql16-llvmjit-devel" arch="x86_64">
  <version epoch="0" ver="16.14" rel="80.2"/>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1726747200">- Don't build the libs and mini flavor anymore to hand over to
  PostgreSQL 17.</changelog>
  <changelog author="Antonio Teixeira &lt;antonio.teixeira@suse.com&gt;" date="1726833600">- Pull upstream patch to fix tests with timezone 2024b
  * postgresql-testsuite-timezone-fix.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1730808000">- Sync spec file from postgresql17.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1731499200">- Upgrade to 16.5:
  * CVE-2024-10976, bsc#1233323: Ensure cached plans are marked as
    dependent on the calling role when RLS applies to a
    non-top-level table reference.
  * CVE-2024-10977, bsc#1233325: Make libpq discard error messages
    received during SSL or GSS protocol negotiation.
  * CVE-2024-10978, bsc#1233326: Fix unintended interactions
    between SET SESSION AUTHORIZATION and SET ROLE
  * CVE-2024-10979, bsc#1233327: Prevent trusted PL/Perl code from
    changing environment variables.
  * obsoletes postgresql-testsuite-timezone-fix.patch
  * https://www.postgresql.org/about/news/p-2955/
  * https://www.postgresql.org/docs/release/16.5/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1732017600">- Upgrade to 16.6:
  * Repair ABI break for extensions that work with struct
    ResultRelInfo.
  * Restore functionality of ALTER {ROLE|DATABASE} SET role.
  * Fix cases where a logical replication slot's restart_lsn could
    go backwards.
  * Avoid deleting still-needed WAL files during pg_rewind.
  * Fix race conditions associated with dropping shared statistics
    entries.
  * Count index scans in contrib/bloom indexes in the statistics
    views, such as the pg_stat_user_indexes.idx_scan counter.
  * Fix crash when checking to see if an index's opclass options
    have changed.
  * Avoid assertion failure caused by disconnected NFA sub-graphs
    in regular expression parsing.
  * https://www.postgresql.org/about/news/p-2965/
  * https://www.postgresql.org/docs/release/16.6/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 16.7:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/16.7/
  * https://www.postgresql.org/about/news/-3015/
- Disable LLVM JIT on loongarch64</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 16.8:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/16.8/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 16.9:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/16.9/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to Fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Upgrade to 16.10:
  * https://www.postgresql.org/about/news/postgresql-176-1610-1514-1419-1322-and-18-beta-3-released-3118/
  * https://www.postgresql.org/docs/release/16.10/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1758628800">- Sync spec file from version 18.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Upgrade to 16.11:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/16.11/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 16.12:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/16.12/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 16.13 to fix two regressions in 16.12:
  * https://www.postgresql.org/docs/release/16.13/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1774872000">- Get rid of update-alternatives for openSUSE/SLE 16.0 and newer
  to support immutable systems and transactional updates.
  (jsc#PED-14824)</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1777550400">- bsc#1263804: After dropping update-alternatives we have to
  package /usr/bin/pg_config as an actual symlink, not %ghost.
- Fix spelling of build conditionals.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1778673600">- Update to version 16.13:
  * bsc#1265172, CVE-2026-6472: ensure the user has CREATE
    privilege on the schema specified
  * bsc#1265173, CVE-2026-6473: integer overflows in
    memory-allocation calculations
  * bsc#1265174, CVE-2026-6474: Guard against malicious time zone
    names
  * bsc#1265175, CVE-2026-6475: Prevent path traversal in
    pg_basebackup and pg_rewind
  * bsc#1265177, CVE-2026-6477: Mark PQfn() as unsafe, and avoid
    using it within libpq
  * bsc#1265178, CVE-2026-6478: Use timing-safe string comparisons
    in authentication code
  * bsc#1265179, CVE-2026-6479: Prevent unbounded recursion while
    processing startup packets
  * bsc#1265181, CVE-2026-6637: Prevent SQL injection and buffer
    overruns in contrib/spi
  * bsc#1265182, CVE-2026-6638: Properly quote object names in
    logical replication origin checks
  * https://www.postgresql.org/docs/release/16.13/</changelog>
</package>
<package pkgid="a6d9a139db4a01e6b03440d55f005854b88545512fa62730160ef16e9a0d3057b4fb611d561dda30718cbc8113b4632e7d91b82ae811d98bb5ca93b321692a55" name="postgresql16-plperl" arch="aarch64">
  <version epoch="0" ver="16.13" rel="70.2"/>
  <changelog author="Aaron Puchert &lt;aaronpuchert@alice-dsl.net&gt;" date="1710244800">- Require LLVM &lt;= 17 for now, because LLVM 18 doesn't seem to work.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1715169600">- Upgrade to 16.3 (bsc#1224051):
  * bsc#1224038, CVE-2024-4317: Restrict visibility of pg_stats_ext
    and pg_stats_ext_exprs entries to the table owner. See the
    release notes for the steps that have to be taken to fix
    existing PostgreSQL instances.
  * Fix incompatibility with LLVM 18.
  * https://www.postgresql.org/docs/release/16.3/
- Prepare for PostgreSQL 17.
- Make sure all compilation and doc generation happens in %build.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1723291200">- Upgrade to 16.4 (bsc#1229013):
  * bsc#1229013, CVE-2024-7348 PostgreSQL relation replacement
    during pg_dump executes arbitrary SQL
  * https://www.postgresql.org/about/news/p-2910/
  * https://www.postgresql.org/docs/release/16.4/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1726747200">- Don't build the libs and mini flavor anymore to hand over to
  PostgreSQL 17.</changelog>
  <changelog author="Antonio Teixeira &lt;antonio.teixeira@suse.com&gt;" date="1726833600">- Pull upstream patch to fix tests with timezone 2024b
  * postgresql-testsuite-timezone-fix.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1730808000">- Sync spec file from postgresql17.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1731499200">- Upgrade to 16.5:
  * CVE-2024-10976, bsc#1233323: Ensure cached plans are marked as
    dependent on the calling role when RLS applies to a
    non-top-level table reference.
  * CVE-2024-10977, bsc#1233325: Make libpq discard error messages
    received during SSL or GSS protocol negotiation.
  * CVE-2024-10978, bsc#1233326: Fix unintended interactions
    between SET SESSION AUTHORIZATION and SET ROLE
  * CVE-2024-10979, bsc#1233327: Prevent trusted PL/Perl code from
    changing environment variables.
  * obsoletes postgresql-testsuite-timezone-fix.patch
  * https://www.postgresql.org/about/news/p-2955/
  * https://www.postgresql.org/docs/release/16.5/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1732017600">- Upgrade to 16.6:
  * Repair ABI break for extensions that work with struct
    ResultRelInfo.
  * Restore functionality of ALTER {ROLE|DATABASE} SET role.
  * Fix cases where a logical replication slot's restart_lsn could
    go backwards.
  * Avoid deleting still-needed WAL files during pg_rewind.
  * Fix race conditions associated with dropping shared statistics
    entries.
  * Count index scans in contrib/bloom indexes in the statistics
    views, such as the pg_stat_user_indexes.idx_scan counter.
  * Fix crash when checking to see if an index's opclass options
    have changed.
  * Avoid assertion failure caused by disconnected NFA sub-graphs
    in regular expression parsing.
  * https://www.postgresql.org/about/news/p-2965/
  * https://www.postgresql.org/docs/release/16.6/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 16.7:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/16.7/
  * https://www.postgresql.org/about/news/-3015/
- Disable LLVM JIT on loongarch64</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 16.8:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/16.8/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 16.9:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/16.9/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to Fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Upgrade to 16.10:
  * https://www.postgresql.org/about/news/postgresql-176-1610-1514-1419-1322-and-18-beta-3-released-3118/
  * https://www.postgresql.org/docs/release/16.10/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1758628800">- Sync spec file from version 18.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Upgrade to 16.11:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/16.11/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 16.12:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/16.12/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 16.13 to fix two regressions in 16.12:
  * https://www.postgresql.org/docs/release/16.13/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
</package>
<package pkgid="cc728ad6b3a9b5eae0f39c82b3dde72d0fa9c869ca7d2b4425fc630e4e5039155ce438767ffda8d88d6baa96cda6ce1405610d7a6f96de25093d45ce7f2976a3" name="postgresql16-plperl" arch="ppc64le">
  <version epoch="0" ver="16.13" rel="70.2"/>
  <changelog author="Aaron Puchert &lt;aaronpuchert@alice-dsl.net&gt;" date="1710244800">- Require LLVM &lt;= 17 for now, because LLVM 18 doesn't seem to work.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1715169600">- Upgrade to 16.3 (bsc#1224051):
  * bsc#1224038, CVE-2024-4317: Restrict visibility of pg_stats_ext
    and pg_stats_ext_exprs entries to the table owner. See the
    release notes for the steps that have to be taken to fix
    existing PostgreSQL instances.
  * Fix incompatibility with LLVM 18.
  * https://www.postgresql.org/docs/release/16.3/
- Prepare for PostgreSQL 17.
- Make sure all compilation and doc generation happens in %build.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1723291200">- Upgrade to 16.4 (bsc#1229013):
  * bsc#1229013, CVE-2024-7348 PostgreSQL relation replacement
    during pg_dump executes arbitrary SQL
  * https://www.postgresql.org/about/news/p-2910/
  * https://www.postgresql.org/docs/release/16.4/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1726747200">- Don't build the libs and mini flavor anymore to hand over to
  PostgreSQL 17.</changelog>
  <changelog author="Antonio Teixeira &lt;antonio.teixeira@suse.com&gt;" date="1726833600">- Pull upstream patch to fix tests with timezone 2024b
  * postgresql-testsuite-timezone-fix.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1730808000">- Sync spec file from postgresql17.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1731499200">- Upgrade to 16.5:
  * CVE-2024-10976, bsc#1233323: Ensure cached plans are marked as
    dependent on the calling role when RLS applies to a
    non-top-level table reference.
  * CVE-2024-10977, bsc#1233325: Make libpq discard error messages
    received during SSL or GSS protocol negotiation.
  * CVE-2024-10978, bsc#1233326: Fix unintended interactions
    between SET SESSION AUTHORIZATION and SET ROLE
  * CVE-2024-10979, bsc#1233327: Prevent trusted PL/Perl code from
    changing environment variables.
  * obsoletes postgresql-testsuite-timezone-fix.patch
  * https://www.postgresql.org/about/news/p-2955/
  * https://www.postgresql.org/docs/release/16.5/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1732017600">- Upgrade to 16.6:
  * Repair ABI break for extensions that work with struct
    ResultRelInfo.
  * Restore functionality of ALTER {ROLE|DATABASE} SET role.
  * Fix cases where a logical replication slot's restart_lsn could
    go backwards.
  * Avoid deleting still-needed WAL files during pg_rewind.
  * Fix race conditions associated with dropping shared statistics
    entries.
  * Count index scans in contrib/bloom indexes in the statistics
    views, such as the pg_stat_user_indexes.idx_scan counter.
  * Fix crash when checking to see if an index's opclass options
    have changed.
  * Avoid assertion failure caused by disconnected NFA sub-graphs
    in regular expression parsing.
  * https://www.postgresql.org/about/news/p-2965/
  * https://www.postgresql.org/docs/release/16.6/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 16.7:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/16.7/
  * https://www.postgresql.org/about/news/-3015/
- Disable LLVM JIT on loongarch64</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 16.8:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/16.8/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 16.9:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/16.9/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to Fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Upgrade to 16.10:
  * https://www.postgresql.org/about/news/postgresql-176-1610-1514-1419-1322-and-18-beta-3-released-3118/
  * https://www.postgresql.org/docs/release/16.10/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1758628800">- Sync spec file from version 18.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Upgrade to 16.11:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/16.11/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 16.12:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/16.12/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 16.13 to fix two regressions in 16.12:
  * https://www.postgresql.org/docs/release/16.13/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
</package>
<package pkgid="c7b1756bc1f31f40ca50fd3f2559a5421ad89e668315501a682acb2d9282e64c6155d2b40164d2847e7c06eea7b00619004289bc1fd1e6bacf98361149faab9d" name="postgresql16-plperl" arch="s390x">
  <version epoch="0" ver="16.13" rel="70.2"/>
  <changelog author="Aaron Puchert &lt;aaronpuchert@alice-dsl.net&gt;" date="1710244800">- Require LLVM &lt;= 17 for now, because LLVM 18 doesn't seem to work.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1715169600">- Upgrade to 16.3 (bsc#1224051):
  * bsc#1224038, CVE-2024-4317: Restrict visibility of pg_stats_ext
    and pg_stats_ext_exprs entries to the table owner. See the
    release notes for the steps that have to be taken to fix
    existing PostgreSQL instances.
  * Fix incompatibility with LLVM 18.
  * https://www.postgresql.org/docs/release/16.3/
- Prepare for PostgreSQL 17.
- Make sure all compilation and doc generation happens in %build.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1723291200">- Upgrade to 16.4 (bsc#1229013):
  * bsc#1229013, CVE-2024-7348 PostgreSQL relation replacement
    during pg_dump executes arbitrary SQL
  * https://www.postgresql.org/about/news/p-2910/
  * https://www.postgresql.org/docs/release/16.4/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1726747200">- Don't build the libs and mini flavor anymore to hand over to
  PostgreSQL 17.</changelog>
  <changelog author="Antonio Teixeira &lt;antonio.teixeira@suse.com&gt;" date="1726833600">- Pull upstream patch to fix tests with timezone 2024b
  * postgresql-testsuite-timezone-fix.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1730808000">- Sync spec file from postgresql17.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1731499200">- Upgrade to 16.5:
  * CVE-2024-10976, bsc#1233323: Ensure cached plans are marked as
    dependent on the calling role when RLS applies to a
    non-top-level table reference.
  * CVE-2024-10977, bsc#1233325: Make libpq discard error messages
    received during SSL or GSS protocol negotiation.
  * CVE-2024-10978, bsc#1233326: Fix unintended interactions
    between SET SESSION AUTHORIZATION and SET ROLE
  * CVE-2024-10979, bsc#1233327: Prevent trusted PL/Perl code from
    changing environment variables.
  * obsoletes postgresql-testsuite-timezone-fix.patch
  * https://www.postgresql.org/about/news/p-2955/
  * https://www.postgresql.org/docs/release/16.5/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1732017600">- Upgrade to 16.6:
  * Repair ABI break for extensions that work with struct
    ResultRelInfo.
  * Restore functionality of ALTER {ROLE|DATABASE} SET role.
  * Fix cases where a logical replication slot's restart_lsn could
    go backwards.
  * Avoid deleting still-needed WAL files during pg_rewind.
  * Fix race conditions associated with dropping shared statistics
    entries.
  * Count index scans in contrib/bloom indexes in the statistics
    views, such as the pg_stat_user_indexes.idx_scan counter.
  * Fix crash when checking to see if an index's opclass options
    have changed.
  * Avoid assertion failure caused by disconnected NFA sub-graphs
    in regular expression parsing.
  * https://www.postgresql.org/about/news/p-2965/
  * https://www.postgresql.org/docs/release/16.6/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 16.7:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/16.7/
  * https://www.postgresql.org/about/news/-3015/
- Disable LLVM JIT on loongarch64</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 16.8:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/16.8/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 16.9:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/16.9/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to Fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Upgrade to 16.10:
  * https://www.postgresql.org/about/news/postgresql-176-1610-1514-1419-1322-and-18-beta-3-released-3118/
  * https://www.postgresql.org/docs/release/16.10/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1758628800">- Sync spec file from version 18.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Upgrade to 16.11:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/16.11/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 16.12:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/16.12/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 16.13 to fix two regressions in 16.12:
  * https://www.postgresql.org/docs/release/16.13/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
</package>
<package pkgid="b2040d131f0a1616dce2cb9460b1d554b8d0968f6a9e03c293990f0b96258c65f2d8015aa540e01fdb55601f5486fa98dfe9cc0b20c3d949547e49053310f159" name="postgresql16-plperl" arch="x86_64">
  <version epoch="0" ver="16.14" rel="80.2"/>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1726747200">- Don't build the libs and mini flavor anymore to hand over to
  PostgreSQL 17.</changelog>
  <changelog author="Antonio Teixeira &lt;antonio.teixeira@suse.com&gt;" date="1726833600">- Pull upstream patch to fix tests with timezone 2024b
  * postgresql-testsuite-timezone-fix.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1730808000">- Sync spec file from postgresql17.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1731499200">- Upgrade to 16.5:
  * CVE-2024-10976, bsc#1233323: Ensure cached plans are marked as
    dependent on the calling role when RLS applies to a
    non-top-level table reference.
  * CVE-2024-10977, bsc#1233325: Make libpq discard error messages
    received during SSL or GSS protocol negotiation.
  * CVE-2024-10978, bsc#1233326: Fix unintended interactions
    between SET SESSION AUTHORIZATION and SET ROLE
  * CVE-2024-10979, bsc#1233327: Prevent trusted PL/Perl code from
    changing environment variables.
  * obsoletes postgresql-testsuite-timezone-fix.patch
  * https://www.postgresql.org/about/news/p-2955/
  * https://www.postgresql.org/docs/release/16.5/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1732017600">- Upgrade to 16.6:
  * Repair ABI break for extensions that work with struct
    ResultRelInfo.
  * Restore functionality of ALTER {ROLE|DATABASE} SET role.
  * Fix cases where a logical replication slot's restart_lsn could
    go backwards.
  * Avoid deleting still-needed WAL files during pg_rewind.
  * Fix race conditions associated with dropping shared statistics
    entries.
  * Count index scans in contrib/bloom indexes in the statistics
    views, such as the pg_stat_user_indexes.idx_scan counter.
  * Fix crash when checking to see if an index's opclass options
    have changed.
  * Avoid assertion failure caused by disconnected NFA sub-graphs
    in regular expression parsing.
  * https://www.postgresql.org/about/news/p-2965/
  * https://www.postgresql.org/docs/release/16.6/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 16.7:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/16.7/
  * https://www.postgresql.org/about/news/-3015/
- Disable LLVM JIT on loongarch64</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 16.8:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/16.8/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 16.9:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/16.9/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to Fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Upgrade to 16.10:
  * https://www.postgresql.org/about/news/postgresql-176-1610-1514-1419-1322-and-18-beta-3-released-3118/
  * https://www.postgresql.org/docs/release/16.10/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1758628800">- Sync spec file from version 18.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Upgrade to 16.11:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/16.11/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 16.12:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/16.12/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 16.13 to fix two regressions in 16.12:
  * https://www.postgresql.org/docs/release/16.13/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1774872000">- Get rid of update-alternatives for openSUSE/SLE 16.0 and newer
  to support immutable systems and transactional updates.
  (jsc#PED-14824)</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1777550400">- bsc#1263804: After dropping update-alternatives we have to
  package /usr/bin/pg_config as an actual symlink, not %ghost.
- Fix spelling of build conditionals.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1778673600">- Update to version 16.13:
  * bsc#1265172, CVE-2026-6472: ensure the user has CREATE
    privilege on the schema specified
  * bsc#1265173, CVE-2026-6473: integer overflows in
    memory-allocation calculations
  * bsc#1265174, CVE-2026-6474: Guard against malicious time zone
    names
  * bsc#1265175, CVE-2026-6475: Prevent path traversal in
    pg_basebackup and pg_rewind
  * bsc#1265177, CVE-2026-6477: Mark PQfn() as unsafe, and avoid
    using it within libpq
  * bsc#1265178, CVE-2026-6478: Use timing-safe string comparisons
    in authentication code
  * bsc#1265179, CVE-2026-6479: Prevent unbounded recursion while
    processing startup packets
  * bsc#1265181, CVE-2026-6637: Prevent SQL injection and buffer
    overruns in contrib/spi
  * bsc#1265182, CVE-2026-6638: Properly quote object names in
    logical replication origin checks
  * https://www.postgresql.org/docs/release/16.13/</changelog>
</package>
<package pkgid="0c41f835c373ce4eeaa265d864d72bf2477563b91de4bd763bd60bd13e8e747c0d108024cc4f2530868d7a4d0bc2b301cebd42ba2c9c946a966dc54925b54cb8" name="postgresql16-plpython" arch="aarch64">
  <version epoch="0" ver="16.13" rel="70.2"/>
  <changelog author="Aaron Puchert &lt;aaronpuchert@alice-dsl.net&gt;" date="1710244800">- Require LLVM &lt;= 17 for now, because LLVM 18 doesn't seem to work.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1715169600">- Upgrade to 16.3 (bsc#1224051):
  * bsc#1224038, CVE-2024-4317: Restrict visibility of pg_stats_ext
    and pg_stats_ext_exprs entries to the table owner. See the
    release notes for the steps that have to be taken to fix
    existing PostgreSQL instances.
  * Fix incompatibility with LLVM 18.
  * https://www.postgresql.org/docs/release/16.3/
- Prepare for PostgreSQL 17.
- Make sure all compilation and doc generation happens in %build.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1723291200">- Upgrade to 16.4 (bsc#1229013):
  * bsc#1229013, CVE-2024-7348 PostgreSQL relation replacement
    during pg_dump executes arbitrary SQL
  * https://www.postgresql.org/about/news/p-2910/
  * https://www.postgresql.org/docs/release/16.4/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1726747200">- Don't build the libs and mini flavor anymore to hand over to
  PostgreSQL 17.</changelog>
  <changelog author="Antonio Teixeira &lt;antonio.teixeira@suse.com&gt;" date="1726833600">- Pull upstream patch to fix tests with timezone 2024b
  * postgresql-testsuite-timezone-fix.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1730808000">- Sync spec file from postgresql17.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1731499200">- Upgrade to 16.5:
  * CVE-2024-10976, bsc#1233323: Ensure cached plans are marked as
    dependent on the calling role when RLS applies to a
    non-top-level table reference.
  * CVE-2024-10977, bsc#1233325: Make libpq discard error messages
    received during SSL or GSS protocol negotiation.
  * CVE-2024-10978, bsc#1233326: Fix unintended interactions
    between SET SESSION AUTHORIZATION and SET ROLE
  * CVE-2024-10979, bsc#1233327: Prevent trusted PL/Perl code from
    changing environment variables.
  * obsoletes postgresql-testsuite-timezone-fix.patch
  * https://www.postgresql.org/about/news/p-2955/
  * https://www.postgresql.org/docs/release/16.5/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1732017600">- Upgrade to 16.6:
  * Repair ABI break for extensions that work with struct
    ResultRelInfo.
  * Restore functionality of ALTER {ROLE|DATABASE} SET role.
  * Fix cases where a logical replication slot's restart_lsn could
    go backwards.
  * Avoid deleting still-needed WAL files during pg_rewind.
  * Fix race conditions associated with dropping shared statistics
    entries.
  * Count index scans in contrib/bloom indexes in the statistics
    views, such as the pg_stat_user_indexes.idx_scan counter.
  * Fix crash when checking to see if an index's opclass options
    have changed.
  * Avoid assertion failure caused by disconnected NFA sub-graphs
    in regular expression parsing.
  * https://www.postgresql.org/about/news/p-2965/
  * https://www.postgresql.org/docs/release/16.6/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 16.7:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/16.7/
  * https://www.postgresql.org/about/news/-3015/
- Disable LLVM JIT on loongarch64</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 16.8:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/16.8/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 16.9:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/16.9/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to Fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Upgrade to 16.10:
  * https://www.postgresql.org/about/news/postgresql-176-1610-1514-1419-1322-and-18-beta-3-released-3118/
  * https://www.postgresql.org/docs/release/16.10/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1758628800">- Sync spec file from version 18.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Upgrade to 16.11:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/16.11/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 16.12:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/16.12/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 16.13 to fix two regressions in 16.12:
  * https://www.postgresql.org/docs/release/16.13/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
</package>
<package pkgid="f72d672b4ac73965d303557ab69311050591acee046d55552350d3ed080855ec5ebd11b21c974adff453cc5864a55956843c9b151ce5b2aa67fc0c5fb87fc044" name="postgresql16-plpython" arch="ppc64le">
  <version epoch="0" ver="16.13" rel="70.2"/>
  <changelog author="Aaron Puchert &lt;aaronpuchert@alice-dsl.net&gt;" date="1710244800">- Require LLVM &lt;= 17 for now, because LLVM 18 doesn't seem to work.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1715169600">- Upgrade to 16.3 (bsc#1224051):
  * bsc#1224038, CVE-2024-4317: Restrict visibility of pg_stats_ext
    and pg_stats_ext_exprs entries to the table owner. See the
    release notes for the steps that have to be taken to fix
    existing PostgreSQL instances.
  * Fix incompatibility with LLVM 18.
  * https://www.postgresql.org/docs/release/16.3/
- Prepare for PostgreSQL 17.
- Make sure all compilation and doc generation happens in %build.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1723291200">- Upgrade to 16.4 (bsc#1229013):
  * bsc#1229013, CVE-2024-7348 PostgreSQL relation replacement
    during pg_dump executes arbitrary SQL
  * https://www.postgresql.org/about/news/p-2910/
  * https://www.postgresql.org/docs/release/16.4/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1726747200">- Don't build the libs and mini flavor anymore to hand over to
  PostgreSQL 17.</changelog>
  <changelog author="Antonio Teixeira &lt;antonio.teixeira@suse.com&gt;" date="1726833600">- Pull upstream patch to fix tests with timezone 2024b
  * postgresql-testsuite-timezone-fix.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1730808000">- Sync spec file from postgresql17.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1731499200">- Upgrade to 16.5:
  * CVE-2024-10976, bsc#1233323: Ensure cached plans are marked as
    dependent on the calling role when RLS applies to a
    non-top-level table reference.
  * CVE-2024-10977, bsc#1233325: Make libpq discard error messages
    received during SSL or GSS protocol negotiation.
  * CVE-2024-10978, bsc#1233326: Fix unintended interactions
    between SET SESSION AUTHORIZATION and SET ROLE
  * CVE-2024-10979, bsc#1233327: Prevent trusted PL/Perl code from
    changing environment variables.
  * obsoletes postgresql-testsuite-timezone-fix.patch
  * https://www.postgresql.org/about/news/p-2955/
  * https://www.postgresql.org/docs/release/16.5/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1732017600">- Upgrade to 16.6:
  * Repair ABI break for extensions that work with struct
    ResultRelInfo.
  * Restore functionality of ALTER {ROLE|DATABASE} SET role.
  * Fix cases where a logical replication slot's restart_lsn could
    go backwards.
  * Avoid deleting still-needed WAL files during pg_rewind.
  * Fix race conditions associated with dropping shared statistics
    entries.
  * Count index scans in contrib/bloom indexes in the statistics
    views, such as the pg_stat_user_indexes.idx_scan counter.
  * Fix crash when checking to see if an index's opclass options
    have changed.
  * Avoid assertion failure caused by disconnected NFA sub-graphs
    in regular expression parsing.
  * https://www.postgresql.org/about/news/p-2965/
  * https://www.postgresql.org/docs/release/16.6/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 16.7:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/16.7/
  * https://www.postgresql.org/about/news/-3015/
- Disable LLVM JIT on loongarch64</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 16.8:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/16.8/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 16.9:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/16.9/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to Fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Upgrade to 16.10:
  * https://www.postgresql.org/about/news/postgresql-176-1610-1514-1419-1322-and-18-beta-3-released-3118/
  * https://www.postgresql.org/docs/release/16.10/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1758628800">- Sync spec file from version 18.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Upgrade to 16.11:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/16.11/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 16.12:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/16.12/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 16.13 to fix two regressions in 16.12:
  * https://www.postgresql.org/docs/release/16.13/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
</package>
<package pkgid="9c6c8fdaca09adc69824013e17a5e479df393d015ad39a1deecdc21b3a3d2d9314d55c4c33c6e7e76755b29e3df9ac472b661e7b95c96226d1c4d873aa8fb628" name="postgresql16-plpython" arch="s390x">
  <version epoch="0" ver="16.13" rel="70.2"/>
  <changelog author="Aaron Puchert &lt;aaronpuchert@alice-dsl.net&gt;" date="1710244800">- Require LLVM &lt;= 17 for now, because LLVM 18 doesn't seem to work.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1715169600">- Upgrade to 16.3 (bsc#1224051):
  * bsc#1224038, CVE-2024-4317: Restrict visibility of pg_stats_ext
    and pg_stats_ext_exprs entries to the table owner. See the
    release notes for the steps that have to be taken to fix
    existing PostgreSQL instances.
  * Fix incompatibility with LLVM 18.
  * https://www.postgresql.org/docs/release/16.3/
- Prepare for PostgreSQL 17.
- Make sure all compilation and doc generation happens in %build.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1723291200">- Upgrade to 16.4 (bsc#1229013):
  * bsc#1229013, CVE-2024-7348 PostgreSQL relation replacement
    during pg_dump executes arbitrary SQL
  * https://www.postgresql.org/about/news/p-2910/
  * https://www.postgresql.org/docs/release/16.4/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1726747200">- Don't build the libs and mini flavor anymore to hand over to
  PostgreSQL 17.</changelog>
  <changelog author="Antonio Teixeira &lt;antonio.teixeira@suse.com&gt;" date="1726833600">- Pull upstream patch to fix tests with timezone 2024b
  * postgresql-testsuite-timezone-fix.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1730808000">- Sync spec file from postgresql17.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1731499200">- Upgrade to 16.5:
  * CVE-2024-10976, bsc#1233323: Ensure cached plans are marked as
    dependent on the calling role when RLS applies to a
    non-top-level table reference.
  * CVE-2024-10977, bsc#1233325: Make libpq discard error messages
    received during SSL or GSS protocol negotiation.
  * CVE-2024-10978, bsc#1233326: Fix unintended interactions
    between SET SESSION AUTHORIZATION and SET ROLE
  * CVE-2024-10979, bsc#1233327: Prevent trusted PL/Perl code from
    changing environment variables.
  * obsoletes postgresql-testsuite-timezone-fix.patch
  * https://www.postgresql.org/about/news/p-2955/
  * https://www.postgresql.org/docs/release/16.5/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1732017600">- Upgrade to 16.6:
  * Repair ABI break for extensions that work with struct
    ResultRelInfo.
  * Restore functionality of ALTER {ROLE|DATABASE} SET role.
  * Fix cases where a logical replication slot's restart_lsn could
    go backwards.
  * Avoid deleting still-needed WAL files during pg_rewind.
  * Fix race conditions associated with dropping shared statistics
    entries.
  * Count index scans in contrib/bloom indexes in the statistics
    views, such as the pg_stat_user_indexes.idx_scan counter.
  * Fix crash when checking to see if an index's opclass options
    have changed.
  * Avoid assertion failure caused by disconnected NFA sub-graphs
    in regular expression parsing.
  * https://www.postgresql.org/about/news/p-2965/
  * https://www.postgresql.org/docs/release/16.6/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 16.7:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/16.7/
  * https://www.postgresql.org/about/news/-3015/
- Disable LLVM JIT on loongarch64</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 16.8:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/16.8/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 16.9:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/16.9/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to Fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Upgrade to 16.10:
  * https://www.postgresql.org/about/news/postgresql-176-1610-1514-1419-1322-and-18-beta-3-released-3118/
  * https://www.postgresql.org/docs/release/16.10/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1758628800">- Sync spec file from version 18.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Upgrade to 16.11:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/16.11/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 16.12:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/16.12/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 16.13 to fix two regressions in 16.12:
  * https://www.postgresql.org/docs/release/16.13/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
</package>
<package pkgid="b41cdd8bdbc5dc8c23aaa8c27629420780e5f7a52bf375365d922eff4d903d0648dcf5507866ae2ade46137e4f888348b7ad3d009fa79368809ee4e8487ba991" name="postgresql16-plpython" arch="x86_64">
  <version epoch="0" ver="16.14" rel="80.2"/>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1726747200">- Don't build the libs and mini flavor anymore to hand over to
  PostgreSQL 17.</changelog>
  <changelog author="Antonio Teixeira &lt;antonio.teixeira@suse.com&gt;" date="1726833600">- Pull upstream patch to fix tests with timezone 2024b
  * postgresql-testsuite-timezone-fix.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1730808000">- Sync spec file from postgresql17.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1731499200">- Upgrade to 16.5:
  * CVE-2024-10976, bsc#1233323: Ensure cached plans are marked as
    dependent on the calling role when RLS applies to a
    non-top-level table reference.
  * CVE-2024-10977, bsc#1233325: Make libpq discard error messages
    received during SSL or GSS protocol negotiation.
  * CVE-2024-10978, bsc#1233326: Fix unintended interactions
    between SET SESSION AUTHORIZATION and SET ROLE
  * CVE-2024-10979, bsc#1233327: Prevent trusted PL/Perl code from
    changing environment variables.
  * obsoletes postgresql-testsuite-timezone-fix.patch
  * https://www.postgresql.org/about/news/p-2955/
  * https://www.postgresql.org/docs/release/16.5/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1732017600">- Upgrade to 16.6:
  * Repair ABI break for extensions that work with struct
    ResultRelInfo.
  * Restore functionality of ALTER {ROLE|DATABASE} SET role.
  * Fix cases where a logical replication slot's restart_lsn could
    go backwards.
  * Avoid deleting still-needed WAL files during pg_rewind.
  * Fix race conditions associated with dropping shared statistics
    entries.
  * Count index scans in contrib/bloom indexes in the statistics
    views, such as the pg_stat_user_indexes.idx_scan counter.
  * Fix crash when checking to see if an index's opclass options
    have changed.
  * Avoid assertion failure caused by disconnected NFA sub-graphs
    in regular expression parsing.
  * https://www.postgresql.org/about/news/p-2965/
  * https://www.postgresql.org/docs/release/16.6/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 16.7:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/16.7/
  * https://www.postgresql.org/about/news/-3015/
- Disable LLVM JIT on loongarch64</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 16.8:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/16.8/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 16.9:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/16.9/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to Fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Upgrade to 16.10:
  * https://www.postgresql.org/about/news/postgresql-176-1610-1514-1419-1322-and-18-beta-3-released-3118/
  * https://www.postgresql.org/docs/release/16.10/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1758628800">- Sync spec file from version 18.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Upgrade to 16.11:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/16.11/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 16.12:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/16.12/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 16.13 to fix two regressions in 16.12:
  * https://www.postgresql.org/docs/release/16.13/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1774872000">- Get rid of update-alternatives for openSUSE/SLE 16.0 and newer
  to support immutable systems and transactional updates.
  (jsc#PED-14824)</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1777550400">- bsc#1263804: After dropping update-alternatives we have to
  package /usr/bin/pg_config as an actual symlink, not %ghost.
- Fix spelling of build conditionals.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1778673600">- Update to version 16.13:
  * bsc#1265172, CVE-2026-6472: ensure the user has CREATE
    privilege on the schema specified
  * bsc#1265173, CVE-2026-6473: integer overflows in
    memory-allocation calculations
  * bsc#1265174, CVE-2026-6474: Guard against malicious time zone
    names
  * bsc#1265175, CVE-2026-6475: Prevent path traversal in
    pg_basebackup and pg_rewind
  * bsc#1265177, CVE-2026-6477: Mark PQfn() as unsafe, and avoid
    using it within libpq
  * bsc#1265178, CVE-2026-6478: Use timing-safe string comparisons
    in authentication code
  * bsc#1265179, CVE-2026-6479: Prevent unbounded recursion while
    processing startup packets
  * bsc#1265181, CVE-2026-6637: Prevent SQL injection and buffer
    overruns in contrib/spi
  * bsc#1265182, CVE-2026-6638: Properly quote object names in
    logical replication origin checks
  * https://www.postgresql.org/docs/release/16.13/</changelog>
</package>
<package pkgid="9b04f76c58d0a885486a76f598a5e454fe57c78e8810481af42568c160b12328f351c2744702d9042b7a789536085f3c768fd35f742e9e5d647543eb61d07a9b" name="postgresql16-pltcl" arch="aarch64">
  <version epoch="0" ver="16.13" rel="70.2"/>
  <changelog author="Aaron Puchert &lt;aaronpuchert@alice-dsl.net&gt;" date="1710244800">- Require LLVM &lt;= 17 for now, because LLVM 18 doesn't seem to work.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1715169600">- Upgrade to 16.3 (bsc#1224051):
  * bsc#1224038, CVE-2024-4317: Restrict visibility of pg_stats_ext
    and pg_stats_ext_exprs entries to the table owner. See the
    release notes for the steps that have to be taken to fix
    existing PostgreSQL instances.
  * Fix incompatibility with LLVM 18.
  * https://www.postgresql.org/docs/release/16.3/
- Prepare for PostgreSQL 17.
- Make sure all compilation and doc generation happens in %build.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1723291200">- Upgrade to 16.4 (bsc#1229013):
  * bsc#1229013, CVE-2024-7348 PostgreSQL relation replacement
    during pg_dump executes arbitrary SQL
  * https://www.postgresql.org/about/news/p-2910/
  * https://www.postgresql.org/docs/release/16.4/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1726747200">- Don't build the libs and mini flavor anymore to hand over to
  PostgreSQL 17.</changelog>
  <changelog author="Antonio Teixeira &lt;antonio.teixeira@suse.com&gt;" date="1726833600">- Pull upstream patch to fix tests with timezone 2024b
  * postgresql-testsuite-timezone-fix.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1730808000">- Sync spec file from postgresql17.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1731499200">- Upgrade to 16.5:
  * CVE-2024-10976, bsc#1233323: Ensure cached plans are marked as
    dependent on the calling role when RLS applies to a
    non-top-level table reference.
  * CVE-2024-10977, bsc#1233325: Make libpq discard error messages
    received during SSL or GSS protocol negotiation.
  * CVE-2024-10978, bsc#1233326: Fix unintended interactions
    between SET SESSION AUTHORIZATION and SET ROLE
  * CVE-2024-10979, bsc#1233327: Prevent trusted PL/Perl code from
    changing environment variables.
  * obsoletes postgresql-testsuite-timezone-fix.patch
  * https://www.postgresql.org/about/news/p-2955/
  * https://www.postgresql.org/docs/release/16.5/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1732017600">- Upgrade to 16.6:
  * Repair ABI break for extensions that work with struct
    ResultRelInfo.
  * Restore functionality of ALTER {ROLE|DATABASE} SET role.
  * Fix cases where a logical replication slot's restart_lsn could
    go backwards.
  * Avoid deleting still-needed WAL files during pg_rewind.
  * Fix race conditions associated with dropping shared statistics
    entries.
  * Count index scans in contrib/bloom indexes in the statistics
    views, such as the pg_stat_user_indexes.idx_scan counter.
  * Fix crash when checking to see if an index's opclass options
    have changed.
  * Avoid assertion failure caused by disconnected NFA sub-graphs
    in regular expression parsing.
  * https://www.postgresql.org/about/news/p-2965/
  * https://www.postgresql.org/docs/release/16.6/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 16.7:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/16.7/
  * https://www.postgresql.org/about/news/-3015/
- Disable LLVM JIT on loongarch64</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 16.8:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/16.8/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 16.9:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/16.9/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to Fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Upgrade to 16.10:
  * https://www.postgresql.org/about/news/postgresql-176-1610-1514-1419-1322-and-18-beta-3-released-3118/
  * https://www.postgresql.org/docs/release/16.10/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1758628800">- Sync spec file from version 18.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Upgrade to 16.11:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/16.11/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 16.12:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/16.12/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 16.13 to fix two regressions in 16.12:
  * https://www.postgresql.org/docs/release/16.13/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
</package>
<package pkgid="6c28f4c50d45226c334cd36e2a46b52da2d870d2658b5c40a469a329083195c622e2700ab46bda0c24901975bcaad817abebda194d32b91f1b60fdf5d14b9c57" name="postgresql16-pltcl" arch="ppc64le">
  <version epoch="0" ver="16.13" rel="70.2"/>
  <changelog author="Aaron Puchert &lt;aaronpuchert@alice-dsl.net&gt;" date="1710244800">- Require LLVM &lt;= 17 for now, because LLVM 18 doesn't seem to work.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1715169600">- Upgrade to 16.3 (bsc#1224051):
  * bsc#1224038, CVE-2024-4317: Restrict visibility of pg_stats_ext
    and pg_stats_ext_exprs entries to the table owner. See the
    release notes for the steps that have to be taken to fix
    existing PostgreSQL instances.
  * Fix incompatibility with LLVM 18.
  * https://www.postgresql.org/docs/release/16.3/
- Prepare for PostgreSQL 17.
- Make sure all compilation and doc generation happens in %build.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1723291200">- Upgrade to 16.4 (bsc#1229013):
  * bsc#1229013, CVE-2024-7348 PostgreSQL relation replacement
    during pg_dump executes arbitrary SQL
  * https://www.postgresql.org/about/news/p-2910/
  * https://www.postgresql.org/docs/release/16.4/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1726747200">- Don't build the libs and mini flavor anymore to hand over to
  PostgreSQL 17.</changelog>
  <changelog author="Antonio Teixeira &lt;antonio.teixeira@suse.com&gt;" date="1726833600">- Pull upstream patch to fix tests with timezone 2024b
  * postgresql-testsuite-timezone-fix.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1730808000">- Sync spec file from postgresql17.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1731499200">- Upgrade to 16.5:
  * CVE-2024-10976, bsc#1233323: Ensure cached plans are marked as
    dependent on the calling role when RLS applies to a
    non-top-level table reference.
  * CVE-2024-10977, bsc#1233325: Make libpq discard error messages
    received during SSL or GSS protocol negotiation.
  * CVE-2024-10978, bsc#1233326: Fix unintended interactions
    between SET SESSION AUTHORIZATION and SET ROLE
  * CVE-2024-10979, bsc#1233327: Prevent trusted PL/Perl code from
    changing environment variables.
  * obsoletes postgresql-testsuite-timezone-fix.patch
  * https://www.postgresql.org/about/news/p-2955/
  * https://www.postgresql.org/docs/release/16.5/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1732017600">- Upgrade to 16.6:
  * Repair ABI break for extensions that work with struct
    ResultRelInfo.
  * Restore functionality of ALTER {ROLE|DATABASE} SET role.
  * Fix cases where a logical replication slot's restart_lsn could
    go backwards.
  * Avoid deleting still-needed WAL files during pg_rewind.
  * Fix race conditions associated with dropping shared statistics
    entries.
  * Count index scans in contrib/bloom indexes in the statistics
    views, such as the pg_stat_user_indexes.idx_scan counter.
  * Fix crash when checking to see if an index's opclass options
    have changed.
  * Avoid assertion failure caused by disconnected NFA sub-graphs
    in regular expression parsing.
  * https://www.postgresql.org/about/news/p-2965/
  * https://www.postgresql.org/docs/release/16.6/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 16.7:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/16.7/
  * https://www.postgresql.org/about/news/-3015/
- Disable LLVM JIT on loongarch64</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 16.8:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/16.8/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 16.9:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/16.9/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to Fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Upgrade to 16.10:
  * https://www.postgresql.org/about/news/postgresql-176-1610-1514-1419-1322-and-18-beta-3-released-3118/
  * https://www.postgresql.org/docs/release/16.10/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1758628800">- Sync spec file from version 18.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Upgrade to 16.11:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/16.11/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 16.12:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/16.12/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 16.13 to fix two regressions in 16.12:
  * https://www.postgresql.org/docs/release/16.13/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
</package>
<package pkgid="98467da6d1092cb2a0d0c8a9b3ab6872e4a085b8f841f591a4649f8b23d5ebcb52dba7a87416d13de5a81f2b710755044e7402f6c9f84e522a60021788910707" name="postgresql16-pltcl" arch="s390x">
  <version epoch="0" ver="16.13" rel="70.2"/>
  <changelog author="Aaron Puchert &lt;aaronpuchert@alice-dsl.net&gt;" date="1710244800">- Require LLVM &lt;= 17 for now, because LLVM 18 doesn't seem to work.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1715169600">- Upgrade to 16.3 (bsc#1224051):
  * bsc#1224038, CVE-2024-4317: Restrict visibility of pg_stats_ext
    and pg_stats_ext_exprs entries to the table owner. See the
    release notes for the steps that have to be taken to fix
    existing PostgreSQL instances.
  * Fix incompatibility with LLVM 18.
  * https://www.postgresql.org/docs/release/16.3/
- Prepare for PostgreSQL 17.
- Make sure all compilation and doc generation happens in %build.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1723291200">- Upgrade to 16.4 (bsc#1229013):
  * bsc#1229013, CVE-2024-7348 PostgreSQL relation replacement
    during pg_dump executes arbitrary SQL
  * https://www.postgresql.org/about/news/p-2910/
  * https://www.postgresql.org/docs/release/16.4/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1726747200">- Don't build the libs and mini flavor anymore to hand over to
  PostgreSQL 17.</changelog>
  <changelog author="Antonio Teixeira &lt;antonio.teixeira@suse.com&gt;" date="1726833600">- Pull upstream patch to fix tests with timezone 2024b
  * postgresql-testsuite-timezone-fix.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1730808000">- Sync spec file from postgresql17.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1731499200">- Upgrade to 16.5:
  * CVE-2024-10976, bsc#1233323: Ensure cached plans are marked as
    dependent on the calling role when RLS applies to a
    non-top-level table reference.
  * CVE-2024-10977, bsc#1233325: Make libpq discard error messages
    received during SSL or GSS protocol negotiation.
  * CVE-2024-10978, bsc#1233326: Fix unintended interactions
    between SET SESSION AUTHORIZATION and SET ROLE
  * CVE-2024-10979, bsc#1233327: Prevent trusted PL/Perl code from
    changing environment variables.
  * obsoletes postgresql-testsuite-timezone-fix.patch
  * https://www.postgresql.org/about/news/p-2955/
  * https://www.postgresql.org/docs/release/16.5/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1732017600">- Upgrade to 16.6:
  * Repair ABI break for extensions that work with struct
    ResultRelInfo.
  * Restore functionality of ALTER {ROLE|DATABASE} SET role.
  * Fix cases where a logical replication slot's restart_lsn could
    go backwards.
  * Avoid deleting still-needed WAL files during pg_rewind.
  * Fix race conditions associated with dropping shared statistics
    entries.
  * Count index scans in contrib/bloom indexes in the statistics
    views, such as the pg_stat_user_indexes.idx_scan counter.
  * Fix crash when checking to see if an index's opclass options
    have changed.
  * Avoid assertion failure caused by disconnected NFA sub-graphs
    in regular expression parsing.
  * https://www.postgresql.org/about/news/p-2965/
  * https://www.postgresql.org/docs/release/16.6/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 16.7:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/16.7/
  * https://www.postgresql.org/about/news/-3015/
- Disable LLVM JIT on loongarch64</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 16.8:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/16.8/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 16.9:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/16.9/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to Fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Upgrade to 16.10:
  * https://www.postgresql.org/about/news/postgresql-176-1610-1514-1419-1322-and-18-beta-3-released-3118/
  * https://www.postgresql.org/docs/release/16.10/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1758628800">- Sync spec file from version 18.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Upgrade to 16.11:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/16.11/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 16.12:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/16.12/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 16.13 to fix two regressions in 16.12:
  * https://www.postgresql.org/docs/release/16.13/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
</package>
<package pkgid="2b4a3cd39717fdb5e5484e2963104b5fc65c4085355cdc88402e807c40ea80d54affd9c76e7f17137fc2a1e4a6bd07eaafe73069d5ac5031dbe23395035ce3c6" name="postgresql16-pltcl" arch="x86_64">
  <version epoch="0" ver="16.14" rel="80.2"/>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1726747200">- Don't build the libs and mini flavor anymore to hand over to
  PostgreSQL 17.</changelog>
  <changelog author="Antonio Teixeira &lt;antonio.teixeira@suse.com&gt;" date="1726833600">- Pull upstream patch to fix tests with timezone 2024b
  * postgresql-testsuite-timezone-fix.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1730808000">- Sync spec file from postgresql17.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1731499200">- Upgrade to 16.5:
  * CVE-2024-10976, bsc#1233323: Ensure cached plans are marked as
    dependent on the calling role when RLS applies to a
    non-top-level table reference.
  * CVE-2024-10977, bsc#1233325: Make libpq discard error messages
    received during SSL or GSS protocol negotiation.
  * CVE-2024-10978, bsc#1233326: Fix unintended interactions
    between SET SESSION AUTHORIZATION and SET ROLE
  * CVE-2024-10979, bsc#1233327: Prevent trusted PL/Perl code from
    changing environment variables.
  * obsoletes postgresql-testsuite-timezone-fix.patch
  * https://www.postgresql.org/about/news/p-2955/
  * https://www.postgresql.org/docs/release/16.5/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1732017600">- Upgrade to 16.6:
  * Repair ABI break for extensions that work with struct
    ResultRelInfo.
  * Restore functionality of ALTER {ROLE|DATABASE} SET role.
  * Fix cases where a logical replication slot's restart_lsn could
    go backwards.
  * Avoid deleting still-needed WAL files during pg_rewind.
  * Fix race conditions associated with dropping shared statistics
    entries.
  * Count index scans in contrib/bloom indexes in the statistics
    views, such as the pg_stat_user_indexes.idx_scan counter.
  * Fix crash when checking to see if an index's opclass options
    have changed.
  * Avoid assertion failure caused by disconnected NFA sub-graphs
    in regular expression parsing.
  * https://www.postgresql.org/about/news/p-2965/
  * https://www.postgresql.org/docs/release/16.6/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 16.7:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/16.7/
  * https://www.postgresql.org/about/news/-3015/
- Disable LLVM JIT on loongarch64</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 16.8:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/16.8/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 16.9:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/16.9/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to Fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Upgrade to 16.10:
  * https://www.postgresql.org/about/news/postgresql-176-1610-1514-1419-1322-and-18-beta-3-released-3118/
  * https://www.postgresql.org/docs/release/16.10/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1758628800">- Sync spec file from version 18.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Upgrade to 16.11:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/16.11/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 16.12:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/16.12/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 16.13 to fix two regressions in 16.12:
  * https://www.postgresql.org/docs/release/16.13/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1774872000">- Get rid of update-alternatives for openSUSE/SLE 16.0 and newer
  to support immutable systems and transactional updates.
  (jsc#PED-14824)</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1777550400">- bsc#1263804: After dropping update-alternatives we have to
  package /usr/bin/pg_config as an actual symlink, not %ghost.
- Fix spelling of build conditionals.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1778673600">- Update to version 16.13:
  * bsc#1265172, CVE-2026-6472: ensure the user has CREATE
    privilege on the schema specified
  * bsc#1265173, CVE-2026-6473: integer overflows in
    memory-allocation calculations
  * bsc#1265174, CVE-2026-6474: Guard against malicious time zone
    names
  * bsc#1265175, CVE-2026-6475: Prevent path traversal in
    pg_basebackup and pg_rewind
  * bsc#1265177, CVE-2026-6477: Mark PQfn() as unsafe, and avoid
    using it within libpq
  * bsc#1265178, CVE-2026-6478: Use timing-safe string comparisons
    in authentication code
  * bsc#1265179, CVE-2026-6479: Prevent unbounded recursion while
    processing startup packets
  * bsc#1265181, CVE-2026-6637: Prevent SQL injection and buffer
    overruns in contrib/spi
  * bsc#1265182, CVE-2026-6638: Properly quote object names in
    logical replication origin checks
  * https://www.postgresql.org/docs/release/16.13/</changelog>
</package>
<package pkgid="5f60e0b073961c196b8ce005a5ad90245985781abaff64b84a3b0e9fe8175fe90f368402e01bf08bf4c7761ae6d84d188256aca6a39295d1c7921163a23347dd" name="postgresql16-server" arch="aarch64">
  <version epoch="0" ver="16.13" rel="70.2"/>
  <changelog author="Aaron Puchert &lt;aaronpuchert@alice-dsl.net&gt;" date="1710244800">- Require LLVM &lt;= 17 for now, because LLVM 18 doesn't seem to work.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1715169600">- Upgrade to 16.3 (bsc#1224051):
  * bsc#1224038, CVE-2024-4317: Restrict visibility of pg_stats_ext
    and pg_stats_ext_exprs entries to the table owner. See the
    release notes for the steps that have to be taken to fix
    existing PostgreSQL instances.
  * Fix incompatibility with LLVM 18.
  * https://www.postgresql.org/docs/release/16.3/
- Prepare for PostgreSQL 17.
- Make sure all compilation and doc generation happens in %build.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1723291200">- Upgrade to 16.4 (bsc#1229013):
  * bsc#1229013, CVE-2024-7348 PostgreSQL relation replacement
    during pg_dump executes arbitrary SQL
  * https://www.postgresql.org/about/news/p-2910/
  * https://www.postgresql.org/docs/release/16.4/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1726747200">- Don't build the libs and mini flavor anymore to hand over to
  PostgreSQL 17.</changelog>
  <changelog author="Antonio Teixeira &lt;antonio.teixeira@suse.com&gt;" date="1726833600">- Pull upstream patch to fix tests with timezone 2024b
  * postgresql-testsuite-timezone-fix.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1730808000">- Sync spec file from postgresql17.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1731499200">- Upgrade to 16.5:
  * CVE-2024-10976, bsc#1233323: Ensure cached plans are marked as
    dependent on the calling role when RLS applies to a
    non-top-level table reference.
  * CVE-2024-10977, bsc#1233325: Make libpq discard error messages
    received during SSL or GSS protocol negotiation.
  * CVE-2024-10978, bsc#1233326: Fix unintended interactions
    between SET SESSION AUTHORIZATION and SET ROLE
  * CVE-2024-10979, bsc#1233327: Prevent trusted PL/Perl code from
    changing environment variables.
  * obsoletes postgresql-testsuite-timezone-fix.patch
  * https://www.postgresql.org/about/news/p-2955/
  * https://www.postgresql.org/docs/release/16.5/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1732017600">- Upgrade to 16.6:
  * Repair ABI break for extensions that work with struct
    ResultRelInfo.
  * Restore functionality of ALTER {ROLE|DATABASE} SET role.
  * Fix cases where a logical replication slot's restart_lsn could
    go backwards.
  * Avoid deleting still-needed WAL files during pg_rewind.
  * Fix race conditions associated with dropping shared statistics
    entries.
  * Count index scans in contrib/bloom indexes in the statistics
    views, such as the pg_stat_user_indexes.idx_scan counter.
  * Fix crash when checking to see if an index's opclass options
    have changed.
  * Avoid assertion failure caused by disconnected NFA sub-graphs
    in regular expression parsing.
  * https://www.postgresql.org/about/news/p-2965/
  * https://www.postgresql.org/docs/release/16.6/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 16.7:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/16.7/
  * https://www.postgresql.org/about/news/-3015/
- Disable LLVM JIT on loongarch64</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 16.8:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/16.8/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 16.9:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/16.9/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to Fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Upgrade to 16.10:
  * https://www.postgresql.org/about/news/postgresql-176-1610-1514-1419-1322-and-18-beta-3-released-3118/
  * https://www.postgresql.org/docs/release/16.10/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1758628800">- Sync spec file from version 18.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Upgrade to 16.11:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/16.11/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 16.12:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/16.12/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 16.13 to fix two regressions in 16.12:
  * https://www.postgresql.org/docs/release/16.13/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
</package>
<package pkgid="73206005cb1a9ab2437100056dbd94199f3f1dc394d257799cc7e70e4e85de60d90c7e1e627ea846d8aee611d7f12dc7d2546136fb2be2a3a5a1152ffa6dff6f" name="postgresql16-server" arch="ppc64le">
  <version epoch="0" ver="16.13" rel="70.2"/>
  <changelog author="Aaron Puchert &lt;aaronpuchert@alice-dsl.net&gt;" date="1710244800">- Require LLVM &lt;= 17 for now, because LLVM 18 doesn't seem to work.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1715169600">- Upgrade to 16.3 (bsc#1224051):
  * bsc#1224038, CVE-2024-4317: Restrict visibility of pg_stats_ext
    and pg_stats_ext_exprs entries to the table owner. See the
    release notes for the steps that have to be taken to fix
    existing PostgreSQL instances.
  * Fix incompatibility with LLVM 18.
  * https://www.postgresql.org/docs/release/16.3/
- Prepare for PostgreSQL 17.
- Make sure all compilation and doc generation happens in %build.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1723291200">- Upgrade to 16.4 (bsc#1229013):
  * bsc#1229013, CVE-2024-7348 PostgreSQL relation replacement
    during pg_dump executes arbitrary SQL
  * https://www.postgresql.org/about/news/p-2910/
  * https://www.postgresql.org/docs/release/16.4/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1726747200">- Don't build the libs and mini flavor anymore to hand over to
  PostgreSQL 17.</changelog>
  <changelog author="Antonio Teixeira &lt;antonio.teixeira@suse.com&gt;" date="1726833600">- Pull upstream patch to fix tests with timezone 2024b
  * postgresql-testsuite-timezone-fix.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1730808000">- Sync spec file from postgresql17.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1731499200">- Upgrade to 16.5:
  * CVE-2024-10976, bsc#1233323: Ensure cached plans are marked as
    dependent on the calling role when RLS applies to a
    non-top-level table reference.
  * CVE-2024-10977, bsc#1233325: Make libpq discard error messages
    received during SSL or GSS protocol negotiation.
  * CVE-2024-10978, bsc#1233326: Fix unintended interactions
    between SET SESSION AUTHORIZATION and SET ROLE
  * CVE-2024-10979, bsc#1233327: Prevent trusted PL/Perl code from
    changing environment variables.
  * obsoletes postgresql-testsuite-timezone-fix.patch
  * https://www.postgresql.org/about/news/p-2955/
  * https://www.postgresql.org/docs/release/16.5/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1732017600">- Upgrade to 16.6:
  * Repair ABI break for extensions that work with struct
    ResultRelInfo.
  * Restore functionality of ALTER {ROLE|DATABASE} SET role.
  * Fix cases where a logical replication slot's restart_lsn could
    go backwards.
  * Avoid deleting still-needed WAL files during pg_rewind.
  * Fix race conditions associated with dropping shared statistics
    entries.
  * Count index scans in contrib/bloom indexes in the statistics
    views, such as the pg_stat_user_indexes.idx_scan counter.
  * Fix crash when checking to see if an index's opclass options
    have changed.
  * Avoid assertion failure caused by disconnected NFA sub-graphs
    in regular expression parsing.
  * https://www.postgresql.org/about/news/p-2965/
  * https://www.postgresql.org/docs/release/16.6/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 16.7:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/16.7/
  * https://www.postgresql.org/about/news/-3015/
- Disable LLVM JIT on loongarch64</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 16.8:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/16.8/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 16.9:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/16.9/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to Fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Upgrade to 16.10:
  * https://www.postgresql.org/about/news/postgresql-176-1610-1514-1419-1322-and-18-beta-3-released-3118/
  * https://www.postgresql.org/docs/release/16.10/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1758628800">- Sync spec file from version 18.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Upgrade to 16.11:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/16.11/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 16.12:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/16.12/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 16.13 to fix two regressions in 16.12:
  * https://www.postgresql.org/docs/release/16.13/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
</package>
<package pkgid="9d961234b2645559b550b7d6d5f8624f9fc686b610b97c035d0ef55cb0b786e7af8762d5bdd0690e967377ec4cab210933cd2e2849fc7aabd1d5b3e8481f00dc" name="postgresql16-server" arch="s390x">
  <version epoch="0" ver="16.13" rel="70.2"/>
  <changelog author="Aaron Puchert &lt;aaronpuchert@alice-dsl.net&gt;" date="1710244800">- Require LLVM &lt;= 17 for now, because LLVM 18 doesn't seem to work.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1715169600">- Upgrade to 16.3 (bsc#1224051):
  * bsc#1224038, CVE-2024-4317: Restrict visibility of pg_stats_ext
    and pg_stats_ext_exprs entries to the table owner. See the
    release notes for the steps that have to be taken to fix
    existing PostgreSQL instances.
  * Fix incompatibility with LLVM 18.
  * https://www.postgresql.org/docs/release/16.3/
- Prepare for PostgreSQL 17.
- Make sure all compilation and doc generation happens in %build.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1723291200">- Upgrade to 16.4 (bsc#1229013):
  * bsc#1229013, CVE-2024-7348 PostgreSQL relation replacement
    during pg_dump executes arbitrary SQL
  * https://www.postgresql.org/about/news/p-2910/
  * https://www.postgresql.org/docs/release/16.4/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1726747200">- Don't build the libs and mini flavor anymore to hand over to
  PostgreSQL 17.</changelog>
  <changelog author="Antonio Teixeira &lt;antonio.teixeira@suse.com&gt;" date="1726833600">- Pull upstream patch to fix tests with timezone 2024b
  * postgresql-testsuite-timezone-fix.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1730808000">- Sync spec file from postgresql17.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1731499200">- Upgrade to 16.5:
  * CVE-2024-10976, bsc#1233323: Ensure cached plans are marked as
    dependent on the calling role when RLS applies to a
    non-top-level table reference.
  * CVE-2024-10977, bsc#1233325: Make libpq discard error messages
    received during SSL or GSS protocol negotiation.
  * CVE-2024-10978, bsc#1233326: Fix unintended interactions
    between SET SESSION AUTHORIZATION and SET ROLE
  * CVE-2024-10979, bsc#1233327: Prevent trusted PL/Perl code from
    changing environment variables.
  * obsoletes postgresql-testsuite-timezone-fix.patch
  * https://www.postgresql.org/about/news/p-2955/
  * https://www.postgresql.org/docs/release/16.5/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1732017600">- Upgrade to 16.6:
  * Repair ABI break for extensions that work with struct
    ResultRelInfo.
  * Restore functionality of ALTER {ROLE|DATABASE} SET role.
  * Fix cases where a logical replication slot's restart_lsn could
    go backwards.
  * Avoid deleting still-needed WAL files during pg_rewind.
  * Fix race conditions associated with dropping shared statistics
    entries.
  * Count index scans in contrib/bloom indexes in the statistics
    views, such as the pg_stat_user_indexes.idx_scan counter.
  * Fix crash when checking to see if an index's opclass options
    have changed.
  * Avoid assertion failure caused by disconnected NFA sub-graphs
    in regular expression parsing.
  * https://www.postgresql.org/about/news/p-2965/
  * https://www.postgresql.org/docs/release/16.6/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 16.7:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/16.7/
  * https://www.postgresql.org/about/news/-3015/
- Disable LLVM JIT on loongarch64</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 16.8:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/16.8/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 16.9:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/16.9/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to Fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Upgrade to 16.10:
  * https://www.postgresql.org/about/news/postgresql-176-1610-1514-1419-1322-and-18-beta-3-released-3118/
  * https://www.postgresql.org/docs/release/16.10/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1758628800">- Sync spec file from version 18.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Upgrade to 16.11:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/16.11/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 16.12:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/16.12/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 16.13 to fix two regressions in 16.12:
  * https://www.postgresql.org/docs/release/16.13/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
</package>
<package pkgid="5fc2fe850bf752ed7d5cc85dd16afaa68321010e2b96eb4875d7eee6750d8116a414c8a7dfd5e154fb9053f2b344532b742a03a70304fb4039eefe37e9dbcc5c" name="postgresql16-server" arch="x86_64">
  <version epoch="0" ver="16.14" rel="80.2"/>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1726747200">- Don't build the libs and mini flavor anymore to hand over to
  PostgreSQL 17.</changelog>
  <changelog author="Antonio Teixeira &lt;antonio.teixeira@suse.com&gt;" date="1726833600">- Pull upstream patch to fix tests with timezone 2024b
  * postgresql-testsuite-timezone-fix.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1730808000">- Sync spec file from postgresql17.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1731499200">- Upgrade to 16.5:
  * CVE-2024-10976, bsc#1233323: Ensure cached plans are marked as
    dependent on the calling role when RLS applies to a
    non-top-level table reference.
  * CVE-2024-10977, bsc#1233325: Make libpq discard error messages
    received during SSL or GSS protocol negotiation.
  * CVE-2024-10978, bsc#1233326: Fix unintended interactions
    between SET SESSION AUTHORIZATION and SET ROLE
  * CVE-2024-10979, bsc#1233327: Prevent trusted PL/Perl code from
    changing environment variables.
  * obsoletes postgresql-testsuite-timezone-fix.patch
  * https://www.postgresql.org/about/news/p-2955/
  * https://www.postgresql.org/docs/release/16.5/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1732017600">- Upgrade to 16.6:
  * Repair ABI break for extensions that work with struct
    ResultRelInfo.
  * Restore functionality of ALTER {ROLE|DATABASE} SET role.
  * Fix cases where a logical replication slot's restart_lsn could
    go backwards.
  * Avoid deleting still-needed WAL files during pg_rewind.
  * Fix race conditions associated with dropping shared statistics
    entries.
  * Count index scans in contrib/bloom indexes in the statistics
    views, such as the pg_stat_user_indexes.idx_scan counter.
  * Fix crash when checking to see if an index's opclass options
    have changed.
  * Avoid assertion failure caused by disconnected NFA sub-graphs
    in regular expression parsing.
  * https://www.postgresql.org/about/news/p-2965/
  * https://www.postgresql.org/docs/release/16.6/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 16.7:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/16.7/
  * https://www.postgresql.org/about/news/-3015/
- Disable LLVM JIT on loongarch64</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 16.8:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/16.8/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 16.9:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/16.9/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to Fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Upgrade to 16.10:
  * https://www.postgresql.org/about/news/postgresql-176-1610-1514-1419-1322-and-18-beta-3-released-3118/
  * https://www.postgresql.org/docs/release/16.10/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1758628800">- Sync spec file from version 18.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Upgrade to 16.11:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/16.11/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 16.12:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/16.12/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 16.13 to fix two regressions in 16.12:
  * https://www.postgresql.org/docs/release/16.13/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1774872000">- Get rid of update-alternatives for openSUSE/SLE 16.0 and newer
  to support immutable systems and transactional updates.
  (jsc#PED-14824)</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1777550400">- bsc#1263804: After dropping update-alternatives we have to
  package /usr/bin/pg_config as an actual symlink, not %ghost.
- Fix spelling of build conditionals.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1778673600">- Update to version 16.13:
  * bsc#1265172, CVE-2026-6472: ensure the user has CREATE
    privilege on the schema specified
  * bsc#1265173, CVE-2026-6473: integer overflows in
    memory-allocation calculations
  * bsc#1265174, CVE-2026-6474: Guard against malicious time zone
    names
  * bsc#1265175, CVE-2026-6475: Prevent path traversal in
    pg_basebackup and pg_rewind
  * bsc#1265177, CVE-2026-6477: Mark PQfn() as unsafe, and avoid
    using it within libpq
  * bsc#1265178, CVE-2026-6478: Use timing-safe string comparisons
    in authentication code
  * bsc#1265179, CVE-2026-6479: Prevent unbounded recursion while
    processing startup packets
  * bsc#1265181, CVE-2026-6637: Prevent SQL injection and buffer
    overruns in contrib/spi
  * bsc#1265182, CVE-2026-6638: Properly quote object names in
    logical replication origin checks
  * https://www.postgresql.org/docs/release/16.13/</changelog>
</package>
<package pkgid="59da2d088aab2b378078df9545e77bad537e48d5845ca8ea21345c96169c84208d572e9972101e71b190d4b25aceb7113491ab3929122985ca258b2b2dd662d7" name="postgresql16-server-devel" arch="aarch64">
  <version epoch="0" ver="16.13" rel="70.2"/>
  <changelog author="Aaron Puchert &lt;aaronpuchert@alice-dsl.net&gt;" date="1710244800">- Require LLVM &lt;= 17 for now, because LLVM 18 doesn't seem to work.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1715169600">- Upgrade to 16.3 (bsc#1224051):
  * bsc#1224038, CVE-2024-4317: Restrict visibility of pg_stats_ext
    and pg_stats_ext_exprs entries to the table owner. See the
    release notes for the steps that have to be taken to fix
    existing PostgreSQL instances.
  * Fix incompatibility with LLVM 18.
  * https://www.postgresql.org/docs/release/16.3/
- Prepare for PostgreSQL 17.
- Make sure all compilation and doc generation happens in %build.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1723291200">- Upgrade to 16.4 (bsc#1229013):
  * bsc#1229013, CVE-2024-7348 PostgreSQL relation replacement
    during pg_dump executes arbitrary SQL
  * https://www.postgresql.org/about/news/p-2910/
  * https://www.postgresql.org/docs/release/16.4/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1726747200">- Don't build the libs and mini flavor anymore to hand over to
  PostgreSQL 17.</changelog>
  <changelog author="Antonio Teixeira &lt;antonio.teixeira@suse.com&gt;" date="1726833600">- Pull upstream patch to fix tests with timezone 2024b
  * postgresql-testsuite-timezone-fix.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1730808000">- Sync spec file from postgresql17.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1731499200">- Upgrade to 16.5:
  * CVE-2024-10976, bsc#1233323: Ensure cached plans are marked as
    dependent on the calling role when RLS applies to a
    non-top-level table reference.
  * CVE-2024-10977, bsc#1233325: Make libpq discard error messages
    received during SSL or GSS protocol negotiation.
  * CVE-2024-10978, bsc#1233326: Fix unintended interactions
    between SET SESSION AUTHORIZATION and SET ROLE
  * CVE-2024-10979, bsc#1233327: Prevent trusted PL/Perl code from
    changing environment variables.
  * obsoletes postgresql-testsuite-timezone-fix.patch
  * https://www.postgresql.org/about/news/p-2955/
  * https://www.postgresql.org/docs/release/16.5/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1732017600">- Upgrade to 16.6:
  * Repair ABI break for extensions that work with struct
    ResultRelInfo.
  * Restore functionality of ALTER {ROLE|DATABASE} SET role.
  * Fix cases where a logical replication slot's restart_lsn could
    go backwards.
  * Avoid deleting still-needed WAL files during pg_rewind.
  * Fix race conditions associated with dropping shared statistics
    entries.
  * Count index scans in contrib/bloom indexes in the statistics
    views, such as the pg_stat_user_indexes.idx_scan counter.
  * Fix crash when checking to see if an index's opclass options
    have changed.
  * Avoid assertion failure caused by disconnected NFA sub-graphs
    in regular expression parsing.
  * https://www.postgresql.org/about/news/p-2965/
  * https://www.postgresql.org/docs/release/16.6/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 16.7:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/16.7/
  * https://www.postgresql.org/about/news/-3015/
- Disable LLVM JIT on loongarch64</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 16.8:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/16.8/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 16.9:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/16.9/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to Fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Upgrade to 16.10:
  * https://www.postgresql.org/about/news/postgresql-176-1610-1514-1419-1322-and-18-beta-3-released-3118/
  * https://www.postgresql.org/docs/release/16.10/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1758628800">- Sync spec file from version 18.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Upgrade to 16.11:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/16.11/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 16.12:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/16.12/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 16.13 to fix two regressions in 16.12:
  * https://www.postgresql.org/docs/release/16.13/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
</package>
<package pkgid="1a558b983ee2332ca05f24eabf81472a265328b72edb6e4e1060651fa26c8dc993769163af074dddf47f9a92e4a7fa529b27a8939f2a26cabda56fee4382143f" name="postgresql16-server-devel" arch="ppc64le">
  <version epoch="0" ver="16.13" rel="70.2"/>
  <changelog author="Aaron Puchert &lt;aaronpuchert@alice-dsl.net&gt;" date="1710244800">- Require LLVM &lt;= 17 for now, because LLVM 18 doesn't seem to work.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1715169600">- Upgrade to 16.3 (bsc#1224051):
  * bsc#1224038, CVE-2024-4317: Restrict visibility of pg_stats_ext
    and pg_stats_ext_exprs entries to the table owner. See the
    release notes for the steps that have to be taken to fix
    existing PostgreSQL instances.
  * Fix incompatibility with LLVM 18.
  * https://www.postgresql.org/docs/release/16.3/
- Prepare for PostgreSQL 17.
- Make sure all compilation and doc generation happens in %build.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1723291200">- Upgrade to 16.4 (bsc#1229013):
  * bsc#1229013, CVE-2024-7348 PostgreSQL relation replacement
    during pg_dump executes arbitrary SQL
  * https://www.postgresql.org/about/news/p-2910/
  * https://www.postgresql.org/docs/release/16.4/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1726747200">- Don't build the libs and mini flavor anymore to hand over to
  PostgreSQL 17.</changelog>
  <changelog author="Antonio Teixeira &lt;antonio.teixeira@suse.com&gt;" date="1726833600">- Pull upstream patch to fix tests with timezone 2024b
  * postgresql-testsuite-timezone-fix.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1730808000">- Sync spec file from postgresql17.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1731499200">- Upgrade to 16.5:
  * CVE-2024-10976, bsc#1233323: Ensure cached plans are marked as
    dependent on the calling role when RLS applies to a
    non-top-level table reference.
  * CVE-2024-10977, bsc#1233325: Make libpq discard error messages
    received during SSL or GSS protocol negotiation.
  * CVE-2024-10978, bsc#1233326: Fix unintended interactions
    between SET SESSION AUTHORIZATION and SET ROLE
  * CVE-2024-10979, bsc#1233327: Prevent trusted PL/Perl code from
    changing environment variables.
  * obsoletes postgresql-testsuite-timezone-fix.patch
  * https://www.postgresql.org/about/news/p-2955/
  * https://www.postgresql.org/docs/release/16.5/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1732017600">- Upgrade to 16.6:
  * Repair ABI break for extensions that work with struct
    ResultRelInfo.
  * Restore functionality of ALTER {ROLE|DATABASE} SET role.
  * Fix cases where a logical replication slot's restart_lsn could
    go backwards.
  * Avoid deleting still-needed WAL files during pg_rewind.
  * Fix race conditions associated with dropping shared statistics
    entries.
  * Count index scans in contrib/bloom indexes in the statistics
    views, such as the pg_stat_user_indexes.idx_scan counter.
  * Fix crash when checking to see if an index's opclass options
    have changed.
  * Avoid assertion failure caused by disconnected NFA sub-graphs
    in regular expression parsing.
  * https://www.postgresql.org/about/news/p-2965/
  * https://www.postgresql.org/docs/release/16.6/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 16.7:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/16.7/
  * https://www.postgresql.org/about/news/-3015/
- Disable LLVM JIT on loongarch64</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 16.8:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/16.8/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 16.9:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/16.9/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to Fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Upgrade to 16.10:
  * https://www.postgresql.org/about/news/postgresql-176-1610-1514-1419-1322-and-18-beta-3-released-3118/
  * https://www.postgresql.org/docs/release/16.10/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1758628800">- Sync spec file from version 18.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Upgrade to 16.11:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/16.11/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 16.12:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/16.12/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 16.13 to fix two regressions in 16.12:
  * https://www.postgresql.org/docs/release/16.13/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
</package>
<package pkgid="e58cf148e98d40948cdebf55e30d14c49decb97df82362a38fc523159f99e5dbb5cd6669b4329dea749192e81a18ce2b4cefb753ab3feb042db2592651ab3f52" name="postgresql16-server-devel" arch="s390x">
  <version epoch="0" ver="16.13" rel="70.2"/>
  <changelog author="Aaron Puchert &lt;aaronpuchert@alice-dsl.net&gt;" date="1710244800">- Require LLVM &lt;= 17 for now, because LLVM 18 doesn't seem to work.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1715169600">- Upgrade to 16.3 (bsc#1224051):
  * bsc#1224038, CVE-2024-4317: Restrict visibility of pg_stats_ext
    and pg_stats_ext_exprs entries to the table owner. See the
    release notes for the steps that have to be taken to fix
    existing PostgreSQL instances.
  * Fix incompatibility with LLVM 18.
  * https://www.postgresql.org/docs/release/16.3/
- Prepare for PostgreSQL 17.
- Make sure all compilation and doc generation happens in %build.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1723291200">- Upgrade to 16.4 (bsc#1229013):
  * bsc#1229013, CVE-2024-7348 PostgreSQL relation replacement
    during pg_dump executes arbitrary SQL
  * https://www.postgresql.org/about/news/p-2910/
  * https://www.postgresql.org/docs/release/16.4/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1726747200">- Don't build the libs and mini flavor anymore to hand over to
  PostgreSQL 17.</changelog>
  <changelog author="Antonio Teixeira &lt;antonio.teixeira@suse.com&gt;" date="1726833600">- Pull upstream patch to fix tests with timezone 2024b
  * postgresql-testsuite-timezone-fix.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1730808000">- Sync spec file from postgresql17.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1731499200">- Upgrade to 16.5:
  * CVE-2024-10976, bsc#1233323: Ensure cached plans are marked as
    dependent on the calling role when RLS applies to a
    non-top-level table reference.
  * CVE-2024-10977, bsc#1233325: Make libpq discard error messages
    received during SSL or GSS protocol negotiation.
  * CVE-2024-10978, bsc#1233326: Fix unintended interactions
    between SET SESSION AUTHORIZATION and SET ROLE
  * CVE-2024-10979, bsc#1233327: Prevent trusted PL/Perl code from
    changing environment variables.
  * obsoletes postgresql-testsuite-timezone-fix.patch
  * https://www.postgresql.org/about/news/p-2955/
  * https://www.postgresql.org/docs/release/16.5/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1732017600">- Upgrade to 16.6:
  * Repair ABI break for extensions that work with struct
    ResultRelInfo.
  * Restore functionality of ALTER {ROLE|DATABASE} SET role.
  * Fix cases where a logical replication slot's restart_lsn could
    go backwards.
  * Avoid deleting still-needed WAL files during pg_rewind.
  * Fix race conditions associated with dropping shared statistics
    entries.
  * Count index scans in contrib/bloom indexes in the statistics
    views, such as the pg_stat_user_indexes.idx_scan counter.
  * Fix crash when checking to see if an index's opclass options
    have changed.
  * Avoid assertion failure caused by disconnected NFA sub-graphs
    in regular expression parsing.
  * https://www.postgresql.org/about/news/p-2965/
  * https://www.postgresql.org/docs/release/16.6/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 16.7:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/16.7/
  * https://www.postgresql.org/about/news/-3015/
- Disable LLVM JIT on loongarch64</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 16.8:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/16.8/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 16.9:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/16.9/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to Fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Upgrade to 16.10:
  * https://www.postgresql.org/about/news/postgresql-176-1610-1514-1419-1322-and-18-beta-3-released-3118/
  * https://www.postgresql.org/docs/release/16.10/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1758628800">- Sync spec file from version 18.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Upgrade to 16.11:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/16.11/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 16.12:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/16.12/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 16.13 to fix two regressions in 16.12:
  * https://www.postgresql.org/docs/release/16.13/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
</package>
<package pkgid="e029bb2a2f7828e2d5deaad34393c129ec1d63cb2822530ad6b96b914951ee720bd92756c6900e5e281e6d30934514cb5f31b4de1bdf39c3a823849f74364108" name="postgresql16-server-devel" arch="x86_64">
  <version epoch="0" ver="16.14" rel="80.2"/>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1726747200">- Don't build the libs and mini flavor anymore to hand over to
  PostgreSQL 17.</changelog>
  <changelog author="Antonio Teixeira &lt;antonio.teixeira@suse.com&gt;" date="1726833600">- Pull upstream patch to fix tests with timezone 2024b
  * postgresql-testsuite-timezone-fix.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1730808000">- Sync spec file from postgresql17.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1731499200">- Upgrade to 16.5:
  * CVE-2024-10976, bsc#1233323: Ensure cached plans are marked as
    dependent on the calling role when RLS applies to a
    non-top-level table reference.
  * CVE-2024-10977, bsc#1233325: Make libpq discard error messages
    received during SSL or GSS protocol negotiation.
  * CVE-2024-10978, bsc#1233326: Fix unintended interactions
    between SET SESSION AUTHORIZATION and SET ROLE
  * CVE-2024-10979, bsc#1233327: Prevent trusted PL/Perl code from
    changing environment variables.
  * obsoletes postgresql-testsuite-timezone-fix.patch
  * https://www.postgresql.org/about/news/p-2955/
  * https://www.postgresql.org/docs/release/16.5/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1732017600">- Upgrade to 16.6:
  * Repair ABI break for extensions that work with struct
    ResultRelInfo.
  * Restore functionality of ALTER {ROLE|DATABASE} SET role.
  * Fix cases where a logical replication slot's restart_lsn could
    go backwards.
  * Avoid deleting still-needed WAL files during pg_rewind.
  * Fix race conditions associated with dropping shared statistics
    entries.
  * Count index scans in contrib/bloom indexes in the statistics
    views, such as the pg_stat_user_indexes.idx_scan counter.
  * Fix crash when checking to see if an index's opclass options
    have changed.
  * Avoid assertion failure caused by disconnected NFA sub-graphs
    in regular expression parsing.
  * https://www.postgresql.org/about/news/p-2965/
  * https://www.postgresql.org/docs/release/16.6/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 16.7:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/16.7/
  * https://www.postgresql.org/about/news/-3015/
- Disable LLVM JIT on loongarch64</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 16.8:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/16.8/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 16.9:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/16.9/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to Fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Upgrade to 16.10:
  * https://www.postgresql.org/about/news/postgresql-176-1610-1514-1419-1322-and-18-beta-3-released-3118/
  * https://www.postgresql.org/docs/release/16.10/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1758628800">- Sync spec file from version 18.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Upgrade to 16.11:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/16.11/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 16.12:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/16.12/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 16.13 to fix two regressions in 16.12:
  * https://www.postgresql.org/docs/release/16.13/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1774872000">- Get rid of update-alternatives for openSUSE/SLE 16.0 and newer
  to support immutable systems and transactional updates.
  (jsc#PED-14824)</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1777550400">- bsc#1263804: After dropping update-alternatives we have to
  package /usr/bin/pg_config as an actual symlink, not %ghost.
- Fix spelling of build conditionals.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1778673600">- Update to version 16.13:
  * bsc#1265172, CVE-2026-6472: ensure the user has CREATE
    privilege on the schema specified
  * bsc#1265173, CVE-2026-6473: integer overflows in
    memory-allocation calculations
  * bsc#1265174, CVE-2026-6474: Guard against malicious time zone
    names
  * bsc#1265175, CVE-2026-6475: Prevent path traversal in
    pg_basebackup and pg_rewind
  * bsc#1265177, CVE-2026-6477: Mark PQfn() as unsafe, and avoid
    using it within libpq
  * bsc#1265178, CVE-2026-6478: Use timing-safe string comparisons
    in authentication code
  * bsc#1265179, CVE-2026-6479: Prevent unbounded recursion while
    processing startup packets
  * bsc#1265181, CVE-2026-6637: Prevent SQL injection and buffer
    overruns in contrib/spi
  * bsc#1265182, CVE-2026-6638: Properly quote object names in
    logical replication origin checks
  * https://www.postgresql.org/docs/release/16.13/</changelog>
</package>
<package pkgid="c89caffd26c22ba63cb04669a3b4d7c92b27def53ca522ce3be6bb6b52cb11086df8e1e9bc1e6c84a255138c0d694ac98bc05a643e15746d4780f069b6ab0471" name="postgresql16-test" arch="aarch64">
  <version epoch="0" ver="16.13" rel="70.2"/>
  <changelog author="Aaron Puchert &lt;aaronpuchert@alice-dsl.net&gt;" date="1710244800">- Require LLVM &lt;= 17 for now, because LLVM 18 doesn't seem to work.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1715169600">- Upgrade to 16.3 (bsc#1224051):
  * bsc#1224038, CVE-2024-4317: Restrict visibility of pg_stats_ext
    and pg_stats_ext_exprs entries to the table owner. See the
    release notes for the steps that have to be taken to fix
    existing PostgreSQL instances.
  * Fix incompatibility with LLVM 18.
  * https://www.postgresql.org/docs/release/16.3/
- Prepare for PostgreSQL 17.
- Make sure all compilation and doc generation happens in %build.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1723291200">- Upgrade to 16.4 (bsc#1229013):
  * bsc#1229013, CVE-2024-7348 PostgreSQL relation replacement
    during pg_dump executes arbitrary SQL
  * https://www.postgresql.org/about/news/p-2910/
  * https://www.postgresql.org/docs/release/16.4/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1726747200">- Don't build the libs and mini flavor anymore to hand over to
  PostgreSQL 17.</changelog>
  <changelog author="Antonio Teixeira &lt;antonio.teixeira@suse.com&gt;" date="1726833600">- Pull upstream patch to fix tests with timezone 2024b
  * postgresql-testsuite-timezone-fix.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1730808000">- Sync spec file from postgresql17.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1731499200">- Upgrade to 16.5:
  * CVE-2024-10976, bsc#1233323: Ensure cached plans are marked as
    dependent on the calling role when RLS applies to a
    non-top-level table reference.
  * CVE-2024-10977, bsc#1233325: Make libpq discard error messages
    received during SSL or GSS protocol negotiation.
  * CVE-2024-10978, bsc#1233326: Fix unintended interactions
    between SET SESSION AUTHORIZATION and SET ROLE
  * CVE-2024-10979, bsc#1233327: Prevent trusted PL/Perl code from
    changing environment variables.
  * obsoletes postgresql-testsuite-timezone-fix.patch
  * https://www.postgresql.org/about/news/p-2955/
  * https://www.postgresql.org/docs/release/16.5/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1732017600">- Upgrade to 16.6:
  * Repair ABI break for extensions that work with struct
    ResultRelInfo.
  * Restore functionality of ALTER {ROLE|DATABASE} SET role.
  * Fix cases where a logical replication slot's restart_lsn could
    go backwards.
  * Avoid deleting still-needed WAL files during pg_rewind.
  * Fix race conditions associated with dropping shared statistics
    entries.
  * Count index scans in contrib/bloom indexes in the statistics
    views, such as the pg_stat_user_indexes.idx_scan counter.
  * Fix crash when checking to see if an index's opclass options
    have changed.
  * Avoid assertion failure caused by disconnected NFA sub-graphs
    in regular expression parsing.
  * https://www.postgresql.org/about/news/p-2965/
  * https://www.postgresql.org/docs/release/16.6/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 16.7:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/16.7/
  * https://www.postgresql.org/about/news/-3015/
- Disable LLVM JIT on loongarch64</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 16.8:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/16.8/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 16.9:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/16.9/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to Fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Upgrade to 16.10:
  * https://www.postgresql.org/about/news/postgresql-176-1610-1514-1419-1322-and-18-beta-3-released-3118/
  * https://www.postgresql.org/docs/release/16.10/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1758628800">- Sync spec file from version 18.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Upgrade to 16.11:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/16.11/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 16.12:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/16.12/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 16.13 to fix two regressions in 16.12:
  * https://www.postgresql.org/docs/release/16.13/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
</package>
<package pkgid="06ef4b1553f31b1ba8759d26d13eff114b22b2300f0bfcfdc13522e4e2b6b4b2d6e980856a90da9a075de2cfc562c9d6eac310e58848e914a78fd04dee0f269a" name="postgresql16-test" arch="ppc64le">
  <version epoch="0" ver="16.13" rel="70.2"/>
  <changelog author="Aaron Puchert &lt;aaronpuchert@alice-dsl.net&gt;" date="1710244800">- Require LLVM &lt;= 17 for now, because LLVM 18 doesn't seem to work.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1715169600">- Upgrade to 16.3 (bsc#1224051):
  * bsc#1224038, CVE-2024-4317: Restrict visibility of pg_stats_ext
    and pg_stats_ext_exprs entries to the table owner. See the
    release notes for the steps that have to be taken to fix
    existing PostgreSQL instances.
  * Fix incompatibility with LLVM 18.
  * https://www.postgresql.org/docs/release/16.3/
- Prepare for PostgreSQL 17.
- Make sure all compilation and doc generation happens in %build.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1723291200">- Upgrade to 16.4 (bsc#1229013):
  * bsc#1229013, CVE-2024-7348 PostgreSQL relation replacement
    during pg_dump executes arbitrary SQL
  * https://www.postgresql.org/about/news/p-2910/
  * https://www.postgresql.org/docs/release/16.4/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1726747200">- Don't build the libs and mini flavor anymore to hand over to
  PostgreSQL 17.</changelog>
  <changelog author="Antonio Teixeira &lt;antonio.teixeira@suse.com&gt;" date="1726833600">- Pull upstream patch to fix tests with timezone 2024b
  * postgresql-testsuite-timezone-fix.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1730808000">- Sync spec file from postgresql17.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1731499200">- Upgrade to 16.5:
  * CVE-2024-10976, bsc#1233323: Ensure cached plans are marked as
    dependent on the calling role when RLS applies to a
    non-top-level table reference.
  * CVE-2024-10977, bsc#1233325: Make libpq discard error messages
    received during SSL or GSS protocol negotiation.
  * CVE-2024-10978, bsc#1233326: Fix unintended interactions
    between SET SESSION AUTHORIZATION and SET ROLE
  * CVE-2024-10979, bsc#1233327: Prevent trusted PL/Perl code from
    changing environment variables.
  * obsoletes postgresql-testsuite-timezone-fix.patch
  * https://www.postgresql.org/about/news/p-2955/
  * https://www.postgresql.org/docs/release/16.5/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1732017600">- Upgrade to 16.6:
  * Repair ABI break for extensions that work with struct
    ResultRelInfo.
  * Restore functionality of ALTER {ROLE|DATABASE} SET role.
  * Fix cases where a logical replication slot's restart_lsn could
    go backwards.
  * Avoid deleting still-needed WAL files during pg_rewind.
  * Fix race conditions associated with dropping shared statistics
    entries.
  * Count index scans in contrib/bloom indexes in the statistics
    views, such as the pg_stat_user_indexes.idx_scan counter.
  * Fix crash when checking to see if an index's opclass options
    have changed.
  * Avoid assertion failure caused by disconnected NFA sub-graphs
    in regular expression parsing.
  * https://www.postgresql.org/about/news/p-2965/
  * https://www.postgresql.org/docs/release/16.6/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 16.7:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/16.7/
  * https://www.postgresql.org/about/news/-3015/
- Disable LLVM JIT on loongarch64</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 16.8:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/16.8/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 16.9:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/16.9/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to Fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Upgrade to 16.10:
  * https://www.postgresql.org/about/news/postgresql-176-1610-1514-1419-1322-and-18-beta-3-released-3118/
  * https://www.postgresql.org/docs/release/16.10/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1758628800">- Sync spec file from version 18.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Upgrade to 16.11:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/16.11/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 16.12:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/16.12/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 16.13 to fix two regressions in 16.12:
  * https://www.postgresql.org/docs/release/16.13/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
</package>
<package pkgid="2e9df322a4433df041781a827a09e3375c3f57fb58b23c2ea53993d991ab6e7979ab484bdcf2772c8ea426750ddb319317c550112ede15f29a025f8b67639014" name="postgresql16-test" arch="s390x">
  <version epoch="0" ver="16.13" rel="70.2"/>
  <changelog author="Aaron Puchert &lt;aaronpuchert@alice-dsl.net&gt;" date="1710244800">- Require LLVM &lt;= 17 for now, because LLVM 18 doesn't seem to work.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1715169600">- Upgrade to 16.3 (bsc#1224051):
  * bsc#1224038, CVE-2024-4317: Restrict visibility of pg_stats_ext
    and pg_stats_ext_exprs entries to the table owner. See the
    release notes for the steps that have to be taken to fix
    existing PostgreSQL instances.
  * Fix incompatibility with LLVM 18.
  * https://www.postgresql.org/docs/release/16.3/
- Prepare for PostgreSQL 17.
- Make sure all compilation and doc generation happens in %build.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1723291200">- Upgrade to 16.4 (bsc#1229013):
  * bsc#1229013, CVE-2024-7348 PostgreSQL relation replacement
    during pg_dump executes arbitrary SQL
  * https://www.postgresql.org/about/news/p-2910/
  * https://www.postgresql.org/docs/release/16.4/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1726747200">- Don't build the libs and mini flavor anymore to hand over to
  PostgreSQL 17.</changelog>
  <changelog author="Antonio Teixeira &lt;antonio.teixeira@suse.com&gt;" date="1726833600">- Pull upstream patch to fix tests with timezone 2024b
  * postgresql-testsuite-timezone-fix.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1730808000">- Sync spec file from postgresql17.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1731499200">- Upgrade to 16.5:
  * CVE-2024-10976, bsc#1233323: Ensure cached plans are marked as
    dependent on the calling role when RLS applies to a
    non-top-level table reference.
  * CVE-2024-10977, bsc#1233325: Make libpq discard error messages
    received during SSL or GSS protocol negotiation.
  * CVE-2024-10978, bsc#1233326: Fix unintended interactions
    between SET SESSION AUTHORIZATION and SET ROLE
  * CVE-2024-10979, bsc#1233327: Prevent trusted PL/Perl code from
    changing environment variables.
  * obsoletes postgresql-testsuite-timezone-fix.patch
  * https://www.postgresql.org/about/news/p-2955/
  * https://www.postgresql.org/docs/release/16.5/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1732017600">- Upgrade to 16.6:
  * Repair ABI break for extensions that work with struct
    ResultRelInfo.
  * Restore functionality of ALTER {ROLE|DATABASE} SET role.
  * Fix cases where a logical replication slot's restart_lsn could
    go backwards.
  * Avoid deleting still-needed WAL files during pg_rewind.
  * Fix race conditions associated with dropping shared statistics
    entries.
  * Count index scans in contrib/bloom indexes in the statistics
    views, such as the pg_stat_user_indexes.idx_scan counter.
  * Fix crash when checking to see if an index's opclass options
    have changed.
  * Avoid assertion failure caused by disconnected NFA sub-graphs
    in regular expression parsing.
  * https://www.postgresql.org/about/news/p-2965/
  * https://www.postgresql.org/docs/release/16.6/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 16.7:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/16.7/
  * https://www.postgresql.org/about/news/-3015/
- Disable LLVM JIT on loongarch64</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 16.8:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/16.8/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 16.9:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/16.9/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to Fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Upgrade to 16.10:
  * https://www.postgresql.org/about/news/postgresql-176-1610-1514-1419-1322-and-18-beta-3-released-3118/
  * https://www.postgresql.org/docs/release/16.10/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1758628800">- Sync spec file from version 18.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Upgrade to 16.11:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/16.11/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 16.12:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/16.12/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 16.13 to fix two regressions in 16.12:
  * https://www.postgresql.org/docs/release/16.13/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
</package>
<package pkgid="296e546f49617513a93f1e3b6eb77d9859376ac70163eccd9ceee785ecb26f351fef22914f8cdb73a2ac60faf958d60a0f8849e8ef8cc190c3d190b3e3107c7c" name="postgresql16-test" arch="x86_64">
  <version epoch="0" ver="16.14" rel="80.2"/>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1726747200">- Don't build the libs and mini flavor anymore to hand over to
  PostgreSQL 17.</changelog>
  <changelog author="Antonio Teixeira &lt;antonio.teixeira@suse.com&gt;" date="1726833600">- Pull upstream patch to fix tests with timezone 2024b
  * postgresql-testsuite-timezone-fix.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1730808000">- Sync spec file from postgresql17.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1731499200">- Upgrade to 16.5:
  * CVE-2024-10976, bsc#1233323: Ensure cached plans are marked as
    dependent on the calling role when RLS applies to a
    non-top-level table reference.
  * CVE-2024-10977, bsc#1233325: Make libpq discard error messages
    received during SSL or GSS protocol negotiation.
  * CVE-2024-10978, bsc#1233326: Fix unintended interactions
    between SET SESSION AUTHORIZATION and SET ROLE
  * CVE-2024-10979, bsc#1233327: Prevent trusted PL/Perl code from
    changing environment variables.
  * obsoletes postgresql-testsuite-timezone-fix.patch
  * https://www.postgresql.org/about/news/p-2955/
  * https://www.postgresql.org/docs/release/16.5/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1732017600">- Upgrade to 16.6:
  * Repair ABI break for extensions that work with struct
    ResultRelInfo.
  * Restore functionality of ALTER {ROLE|DATABASE} SET role.
  * Fix cases where a logical replication slot's restart_lsn could
    go backwards.
  * Avoid deleting still-needed WAL files during pg_rewind.
  * Fix race conditions associated with dropping shared statistics
    entries.
  * Count index scans in contrib/bloom indexes in the statistics
    views, such as the pg_stat_user_indexes.idx_scan counter.
  * Fix crash when checking to see if an index's opclass options
    have changed.
  * Avoid assertion failure caused by disconnected NFA sub-graphs
    in regular expression parsing.
  * https://www.postgresql.org/about/news/p-2965/
  * https://www.postgresql.org/docs/release/16.6/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 16.7:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/16.7/
  * https://www.postgresql.org/about/news/-3015/
- Disable LLVM JIT on loongarch64</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 16.8:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/16.8/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 16.9:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/16.9/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to Fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Upgrade to 16.10:
  * https://www.postgresql.org/about/news/postgresql-176-1610-1514-1419-1322-and-18-beta-3-released-3118/
  * https://www.postgresql.org/docs/release/16.10/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1758628800">- Sync spec file from version 18.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Upgrade to 16.11:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/16.11/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 16.12:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/16.12/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 16.13 to fix two regressions in 16.12:
  * https://www.postgresql.org/docs/release/16.13/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1774872000">- Get rid of update-alternatives for openSUSE/SLE 16.0 and newer
  to support immutable systems and transactional updates.
  (jsc#PED-14824)</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1777550400">- bsc#1263804: After dropping update-alternatives we have to
  package /usr/bin/pg_config as an actual symlink, not %ghost.
- Fix spelling of build conditionals.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1778673600">- Update to version 16.13:
  * bsc#1265172, CVE-2026-6472: ensure the user has CREATE
    privilege on the schema specified
  * bsc#1265173, CVE-2026-6473: integer overflows in
    memory-allocation calculations
  * bsc#1265174, CVE-2026-6474: Guard against malicious time zone
    names
  * bsc#1265175, CVE-2026-6475: Prevent path traversal in
    pg_basebackup and pg_rewind
  * bsc#1265177, CVE-2026-6477: Mark PQfn() as unsafe, and avoid
    using it within libpq
  * bsc#1265178, CVE-2026-6478: Use timing-safe string comparisons
    in authentication code
  * bsc#1265179, CVE-2026-6479: Prevent unbounded recursion while
    processing startup packets
  * bsc#1265181, CVE-2026-6637: Prevent SQL injection and buffer
    overruns in contrib/spi
  * bsc#1265182, CVE-2026-6638: Properly quote object names in
    logical replication origin checks
  * https://www.postgresql.org/docs/release/16.13/</changelog>
</package>
<package pkgid="a11c53ec3566ae555fc817e5388bb946d214574c1d6e61c04f33921bc57c15b1190edc3a2ea3d81ddb3d6bc97dfb3cc399eb7887a111c6f5e059f3eaf7ddeda0" name="postgresql17" arch="src">
  <version epoch="0" ver="17.10" rel="69.2"/>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1731499200">- Upgrade to 17.1:
  * CVE-2024-10976, bsc#1233323: Ensure cached plans are marked as
    dependent on the calling role when RLS applies to a
    non-top-level table reference.
  * CVE-2024-10977, bsc#1233325: Make libpq discard error messages
    received during SSL or GSS protocol negotiation.
  * CVE-2024-10978, bsc#1233326: Fix unintended interactions
    between SET SESSION AUTHORIZATION and SET ROLE
  * CVE-2024-10979, bsc#1233327: Prevent trusted PL/Perl code from
    changing environment variables.
  * obsoletes postgresql17-jsonb_jsonpath.patch
  * https://www.postgresql.org/about/news/p-2955/
  * https://www.postgresql.org/docs/release/17.1/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1732017600">- Upgrade to 17.2:
  * Repair ABI break for extensions that work with struct
    ResultRelInfo.
  * Restore functionality of ALTER {ROLE|DATABASE} SET role.
  * Fix cases where a logical replication slot's restart_lsn could
    go backwards.
  * Avoid deleting still-needed WAL files during pg_rewind.
  * Fix race conditions associated with dropping shared statistics
    entries.
  * Count index scans in contrib/bloom indexes in the statistics
    views, such as the pg_stat_user_indexes.idx_scan counter.
  * Fix crash when checking to see if an index's opclass options
    have changed.
  * Avoid assertion failure caused by disconnected NFA sub-graphs
    in regular expression parsing.
  * https://www.postgresql.org/about/news/p-2965/
  * https://www.postgresql.org/docs/release/17.2/</changelog>
  <changelog author="JS &lt;obs.coke518@passinbox.com&gt;" date="1735214400">- Disable LLVM JIT on loongarch64</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="JS &lt;obs.coke518@passinbox.com&gt;" date="1738152000">- Apply postgresql-tzdata2025a.patch regardless of
  whether LLVM JIT is enabled</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 17.3:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/17.3/
  * https://www.postgresql.org/about/news/-3015/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 17.4:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/17.4/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 17.5:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/17.5/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to Fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Update to 17.6
  * https://www.postgresql.org/about/news/postgresql-176-1610-1514-1419-1322-and-18-beta-3-released-3118/
  * https://www.postgresql.org/docs/release/17.6/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1756036800">- switch library to pg 18</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1756987200">- Sync spec file with version 18.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Update to 17.7:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/17.7/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 17.8:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/17.8/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 17.9 to fix two regressions in 17.8:
  * https://www.postgresql.org/docs/release/17.9/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1774872000">- Get rid of update-alternatives for openSUSE/SLE 16.0 and newer
  to support immutable systems and transactional updates.
  (jsc#PED-14825, bsc#1245875)</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1777550400">- bsc#1263804: After dropping update-alternatives we have to
  package /usr/bin/pg_config as an actual symlink, not %ghost.
- Fix spelling of build conditionals.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1778673600">- Update to version 17.10:
  * bsc#1265172, CVE-2026-6472: ensure the user has CREATE
    privilege on the schema specified
  * bsc#1265173, CVE-2026-6473: integer overflows in
    memory-allocation calculations
  * bsc#1265174, CVE-2026-6474: Guard against malicious time zone
    names
  * bsc#1265175, CVE-2026-6475: Prevent path traversal in
    pg_basebackup and pg_rewind
  * bsc#1265176, CVE-2026-6476: Properly quote subscription names
    in pg_createsubscriber
  * bsc#1265177, CVE-2026-6477: Mark PQfn() as unsafe, and avoid
    using it within libpq
  * bsc#1265178, CVE-2026-6478: Use timing-safe string comparisons
    in authentication code
  * bsc#1265179, CVE-2026-6479: Prevent unbounded recursion while
    processing startup packets
  * bsc#1265181, CVE-2026-6637: Prevent SQL injection and buffer
    overruns in contrib/spi
  * bsc#1265182, CVE-2026-6638: Properly quote object names in
    logical replication origin checks
  * https://www.postgresql.org/docs/release/17.10/</changelog>
</package>
<package pkgid="16b93667beedff66be537dcdb9b4600f680719d19422c3ff40ed647f1effebc4bb8f5d2290fb4cbdbc2f0f07d89a22e2bd41785475f2af74783d49091c897924" name="postgresql17" arch="x86_64">
  <version epoch="0" ver="17.10" rel="69.2"/>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1731499200">- Upgrade to 17.1:
  * CVE-2024-10976, bsc#1233323: Ensure cached plans are marked as
    dependent on the calling role when RLS applies to a
    non-top-level table reference.
  * CVE-2024-10977, bsc#1233325: Make libpq discard error messages
    received during SSL or GSS protocol negotiation.
  * CVE-2024-10978, bsc#1233326: Fix unintended interactions
    between SET SESSION AUTHORIZATION and SET ROLE
  * CVE-2024-10979, bsc#1233327: Prevent trusted PL/Perl code from
    changing environment variables.
  * obsoletes postgresql17-jsonb_jsonpath.patch
  * https://www.postgresql.org/about/news/p-2955/
  * https://www.postgresql.org/docs/release/17.1/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1732017600">- Upgrade to 17.2:
  * Repair ABI break for extensions that work with struct
    ResultRelInfo.
  * Restore functionality of ALTER {ROLE|DATABASE} SET role.
  * Fix cases where a logical replication slot's restart_lsn could
    go backwards.
  * Avoid deleting still-needed WAL files during pg_rewind.
  * Fix race conditions associated with dropping shared statistics
    entries.
  * Count index scans in contrib/bloom indexes in the statistics
    views, such as the pg_stat_user_indexes.idx_scan counter.
  * Fix crash when checking to see if an index's opclass options
    have changed.
  * Avoid assertion failure caused by disconnected NFA sub-graphs
    in regular expression parsing.
  * https://www.postgresql.org/about/news/p-2965/
  * https://www.postgresql.org/docs/release/17.2/</changelog>
  <changelog author="JS &lt;obs.coke518@passinbox.com&gt;" date="1735214400">- Disable LLVM JIT on loongarch64</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="JS &lt;obs.coke518@passinbox.com&gt;" date="1738152000">- Apply postgresql-tzdata2025a.patch regardless of
  whether LLVM JIT is enabled</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 17.3:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/17.3/
  * https://www.postgresql.org/about/news/-3015/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 17.4:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/17.4/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 17.5:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/17.5/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to Fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Update to 17.6
  * https://www.postgresql.org/about/news/postgresql-176-1610-1514-1419-1322-and-18-beta-3-released-3118/
  * https://www.postgresql.org/docs/release/17.6/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1756036800">- switch library to pg 18</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1756987200">- Sync spec file with version 18.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Update to 17.7:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/17.7/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 17.8:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/17.8/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 17.9 to fix two regressions in 17.8:
  * https://www.postgresql.org/docs/release/17.9/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1774872000">- Get rid of update-alternatives for openSUSE/SLE 16.0 and newer
  to support immutable systems and transactional updates.
  (jsc#PED-14825, bsc#1245875)</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1777550400">- bsc#1263804: After dropping update-alternatives we have to
  package /usr/bin/pg_config as an actual symlink, not %ghost.
- Fix spelling of build conditionals.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1778673600">- Update to version 17.10:
  * bsc#1265172, CVE-2026-6472: ensure the user has CREATE
    privilege on the schema specified
  * bsc#1265173, CVE-2026-6473: integer overflows in
    memory-allocation calculations
  * bsc#1265174, CVE-2026-6474: Guard against malicious time zone
    names
  * bsc#1265175, CVE-2026-6475: Prevent path traversal in
    pg_basebackup and pg_rewind
  * bsc#1265176, CVE-2026-6476: Properly quote subscription names
    in pg_createsubscriber
  * bsc#1265177, CVE-2026-6477: Mark PQfn() as unsafe, and avoid
    using it within libpq
  * bsc#1265178, CVE-2026-6478: Use timing-safe string comparisons
    in authentication code
  * bsc#1265179, CVE-2026-6479: Prevent unbounded recursion while
    processing startup packets
  * bsc#1265181, CVE-2026-6637: Prevent SQL injection and buffer
    overruns in contrib/spi
  * bsc#1265182, CVE-2026-6638: Properly quote object names in
    logical replication origin checks
  * https://www.postgresql.org/docs/release/17.10/</changelog>
</package>
<package pkgid="151f3d2d3606532246e6310469d77321d999e8f373959e8300f23210e7c7e204c62f53613dc623f8f65394ffbb2873f31a6b379a1d3f32e895e032b3504fbc04" name="postgresql17" arch="s390x">
  <version epoch="0" ver="17.9" rel="53.1"/>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1727352000">- Upgrade to 17.0:
  * New memory management system for VACUUM, which reduces memory
    consumption and can improve overall vacuuming performance.
  * New SQL/JSON capabilities, including constructors, identity
    functions, and the JSON_TABLE() function, which converts JSON
    data into a table representation.
  * Various query performance improvements, including for
    sequential reads using streaming I/O, write throughput under
    high concurrency, and searches over multiple values in a btree
    index.
  * Logical replication enhancements, including:
    + Failover control
    + pg_createsubscriber, a utility that creates logical replicas
    from physical standbys
    + pg_upgrade now preserves replication slots on both publishers
    and subscribers
  * New client-side connection option, sslnegotiation=direct, that
    performs a direct TLS handshake to avoid a round-trip
    negotiation.
  * pg_basebackup now supports incremental backup.
  * COPY adds a new option, ON_ERROR ignore, that allows a copy
    operation to continue in the event of an error.
  * https://www.postgresql.org/about/news/p-2936/
  * https://www.postgresql.org/docs/17/release-17.html</changelog>
  <changelog author="Fabian Vogt &lt;fvogt@suse.com&gt;" date="1728302400">- Use cmake(LLVM) &lt; instead of &lt;= to also allow building against
  LLVM 18.1 and newer 18.x versions</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1730721600">- Add postgresql17-jsonb_jsonpath.patch as a temporary build fix.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1731499200">- Upgrade to 17.1:
  * CVE-2024-10976, bsc#1233323: Ensure cached plans are marked as
    dependent on the calling role when RLS applies to a
    non-top-level table reference.
  * CVE-2024-10977, bsc#1233325: Make libpq discard error messages
    received during SSL or GSS protocol negotiation.
  * CVE-2024-10978, bsc#1233326: Fix unintended interactions
    between SET SESSION AUTHORIZATION and SET ROLE
  * CVE-2024-10979, bsc#1233327: Prevent trusted PL/Perl code from
    changing environment variables.
  * obsoletes postgresql17-jsonb_jsonpath.patch
  * https://www.postgresql.org/about/news/p-2955/
  * https://www.postgresql.org/docs/release/17.1/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1732017600">- Upgrade to 17.2:
  * Repair ABI break for extensions that work with struct
    ResultRelInfo.
  * Restore functionality of ALTER {ROLE|DATABASE} SET role.
  * Fix cases where a logical replication slot's restart_lsn could
    go backwards.
  * Avoid deleting still-needed WAL files during pg_rewind.
  * Fix race conditions associated with dropping shared statistics
    entries.
  * Count index scans in contrib/bloom indexes in the statistics
    views, such as the pg_stat_user_indexes.idx_scan counter.
  * Fix crash when checking to see if an index's opclass options
    have changed.
  * Avoid assertion failure caused by disconnected NFA sub-graphs
    in regular expression parsing.
  * https://www.postgresql.org/about/news/p-2965/
  * https://www.postgresql.org/docs/release/17.2/</changelog>
  <changelog author="JS &lt;obs.coke518@passinbox.com&gt;" date="1735214400">- Disable LLVM JIT on loongarch64</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="JS &lt;obs.coke518@passinbox.com&gt;" date="1738152000">- Apply postgresql-tzdata2025a.patch regardless of
  whether LLVM JIT is enabled</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 17.3:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/17.3/
  * https://www.postgresql.org/about/news/-3015/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 17.4:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/17.4/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 17.5:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/17.5/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to Fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Update to 17.6
  * https://www.postgresql.org/about/news/postgresql-176-1610-1514-1419-1322-and-18-beta-3-released-3118/
  * https://www.postgresql.org/docs/release/17.6/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1756036800">- switch library to pg 18</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1756987200">- Sync spec file with version 18.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Update to 17.7:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/17.7/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 17.8:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/17.8/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 17.9 to fix two regressions in 17.8:
  * https://www.postgresql.org/docs/release/17.9/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
</package>
<package pkgid="95297e7df027ace3a515567cc17e2f918f223153abdf77f48354afadf1de4e1cdff2f0bb8d03356c7d9640266de80615c31e521eaa445e57923494b8075af0da" name="postgresql17" arch="src">
  <version epoch="0" ver="17.9" rel="53.1"/>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1727352000">- Upgrade to 17.0:
  * New memory management system for VACUUM, which reduces memory
    consumption and can improve overall vacuuming performance.
  * New SQL/JSON capabilities, including constructors, identity
    functions, and the JSON_TABLE() function, which converts JSON
    data into a table representation.
  * Various query performance improvements, including for
    sequential reads using streaming I/O, write throughput under
    high concurrency, and searches over multiple values in a btree
    index.
  * Logical replication enhancements, including:
    + Failover control
    + pg_createsubscriber, a utility that creates logical replicas
    from physical standbys
    + pg_upgrade now preserves replication slots on both publishers
    and subscribers
  * New client-side connection option, sslnegotiation=direct, that
    performs a direct TLS handshake to avoid a round-trip
    negotiation.
  * pg_basebackup now supports incremental backup.
  * COPY adds a new option, ON_ERROR ignore, that allows a copy
    operation to continue in the event of an error.
  * https://www.postgresql.org/about/news/p-2936/
  * https://www.postgresql.org/docs/17/release-17.html</changelog>
  <changelog author="Fabian Vogt &lt;fvogt@suse.com&gt;" date="1728302400">- Use cmake(LLVM) &lt; instead of &lt;= to also allow building against
  LLVM 18.1 and newer 18.x versions</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1730721600">- Add postgresql17-jsonb_jsonpath.patch as a temporary build fix.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1731499200">- Upgrade to 17.1:
  * CVE-2024-10976, bsc#1233323: Ensure cached plans are marked as
    dependent on the calling role when RLS applies to a
    non-top-level table reference.
  * CVE-2024-10977, bsc#1233325: Make libpq discard error messages
    received during SSL or GSS protocol negotiation.
  * CVE-2024-10978, bsc#1233326: Fix unintended interactions
    between SET SESSION AUTHORIZATION and SET ROLE
  * CVE-2024-10979, bsc#1233327: Prevent trusted PL/Perl code from
    changing environment variables.
  * obsoletes postgresql17-jsonb_jsonpath.patch
  * https://www.postgresql.org/about/news/p-2955/
  * https://www.postgresql.org/docs/release/17.1/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1732017600">- Upgrade to 17.2:
  * Repair ABI break for extensions that work with struct
    ResultRelInfo.
  * Restore functionality of ALTER {ROLE|DATABASE} SET role.
  * Fix cases where a logical replication slot's restart_lsn could
    go backwards.
  * Avoid deleting still-needed WAL files during pg_rewind.
  * Fix race conditions associated with dropping shared statistics
    entries.
  * Count index scans in contrib/bloom indexes in the statistics
    views, such as the pg_stat_user_indexes.idx_scan counter.
  * Fix crash when checking to see if an index's opclass options
    have changed.
  * Avoid assertion failure caused by disconnected NFA sub-graphs
    in regular expression parsing.
  * https://www.postgresql.org/about/news/p-2965/
  * https://www.postgresql.org/docs/release/17.2/</changelog>
  <changelog author="JS &lt;obs.coke518@passinbox.com&gt;" date="1735214400">- Disable LLVM JIT on loongarch64</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="JS &lt;obs.coke518@passinbox.com&gt;" date="1738152000">- Apply postgresql-tzdata2025a.patch regardless of
  whether LLVM JIT is enabled</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 17.3:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/17.3/
  * https://www.postgresql.org/about/news/-3015/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 17.4:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/17.4/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 17.5:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/17.5/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to Fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Update to 17.6
  * https://www.postgresql.org/about/news/postgresql-176-1610-1514-1419-1322-and-18-beta-3-released-3118/
  * https://www.postgresql.org/docs/release/17.6/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1756036800">- switch library to pg 18</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1756987200">- Sync spec file with version 18.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Update to 17.7:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/17.7/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 17.8:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/17.8/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 17.9 to fix two regressions in 17.8:
  * https://www.postgresql.org/docs/release/17.9/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
</package>
<package pkgid="9d30b20e3f617f298b6c94c5918cb5a5b39c43f8c7c22a1227cc3d77fd7533e8190716750150ebb1fccc225091e000440153f46f3dbf096ed617965dbf9bfd1d" name="postgresql17" arch="aarch64">
  <version epoch="0" ver="17.9" rel="54.2"/>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1727352000">- Upgrade to 17.0:
  * New memory management system for VACUUM, which reduces memory
    consumption and can improve overall vacuuming performance.
  * New SQL/JSON capabilities, including constructors, identity
    functions, and the JSON_TABLE() function, which converts JSON
    data into a table representation.
  * Various query performance improvements, including for
    sequential reads using streaming I/O, write throughput under
    high concurrency, and searches over multiple values in a btree
    index.
  * Logical replication enhancements, including:
    + Failover control
    + pg_createsubscriber, a utility that creates logical replicas
    from physical standbys
    + pg_upgrade now preserves replication slots on both publishers
    and subscribers
  * New client-side connection option, sslnegotiation=direct, that
    performs a direct TLS handshake to avoid a round-trip
    negotiation.
  * pg_basebackup now supports incremental backup.
  * COPY adds a new option, ON_ERROR ignore, that allows a copy
    operation to continue in the event of an error.
  * https://www.postgresql.org/about/news/p-2936/
  * https://www.postgresql.org/docs/17/release-17.html</changelog>
  <changelog author="Fabian Vogt &lt;fvogt@suse.com&gt;" date="1728302400">- Use cmake(LLVM) &lt; instead of &lt;= to also allow building against
  LLVM 18.1 and newer 18.x versions</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1730721600">- Add postgresql17-jsonb_jsonpath.patch as a temporary build fix.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1731499200">- Upgrade to 17.1:
  * CVE-2024-10976, bsc#1233323: Ensure cached plans are marked as
    dependent on the calling role when RLS applies to a
    non-top-level table reference.
  * CVE-2024-10977, bsc#1233325: Make libpq discard error messages
    received during SSL or GSS protocol negotiation.
  * CVE-2024-10978, bsc#1233326: Fix unintended interactions
    between SET SESSION AUTHORIZATION and SET ROLE
  * CVE-2024-10979, bsc#1233327: Prevent trusted PL/Perl code from
    changing environment variables.
  * obsoletes postgresql17-jsonb_jsonpath.patch
  * https://www.postgresql.org/about/news/p-2955/
  * https://www.postgresql.org/docs/release/17.1/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1732017600">- Upgrade to 17.2:
  * Repair ABI break for extensions that work with struct
    ResultRelInfo.
  * Restore functionality of ALTER {ROLE|DATABASE} SET role.
  * Fix cases where a logical replication slot's restart_lsn could
    go backwards.
  * Avoid deleting still-needed WAL files during pg_rewind.
  * Fix race conditions associated with dropping shared statistics
    entries.
  * Count index scans in contrib/bloom indexes in the statistics
    views, such as the pg_stat_user_indexes.idx_scan counter.
  * Fix crash when checking to see if an index's opclass options
    have changed.
  * Avoid assertion failure caused by disconnected NFA sub-graphs
    in regular expression parsing.
  * https://www.postgresql.org/about/news/p-2965/
  * https://www.postgresql.org/docs/release/17.2/</changelog>
  <changelog author="JS &lt;obs.coke518@passinbox.com&gt;" date="1735214400">- Disable LLVM JIT on loongarch64</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="JS &lt;obs.coke518@passinbox.com&gt;" date="1738152000">- Apply postgresql-tzdata2025a.patch regardless of
  whether LLVM JIT is enabled</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 17.3:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/17.3/
  * https://www.postgresql.org/about/news/-3015/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 17.4:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/17.4/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 17.5:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/17.5/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to Fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Update to 17.6
  * https://www.postgresql.org/about/news/postgresql-176-1610-1514-1419-1322-and-18-beta-3-released-3118/
  * https://www.postgresql.org/docs/release/17.6/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1756036800">- switch library to pg 18</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1756987200">- Sync spec file with version 18.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Update to 17.7:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/17.7/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 17.8:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/17.8/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 17.9 to fix two regressions in 17.8:
  * https://www.postgresql.org/docs/release/17.9/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
</package>
<package pkgid="524724818fc69e48af9a50e07050b0a5231cb0ceb64e2d2f7353839f361b26ba3550707c43ad0e1a60d885e181d34343c2fa68f317321570f00ff3b64411d21f" name="postgresql17" arch="src">
  <version epoch="0" ver="17.9" rel="54.2"/>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1727352000">- Upgrade to 17.0:
  * New memory management system for VACUUM, which reduces memory
    consumption and can improve overall vacuuming performance.
  * New SQL/JSON capabilities, including constructors, identity
    functions, and the JSON_TABLE() function, which converts JSON
    data into a table representation.
  * Various query performance improvements, including for
    sequential reads using streaming I/O, write throughput under
    high concurrency, and searches over multiple values in a btree
    index.
  * Logical replication enhancements, including:
    + Failover control
    + pg_createsubscriber, a utility that creates logical replicas
    from physical standbys
    + pg_upgrade now preserves replication slots on both publishers
    and subscribers
  * New client-side connection option, sslnegotiation=direct, that
    performs a direct TLS handshake to avoid a round-trip
    negotiation.
  * pg_basebackup now supports incremental backup.
  * COPY adds a new option, ON_ERROR ignore, that allows a copy
    operation to continue in the event of an error.
  * https://www.postgresql.org/about/news/p-2936/
  * https://www.postgresql.org/docs/17/release-17.html</changelog>
  <changelog author="Fabian Vogt &lt;fvogt@suse.com&gt;" date="1728302400">- Use cmake(LLVM) &lt; instead of &lt;= to also allow building against
  LLVM 18.1 and newer 18.x versions</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1730721600">- Add postgresql17-jsonb_jsonpath.patch as a temporary build fix.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1731499200">- Upgrade to 17.1:
  * CVE-2024-10976, bsc#1233323: Ensure cached plans are marked as
    dependent on the calling role when RLS applies to a
    non-top-level table reference.
  * CVE-2024-10977, bsc#1233325: Make libpq discard error messages
    received during SSL or GSS protocol negotiation.
  * CVE-2024-10978, bsc#1233326: Fix unintended interactions
    between SET SESSION AUTHORIZATION and SET ROLE
  * CVE-2024-10979, bsc#1233327: Prevent trusted PL/Perl code from
    changing environment variables.
  * obsoletes postgresql17-jsonb_jsonpath.patch
  * https://www.postgresql.org/about/news/p-2955/
  * https://www.postgresql.org/docs/release/17.1/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1732017600">- Upgrade to 17.2:
  * Repair ABI break for extensions that work with struct
    ResultRelInfo.
  * Restore functionality of ALTER {ROLE|DATABASE} SET role.
  * Fix cases where a logical replication slot's restart_lsn could
    go backwards.
  * Avoid deleting still-needed WAL files during pg_rewind.
  * Fix race conditions associated with dropping shared statistics
    entries.
  * Count index scans in contrib/bloom indexes in the statistics
    views, such as the pg_stat_user_indexes.idx_scan counter.
  * Fix crash when checking to see if an index's opclass options
    have changed.
  * Avoid assertion failure caused by disconnected NFA sub-graphs
    in regular expression parsing.
  * https://www.postgresql.org/about/news/p-2965/
  * https://www.postgresql.org/docs/release/17.2/</changelog>
  <changelog author="JS &lt;obs.coke518@passinbox.com&gt;" date="1735214400">- Disable LLVM JIT on loongarch64</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="JS &lt;obs.coke518@passinbox.com&gt;" date="1738152000">- Apply postgresql-tzdata2025a.patch regardless of
  whether LLVM JIT is enabled</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 17.3:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/17.3/
  * https://www.postgresql.org/about/news/-3015/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 17.4:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/17.4/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 17.5:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/17.5/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to Fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Update to 17.6
  * https://www.postgresql.org/about/news/postgresql-176-1610-1514-1419-1322-and-18-beta-3-released-3118/
  * https://www.postgresql.org/docs/release/17.6/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1756036800">- switch library to pg 18</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1756987200">- Sync spec file with version 18.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Update to 17.7:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/17.7/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 17.8:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/17.8/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 17.9 to fix two regressions in 17.8:
  * https://www.postgresql.org/docs/release/17.9/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
</package>
<package pkgid="ec014c5bca181f2ccd9e9d420194ec6cf5e11b76f81b63c80826cb174f097318c83080e68e5c0a03ff18723bdf0af90f966b771a90609f50bd2e2b8e300ebe0b" name="postgresql17" arch="ppc64le">
  <version epoch="0" ver="17.9" rel="55.1"/>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1727352000">- Upgrade to 17.0:
  * New memory management system for VACUUM, which reduces memory
    consumption and can improve overall vacuuming performance.
  * New SQL/JSON capabilities, including constructors, identity
    functions, and the JSON_TABLE() function, which converts JSON
    data into a table representation.
  * Various query performance improvements, including for
    sequential reads using streaming I/O, write throughput under
    high concurrency, and searches over multiple values in a btree
    index.
  * Logical replication enhancements, including:
    + Failover control
    + pg_createsubscriber, a utility that creates logical replicas
    from physical standbys
    + pg_upgrade now preserves replication slots on both publishers
    and subscribers
  * New client-side connection option, sslnegotiation=direct, that
    performs a direct TLS handshake to avoid a round-trip
    negotiation.
  * pg_basebackup now supports incremental backup.
  * COPY adds a new option, ON_ERROR ignore, that allows a copy
    operation to continue in the event of an error.
  * https://www.postgresql.org/about/news/p-2936/
  * https://www.postgresql.org/docs/17/release-17.html</changelog>
  <changelog author="Fabian Vogt &lt;fvogt@suse.com&gt;" date="1728302400">- Use cmake(LLVM) &lt; instead of &lt;= to also allow building against
  LLVM 18.1 and newer 18.x versions</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1730721600">- Add postgresql17-jsonb_jsonpath.patch as a temporary build fix.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1731499200">- Upgrade to 17.1:
  * CVE-2024-10976, bsc#1233323: Ensure cached plans are marked as
    dependent on the calling role when RLS applies to a
    non-top-level table reference.
  * CVE-2024-10977, bsc#1233325: Make libpq discard error messages
    received during SSL or GSS protocol negotiation.
  * CVE-2024-10978, bsc#1233326: Fix unintended interactions
    between SET SESSION AUTHORIZATION and SET ROLE
  * CVE-2024-10979, bsc#1233327: Prevent trusted PL/Perl code from
    changing environment variables.
  * obsoletes postgresql17-jsonb_jsonpath.patch
  * https://www.postgresql.org/about/news/p-2955/
  * https://www.postgresql.org/docs/release/17.1/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1732017600">- Upgrade to 17.2:
  * Repair ABI break for extensions that work with struct
    ResultRelInfo.
  * Restore functionality of ALTER {ROLE|DATABASE} SET role.
  * Fix cases where a logical replication slot's restart_lsn could
    go backwards.
  * Avoid deleting still-needed WAL files during pg_rewind.
  * Fix race conditions associated with dropping shared statistics
    entries.
  * Count index scans in contrib/bloom indexes in the statistics
    views, such as the pg_stat_user_indexes.idx_scan counter.
  * Fix crash when checking to see if an index's opclass options
    have changed.
  * Avoid assertion failure caused by disconnected NFA sub-graphs
    in regular expression parsing.
  * https://www.postgresql.org/about/news/p-2965/
  * https://www.postgresql.org/docs/release/17.2/</changelog>
  <changelog author="JS &lt;obs.coke518@passinbox.com&gt;" date="1735214400">- Disable LLVM JIT on loongarch64</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="JS &lt;obs.coke518@passinbox.com&gt;" date="1738152000">- Apply postgresql-tzdata2025a.patch regardless of
  whether LLVM JIT is enabled</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 17.3:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/17.3/
  * https://www.postgresql.org/about/news/-3015/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 17.4:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/17.4/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 17.5:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/17.5/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to Fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Update to 17.6
  * https://www.postgresql.org/about/news/postgresql-176-1610-1514-1419-1322-and-18-beta-3-released-3118/
  * https://www.postgresql.org/docs/release/17.6/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1756036800">- switch library to pg 18</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1756987200">- Sync spec file with version 18.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Update to 17.7:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/17.7/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 17.8:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/17.8/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 17.9 to fix two regressions in 17.8:
  * https://www.postgresql.org/docs/release/17.9/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
</package>
<package pkgid="4192f6a316f35fa2d5cfd93317b7b41f4d8f5ab598a4f12222b0bd4b209f25a6f51979caee94ec0761d61ca6b73d50cf4ae6ba482fefb9a17d9445a979fb6824" name="postgresql17" arch="src">
  <version epoch="0" ver="17.9" rel="55.1"/>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1727352000">- Upgrade to 17.0:
  * New memory management system for VACUUM, which reduces memory
    consumption and can improve overall vacuuming performance.
  * New SQL/JSON capabilities, including constructors, identity
    functions, and the JSON_TABLE() function, which converts JSON
    data into a table representation.
  * Various query performance improvements, including for
    sequential reads using streaming I/O, write throughput under
    high concurrency, and searches over multiple values in a btree
    index.
  * Logical replication enhancements, including:
    + Failover control
    + pg_createsubscriber, a utility that creates logical replicas
    from physical standbys
    + pg_upgrade now preserves replication slots on both publishers
    and subscribers
  * New client-side connection option, sslnegotiation=direct, that
    performs a direct TLS handshake to avoid a round-trip
    negotiation.
  * pg_basebackup now supports incremental backup.
  * COPY adds a new option, ON_ERROR ignore, that allows a copy
    operation to continue in the event of an error.
  * https://www.postgresql.org/about/news/p-2936/
  * https://www.postgresql.org/docs/17/release-17.html</changelog>
  <changelog author="Fabian Vogt &lt;fvogt@suse.com&gt;" date="1728302400">- Use cmake(LLVM) &lt; instead of &lt;= to also allow building against
  LLVM 18.1 and newer 18.x versions</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1730721600">- Add postgresql17-jsonb_jsonpath.patch as a temporary build fix.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1731499200">- Upgrade to 17.1:
  * CVE-2024-10976, bsc#1233323: Ensure cached plans are marked as
    dependent on the calling role when RLS applies to a
    non-top-level table reference.
  * CVE-2024-10977, bsc#1233325: Make libpq discard error messages
    received during SSL or GSS protocol negotiation.
  * CVE-2024-10978, bsc#1233326: Fix unintended interactions
    between SET SESSION AUTHORIZATION and SET ROLE
  * CVE-2024-10979, bsc#1233327: Prevent trusted PL/Perl code from
    changing environment variables.
  * obsoletes postgresql17-jsonb_jsonpath.patch
  * https://www.postgresql.org/about/news/p-2955/
  * https://www.postgresql.org/docs/release/17.1/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1732017600">- Upgrade to 17.2:
  * Repair ABI break for extensions that work with struct
    ResultRelInfo.
  * Restore functionality of ALTER {ROLE|DATABASE} SET role.
  * Fix cases where a logical replication slot's restart_lsn could
    go backwards.
  * Avoid deleting still-needed WAL files during pg_rewind.
  * Fix race conditions associated with dropping shared statistics
    entries.
  * Count index scans in contrib/bloom indexes in the statistics
    views, such as the pg_stat_user_indexes.idx_scan counter.
  * Fix crash when checking to see if an index's opclass options
    have changed.
  * Avoid assertion failure caused by disconnected NFA sub-graphs
    in regular expression parsing.
  * https://www.postgresql.org/about/news/p-2965/
  * https://www.postgresql.org/docs/release/17.2/</changelog>
  <changelog author="JS &lt;obs.coke518@passinbox.com&gt;" date="1735214400">- Disable LLVM JIT on loongarch64</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="JS &lt;obs.coke518@passinbox.com&gt;" date="1738152000">- Apply postgresql-tzdata2025a.patch regardless of
  whether LLVM JIT is enabled</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 17.3:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/17.3/
  * https://www.postgresql.org/about/news/-3015/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 17.4:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/17.4/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 17.5:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/17.5/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to Fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Update to 17.6
  * https://www.postgresql.org/about/news/postgresql-176-1610-1514-1419-1322-and-18-beta-3-released-3118/
  * https://www.postgresql.org/docs/release/17.6/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1756036800">- switch library to pg 18</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1756987200">- Sync spec file with version 18.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Update to 17.7:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/17.7/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 17.8:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/17.8/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 17.9 to fix two regressions in 17.8:
  * https://www.postgresql.org/docs/release/17.9/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
</package>
<package pkgid="8e170207084d16b06ba55cab3e0f904dd29930e3ae42021472778e27cd60fe83506e3ac2a7d7d4c543134e8d05f098f230106e38fa0ab544916d093d06152c6f" name="postgresql17-contrib" arch="x86_64">
  <version epoch="0" ver="17.10" rel="69.2"/>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1731499200">- Upgrade to 17.1:
  * CVE-2024-10976, bsc#1233323: Ensure cached plans are marked as
    dependent on the calling role when RLS applies to a
    non-top-level table reference.
  * CVE-2024-10977, bsc#1233325: Make libpq discard error messages
    received during SSL or GSS protocol negotiation.
  * CVE-2024-10978, bsc#1233326: Fix unintended interactions
    between SET SESSION AUTHORIZATION and SET ROLE
  * CVE-2024-10979, bsc#1233327: Prevent trusted PL/Perl code from
    changing environment variables.
  * obsoletes postgresql17-jsonb_jsonpath.patch
  * https://www.postgresql.org/about/news/p-2955/
  * https://www.postgresql.org/docs/release/17.1/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1732017600">- Upgrade to 17.2:
  * Repair ABI break for extensions that work with struct
    ResultRelInfo.
  * Restore functionality of ALTER {ROLE|DATABASE} SET role.
  * Fix cases where a logical replication slot's restart_lsn could
    go backwards.
  * Avoid deleting still-needed WAL files during pg_rewind.
  * Fix race conditions associated with dropping shared statistics
    entries.
  * Count index scans in contrib/bloom indexes in the statistics
    views, such as the pg_stat_user_indexes.idx_scan counter.
  * Fix crash when checking to see if an index's opclass options
    have changed.
  * Avoid assertion failure caused by disconnected NFA sub-graphs
    in regular expression parsing.
  * https://www.postgresql.org/about/news/p-2965/
  * https://www.postgresql.org/docs/release/17.2/</changelog>
  <changelog author="JS &lt;obs.coke518@passinbox.com&gt;" date="1735214400">- Disable LLVM JIT on loongarch64</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="JS &lt;obs.coke518@passinbox.com&gt;" date="1738152000">- Apply postgresql-tzdata2025a.patch regardless of
  whether LLVM JIT is enabled</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 17.3:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/17.3/
  * https://www.postgresql.org/about/news/-3015/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 17.4:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/17.4/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 17.5:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/17.5/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to Fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Update to 17.6
  * https://www.postgresql.org/about/news/postgresql-176-1610-1514-1419-1322-and-18-beta-3-released-3118/
  * https://www.postgresql.org/docs/release/17.6/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1756036800">- switch library to pg 18</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1756987200">- Sync spec file with version 18.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Update to 17.7:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/17.7/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 17.8:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/17.8/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 17.9 to fix two regressions in 17.8:
  * https://www.postgresql.org/docs/release/17.9/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1774872000">- Get rid of update-alternatives for openSUSE/SLE 16.0 and newer
  to support immutable systems and transactional updates.
  (jsc#PED-14825, bsc#1245875)</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1777550400">- bsc#1263804: After dropping update-alternatives we have to
  package /usr/bin/pg_config as an actual symlink, not %ghost.
- Fix spelling of build conditionals.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1778673600">- Update to version 17.10:
  * bsc#1265172, CVE-2026-6472: ensure the user has CREATE
    privilege on the schema specified
  * bsc#1265173, CVE-2026-6473: integer overflows in
    memory-allocation calculations
  * bsc#1265174, CVE-2026-6474: Guard against malicious time zone
    names
  * bsc#1265175, CVE-2026-6475: Prevent path traversal in
    pg_basebackup and pg_rewind
  * bsc#1265176, CVE-2026-6476: Properly quote subscription names
    in pg_createsubscriber
  * bsc#1265177, CVE-2026-6477: Mark PQfn() as unsafe, and avoid
    using it within libpq
  * bsc#1265178, CVE-2026-6478: Use timing-safe string comparisons
    in authentication code
  * bsc#1265179, CVE-2026-6479: Prevent unbounded recursion while
    processing startup packets
  * bsc#1265181, CVE-2026-6637: Prevent SQL injection and buffer
    overruns in contrib/spi
  * bsc#1265182, CVE-2026-6638: Properly quote object names in
    logical replication origin checks
  * https://www.postgresql.org/docs/release/17.10/</changelog>
</package>
<package pkgid="34173db48ba98be3726af5a3cfc9b49d9f82ff4d636aee31b9601ce00298076323aa38bf8e3127cf27bf1ea7c064e06d014d50ea1e0643f718511276db2a6ece" name="postgresql17-contrib" arch="s390x">
  <version epoch="0" ver="17.9" rel="53.1"/>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1727352000">- Upgrade to 17.0:
  * New memory management system for VACUUM, which reduces memory
    consumption and can improve overall vacuuming performance.
  * New SQL/JSON capabilities, including constructors, identity
    functions, and the JSON_TABLE() function, which converts JSON
    data into a table representation.
  * Various query performance improvements, including for
    sequential reads using streaming I/O, write throughput under
    high concurrency, and searches over multiple values in a btree
    index.
  * Logical replication enhancements, including:
    + Failover control
    + pg_createsubscriber, a utility that creates logical replicas
    from physical standbys
    + pg_upgrade now preserves replication slots on both publishers
    and subscribers
  * New client-side connection option, sslnegotiation=direct, that
    performs a direct TLS handshake to avoid a round-trip
    negotiation.
  * pg_basebackup now supports incremental backup.
  * COPY adds a new option, ON_ERROR ignore, that allows a copy
    operation to continue in the event of an error.
  * https://www.postgresql.org/about/news/p-2936/
  * https://www.postgresql.org/docs/17/release-17.html</changelog>
  <changelog author="Fabian Vogt &lt;fvogt@suse.com&gt;" date="1728302400">- Use cmake(LLVM) &lt; instead of &lt;= to also allow building against
  LLVM 18.1 and newer 18.x versions</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1730721600">- Add postgresql17-jsonb_jsonpath.patch as a temporary build fix.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1731499200">- Upgrade to 17.1:
  * CVE-2024-10976, bsc#1233323: Ensure cached plans are marked as
    dependent on the calling role when RLS applies to a
    non-top-level table reference.
  * CVE-2024-10977, bsc#1233325: Make libpq discard error messages
    received during SSL or GSS protocol negotiation.
  * CVE-2024-10978, bsc#1233326: Fix unintended interactions
    between SET SESSION AUTHORIZATION and SET ROLE
  * CVE-2024-10979, bsc#1233327: Prevent trusted PL/Perl code from
    changing environment variables.
  * obsoletes postgresql17-jsonb_jsonpath.patch
  * https://www.postgresql.org/about/news/p-2955/
  * https://www.postgresql.org/docs/release/17.1/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1732017600">- Upgrade to 17.2:
  * Repair ABI break for extensions that work with struct
    ResultRelInfo.
  * Restore functionality of ALTER {ROLE|DATABASE} SET role.
  * Fix cases where a logical replication slot's restart_lsn could
    go backwards.
  * Avoid deleting still-needed WAL files during pg_rewind.
  * Fix race conditions associated with dropping shared statistics
    entries.
  * Count index scans in contrib/bloom indexes in the statistics
    views, such as the pg_stat_user_indexes.idx_scan counter.
  * Fix crash when checking to see if an index's opclass options
    have changed.
  * Avoid assertion failure caused by disconnected NFA sub-graphs
    in regular expression parsing.
  * https://www.postgresql.org/about/news/p-2965/
  * https://www.postgresql.org/docs/release/17.2/</changelog>
  <changelog author="JS &lt;obs.coke518@passinbox.com&gt;" date="1735214400">- Disable LLVM JIT on loongarch64</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="JS &lt;obs.coke518@passinbox.com&gt;" date="1738152000">- Apply postgresql-tzdata2025a.patch regardless of
  whether LLVM JIT is enabled</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 17.3:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/17.3/
  * https://www.postgresql.org/about/news/-3015/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 17.4:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/17.4/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 17.5:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/17.5/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to Fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Update to 17.6
  * https://www.postgresql.org/about/news/postgresql-176-1610-1514-1419-1322-and-18-beta-3-released-3118/
  * https://www.postgresql.org/docs/release/17.6/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1756036800">- switch library to pg 18</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1756987200">- Sync spec file with version 18.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Update to 17.7:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/17.7/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 17.8:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/17.8/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 17.9 to fix two regressions in 17.8:
  * https://www.postgresql.org/docs/release/17.9/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
</package>
<package pkgid="9fcaafb3000100837d32c1c4ad5d78c00512935bfd51244498f459c2cf83d5771e8d5caf9b1767db33a749b79f9fad41bf391403f0f6142e495706189a4dc4ae" name="postgresql17-contrib" arch="aarch64">
  <version epoch="0" ver="17.9" rel="54.2"/>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1727352000">- Upgrade to 17.0:
  * New memory management system for VACUUM, which reduces memory
    consumption and can improve overall vacuuming performance.
  * New SQL/JSON capabilities, including constructors, identity
    functions, and the JSON_TABLE() function, which converts JSON
    data into a table representation.
  * Various query performance improvements, including for
    sequential reads using streaming I/O, write throughput under
    high concurrency, and searches over multiple values in a btree
    index.
  * Logical replication enhancements, including:
    + Failover control
    + pg_createsubscriber, a utility that creates logical replicas
    from physical standbys
    + pg_upgrade now preserves replication slots on both publishers
    and subscribers
  * New client-side connection option, sslnegotiation=direct, that
    performs a direct TLS handshake to avoid a round-trip
    negotiation.
  * pg_basebackup now supports incremental backup.
  * COPY adds a new option, ON_ERROR ignore, that allows a copy
    operation to continue in the event of an error.
  * https://www.postgresql.org/about/news/p-2936/
  * https://www.postgresql.org/docs/17/release-17.html</changelog>
  <changelog author="Fabian Vogt &lt;fvogt@suse.com&gt;" date="1728302400">- Use cmake(LLVM) &lt; instead of &lt;= to also allow building against
  LLVM 18.1 and newer 18.x versions</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1730721600">- Add postgresql17-jsonb_jsonpath.patch as a temporary build fix.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1731499200">- Upgrade to 17.1:
  * CVE-2024-10976, bsc#1233323: Ensure cached plans are marked as
    dependent on the calling role when RLS applies to a
    non-top-level table reference.
  * CVE-2024-10977, bsc#1233325: Make libpq discard error messages
    received during SSL or GSS protocol negotiation.
  * CVE-2024-10978, bsc#1233326: Fix unintended interactions
    between SET SESSION AUTHORIZATION and SET ROLE
  * CVE-2024-10979, bsc#1233327: Prevent trusted PL/Perl code from
    changing environment variables.
  * obsoletes postgresql17-jsonb_jsonpath.patch
  * https://www.postgresql.org/about/news/p-2955/
  * https://www.postgresql.org/docs/release/17.1/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1732017600">- Upgrade to 17.2:
  * Repair ABI break for extensions that work with struct
    ResultRelInfo.
  * Restore functionality of ALTER {ROLE|DATABASE} SET role.
  * Fix cases where a logical replication slot's restart_lsn could
    go backwards.
  * Avoid deleting still-needed WAL files during pg_rewind.
  * Fix race conditions associated with dropping shared statistics
    entries.
  * Count index scans in contrib/bloom indexes in the statistics
    views, such as the pg_stat_user_indexes.idx_scan counter.
  * Fix crash when checking to see if an index's opclass options
    have changed.
  * Avoid assertion failure caused by disconnected NFA sub-graphs
    in regular expression parsing.
  * https://www.postgresql.org/about/news/p-2965/
  * https://www.postgresql.org/docs/release/17.2/</changelog>
  <changelog author="JS &lt;obs.coke518@passinbox.com&gt;" date="1735214400">- Disable LLVM JIT on loongarch64</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="JS &lt;obs.coke518@passinbox.com&gt;" date="1738152000">- Apply postgresql-tzdata2025a.patch regardless of
  whether LLVM JIT is enabled</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 17.3:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/17.3/
  * https://www.postgresql.org/about/news/-3015/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 17.4:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/17.4/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 17.5:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/17.5/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to Fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Update to 17.6
  * https://www.postgresql.org/about/news/postgresql-176-1610-1514-1419-1322-and-18-beta-3-released-3118/
  * https://www.postgresql.org/docs/release/17.6/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1756036800">- switch library to pg 18</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1756987200">- Sync spec file with version 18.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Update to 17.7:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/17.7/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 17.8:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/17.8/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 17.9 to fix two regressions in 17.8:
  * https://www.postgresql.org/docs/release/17.9/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
</package>
<package pkgid="ebf32eea0a96fbf03fea085c54e680f6752a7cb8a2c0035eb5b1bc068f4d1d8b27aaddd46c8e57b2b37378a1e209ee6c208c1e7f71ee3eed0e0e2709ae2dc258" name="postgresql17-contrib" arch="ppc64le">
  <version epoch="0" ver="17.9" rel="55.1"/>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1727352000">- Upgrade to 17.0:
  * New memory management system for VACUUM, which reduces memory
    consumption and can improve overall vacuuming performance.
  * New SQL/JSON capabilities, including constructors, identity
    functions, and the JSON_TABLE() function, which converts JSON
    data into a table representation.
  * Various query performance improvements, including for
    sequential reads using streaming I/O, write throughput under
    high concurrency, and searches over multiple values in a btree
    index.
  * Logical replication enhancements, including:
    + Failover control
    + pg_createsubscriber, a utility that creates logical replicas
    from physical standbys
    + pg_upgrade now preserves replication slots on both publishers
    and subscribers
  * New client-side connection option, sslnegotiation=direct, that
    performs a direct TLS handshake to avoid a round-trip
    negotiation.
  * pg_basebackup now supports incremental backup.
  * COPY adds a new option, ON_ERROR ignore, that allows a copy
    operation to continue in the event of an error.
  * https://www.postgresql.org/about/news/p-2936/
  * https://www.postgresql.org/docs/17/release-17.html</changelog>
  <changelog author="Fabian Vogt &lt;fvogt@suse.com&gt;" date="1728302400">- Use cmake(LLVM) &lt; instead of &lt;= to also allow building against
  LLVM 18.1 and newer 18.x versions</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1730721600">- Add postgresql17-jsonb_jsonpath.patch as a temporary build fix.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1731499200">- Upgrade to 17.1:
  * CVE-2024-10976, bsc#1233323: Ensure cached plans are marked as
    dependent on the calling role when RLS applies to a
    non-top-level table reference.
  * CVE-2024-10977, bsc#1233325: Make libpq discard error messages
    received during SSL or GSS protocol negotiation.
  * CVE-2024-10978, bsc#1233326: Fix unintended interactions
    between SET SESSION AUTHORIZATION and SET ROLE
  * CVE-2024-10979, bsc#1233327: Prevent trusted PL/Perl code from
    changing environment variables.
  * obsoletes postgresql17-jsonb_jsonpath.patch
  * https://www.postgresql.org/about/news/p-2955/
  * https://www.postgresql.org/docs/release/17.1/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1732017600">- Upgrade to 17.2:
  * Repair ABI break for extensions that work with struct
    ResultRelInfo.
  * Restore functionality of ALTER {ROLE|DATABASE} SET role.
  * Fix cases where a logical replication slot's restart_lsn could
    go backwards.
  * Avoid deleting still-needed WAL files during pg_rewind.
  * Fix race conditions associated with dropping shared statistics
    entries.
  * Count index scans in contrib/bloom indexes in the statistics
    views, such as the pg_stat_user_indexes.idx_scan counter.
  * Fix crash when checking to see if an index's opclass options
    have changed.
  * Avoid assertion failure caused by disconnected NFA sub-graphs
    in regular expression parsing.
  * https://www.postgresql.org/about/news/p-2965/
  * https://www.postgresql.org/docs/release/17.2/</changelog>
  <changelog author="JS &lt;obs.coke518@passinbox.com&gt;" date="1735214400">- Disable LLVM JIT on loongarch64</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="JS &lt;obs.coke518@passinbox.com&gt;" date="1738152000">- Apply postgresql-tzdata2025a.patch regardless of
  whether LLVM JIT is enabled</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 17.3:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/17.3/
  * https://www.postgresql.org/about/news/-3015/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 17.4:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/17.4/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 17.5:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/17.5/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to Fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Update to 17.6
  * https://www.postgresql.org/about/news/postgresql-176-1610-1514-1419-1322-and-18-beta-3-released-3118/
  * https://www.postgresql.org/docs/release/17.6/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1756036800">- switch library to pg 18</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1756987200">- Sync spec file with version 18.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Update to 17.7:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/17.7/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 17.8:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/17.8/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 17.9 to fix two regressions in 17.8:
  * https://www.postgresql.org/docs/release/17.9/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
</package>
<package pkgid="0b0991aa3cc5834052ac8c024066cf53e2c8154689dfc516751262e064a421c0b64a7bcc596acfc1704fcdb331c51646d8b51bcbd4f9799912331381ed54cdeb" name="postgresql17-devel" arch="x86_64">
  <version epoch="0" ver="17.10" rel="69.2"/>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1731499200">- Upgrade to 17.1:
  * CVE-2024-10976, bsc#1233323: Ensure cached plans are marked as
    dependent on the calling role when RLS applies to a
    non-top-level table reference.
  * CVE-2024-10977, bsc#1233325: Make libpq discard error messages
    received during SSL or GSS protocol negotiation.
  * CVE-2024-10978, bsc#1233326: Fix unintended interactions
    between SET SESSION AUTHORIZATION and SET ROLE
  * CVE-2024-10979, bsc#1233327: Prevent trusted PL/Perl code from
    changing environment variables.
  * obsoletes postgresql17-jsonb_jsonpath.patch
  * https://www.postgresql.org/about/news/p-2955/
  * https://www.postgresql.org/docs/release/17.1/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1732017600">- Upgrade to 17.2:
  * Repair ABI break for extensions that work with struct
    ResultRelInfo.
  * Restore functionality of ALTER {ROLE|DATABASE} SET role.
  * Fix cases where a logical replication slot's restart_lsn could
    go backwards.
  * Avoid deleting still-needed WAL files during pg_rewind.
  * Fix race conditions associated with dropping shared statistics
    entries.
  * Count index scans in contrib/bloom indexes in the statistics
    views, such as the pg_stat_user_indexes.idx_scan counter.
  * Fix crash when checking to see if an index's opclass options
    have changed.
  * Avoid assertion failure caused by disconnected NFA sub-graphs
    in regular expression parsing.
  * https://www.postgresql.org/about/news/p-2965/
  * https://www.postgresql.org/docs/release/17.2/</changelog>
  <changelog author="JS &lt;obs.coke518@passinbox.com&gt;" date="1735214400">- Disable LLVM JIT on loongarch64</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="JS &lt;obs.coke518@passinbox.com&gt;" date="1738152000">- Apply postgresql-tzdata2025a.patch regardless of
  whether LLVM JIT is enabled</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 17.3:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/17.3/
  * https://www.postgresql.org/about/news/-3015/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 17.4:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/17.4/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 17.5:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/17.5/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to Fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Update to 17.6
  * https://www.postgresql.org/about/news/postgresql-176-1610-1514-1419-1322-and-18-beta-3-released-3118/
  * https://www.postgresql.org/docs/release/17.6/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1756036800">- switch library to pg 18</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1756987200">- Sync spec file with version 18.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Update to 17.7:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/17.7/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 17.8:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/17.8/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 17.9 to fix two regressions in 17.8:
  * https://www.postgresql.org/docs/release/17.9/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1774872000">- Get rid of update-alternatives for openSUSE/SLE 16.0 and newer
  to support immutable systems and transactional updates.
  (jsc#PED-14825, bsc#1245875)</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1777550400">- bsc#1263804: After dropping update-alternatives we have to
  package /usr/bin/pg_config as an actual symlink, not %ghost.
- Fix spelling of build conditionals.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1778673600">- Update to version 17.10:
  * bsc#1265172, CVE-2026-6472: ensure the user has CREATE
    privilege on the schema specified
  * bsc#1265173, CVE-2026-6473: integer overflows in
    memory-allocation calculations
  * bsc#1265174, CVE-2026-6474: Guard against malicious time zone
    names
  * bsc#1265175, CVE-2026-6475: Prevent path traversal in
    pg_basebackup and pg_rewind
  * bsc#1265176, CVE-2026-6476: Properly quote subscription names
    in pg_createsubscriber
  * bsc#1265177, CVE-2026-6477: Mark PQfn() as unsafe, and avoid
    using it within libpq
  * bsc#1265178, CVE-2026-6478: Use timing-safe string comparisons
    in authentication code
  * bsc#1265179, CVE-2026-6479: Prevent unbounded recursion while
    processing startup packets
  * bsc#1265181, CVE-2026-6637: Prevent SQL injection and buffer
    overruns in contrib/spi
  * bsc#1265182, CVE-2026-6638: Properly quote object names in
    logical replication origin checks
  * https://www.postgresql.org/docs/release/17.10/</changelog>
</package>
<package pkgid="adb8b2987b6025868e510b378b19770e51ad3e5b692fe410ca9d28aad2f33538a53510f7c9702ace29a79d48f97fdd6f8be1b76646558e048f1fc562e7a09f7f" name="postgresql17-devel" arch="s390x">
  <version epoch="0" ver="17.9" rel="53.1"/>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1727352000">- Upgrade to 17.0:
  * New memory management system for VACUUM, which reduces memory
    consumption and can improve overall vacuuming performance.
  * New SQL/JSON capabilities, including constructors, identity
    functions, and the JSON_TABLE() function, which converts JSON
    data into a table representation.
  * Various query performance improvements, including for
    sequential reads using streaming I/O, write throughput under
    high concurrency, and searches over multiple values in a btree
    index.
  * Logical replication enhancements, including:
    + Failover control
    + pg_createsubscriber, a utility that creates logical replicas
    from physical standbys
    + pg_upgrade now preserves replication slots on both publishers
    and subscribers
  * New client-side connection option, sslnegotiation=direct, that
    performs a direct TLS handshake to avoid a round-trip
    negotiation.
  * pg_basebackup now supports incremental backup.
  * COPY adds a new option, ON_ERROR ignore, that allows a copy
    operation to continue in the event of an error.
  * https://www.postgresql.org/about/news/p-2936/
  * https://www.postgresql.org/docs/17/release-17.html</changelog>
  <changelog author="Fabian Vogt &lt;fvogt@suse.com&gt;" date="1728302400">- Use cmake(LLVM) &lt; instead of &lt;= to also allow building against
  LLVM 18.1 and newer 18.x versions</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1730721600">- Add postgresql17-jsonb_jsonpath.patch as a temporary build fix.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1731499200">- Upgrade to 17.1:
  * CVE-2024-10976, bsc#1233323: Ensure cached plans are marked as
    dependent on the calling role when RLS applies to a
    non-top-level table reference.
  * CVE-2024-10977, bsc#1233325: Make libpq discard error messages
    received during SSL or GSS protocol negotiation.
  * CVE-2024-10978, bsc#1233326: Fix unintended interactions
    between SET SESSION AUTHORIZATION and SET ROLE
  * CVE-2024-10979, bsc#1233327: Prevent trusted PL/Perl code from
    changing environment variables.
  * obsoletes postgresql17-jsonb_jsonpath.patch
  * https://www.postgresql.org/about/news/p-2955/
  * https://www.postgresql.org/docs/release/17.1/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1732017600">- Upgrade to 17.2:
  * Repair ABI break for extensions that work with struct
    ResultRelInfo.
  * Restore functionality of ALTER {ROLE|DATABASE} SET role.
  * Fix cases where a logical replication slot's restart_lsn could
    go backwards.
  * Avoid deleting still-needed WAL files during pg_rewind.
  * Fix race conditions associated with dropping shared statistics
    entries.
  * Count index scans in contrib/bloom indexes in the statistics
    views, such as the pg_stat_user_indexes.idx_scan counter.
  * Fix crash when checking to see if an index's opclass options
    have changed.
  * Avoid assertion failure caused by disconnected NFA sub-graphs
    in regular expression parsing.
  * https://www.postgresql.org/about/news/p-2965/
  * https://www.postgresql.org/docs/release/17.2/</changelog>
  <changelog author="JS &lt;obs.coke518@passinbox.com&gt;" date="1735214400">- Disable LLVM JIT on loongarch64</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="JS &lt;obs.coke518@passinbox.com&gt;" date="1738152000">- Apply postgresql-tzdata2025a.patch regardless of
  whether LLVM JIT is enabled</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 17.3:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/17.3/
  * https://www.postgresql.org/about/news/-3015/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 17.4:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/17.4/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 17.5:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/17.5/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to Fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Update to 17.6
  * https://www.postgresql.org/about/news/postgresql-176-1610-1514-1419-1322-and-18-beta-3-released-3118/
  * https://www.postgresql.org/docs/release/17.6/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1756036800">- switch library to pg 18</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1756987200">- Sync spec file with version 18.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Update to 17.7:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/17.7/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 17.8:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/17.8/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 17.9 to fix two regressions in 17.8:
  * https://www.postgresql.org/docs/release/17.9/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
</package>
<package pkgid="b3d672ef8bddcd86ae368b31b6ba07280e425971a5e1a23d6fbeebdb41b35722e9ac7b6a15bddbfeadb2294f2e7df012692785ae9fb78ca685534371cfe722dc" name="postgresql17-devel" arch="aarch64">
  <version epoch="0" ver="17.9" rel="54.2"/>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1727352000">- Upgrade to 17.0:
  * New memory management system for VACUUM, which reduces memory
    consumption and can improve overall vacuuming performance.
  * New SQL/JSON capabilities, including constructors, identity
    functions, and the JSON_TABLE() function, which converts JSON
    data into a table representation.
  * Various query performance improvements, including for
    sequential reads using streaming I/O, write throughput under
    high concurrency, and searches over multiple values in a btree
    index.
  * Logical replication enhancements, including:
    + Failover control
    + pg_createsubscriber, a utility that creates logical replicas
    from physical standbys
    + pg_upgrade now preserves replication slots on both publishers
    and subscribers
  * New client-side connection option, sslnegotiation=direct, that
    performs a direct TLS handshake to avoid a round-trip
    negotiation.
  * pg_basebackup now supports incremental backup.
  * COPY adds a new option, ON_ERROR ignore, that allows a copy
    operation to continue in the event of an error.
  * https://www.postgresql.org/about/news/p-2936/
  * https://www.postgresql.org/docs/17/release-17.html</changelog>
  <changelog author="Fabian Vogt &lt;fvogt@suse.com&gt;" date="1728302400">- Use cmake(LLVM) &lt; instead of &lt;= to also allow building against
  LLVM 18.1 and newer 18.x versions</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1730721600">- Add postgresql17-jsonb_jsonpath.patch as a temporary build fix.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1731499200">- Upgrade to 17.1:
  * CVE-2024-10976, bsc#1233323: Ensure cached plans are marked as
    dependent on the calling role when RLS applies to a
    non-top-level table reference.
  * CVE-2024-10977, bsc#1233325: Make libpq discard error messages
    received during SSL or GSS protocol negotiation.
  * CVE-2024-10978, bsc#1233326: Fix unintended interactions
    between SET SESSION AUTHORIZATION and SET ROLE
  * CVE-2024-10979, bsc#1233327: Prevent trusted PL/Perl code from
    changing environment variables.
  * obsoletes postgresql17-jsonb_jsonpath.patch
  * https://www.postgresql.org/about/news/p-2955/
  * https://www.postgresql.org/docs/release/17.1/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1732017600">- Upgrade to 17.2:
  * Repair ABI break for extensions that work with struct
    ResultRelInfo.
  * Restore functionality of ALTER {ROLE|DATABASE} SET role.
  * Fix cases where a logical replication slot's restart_lsn could
    go backwards.
  * Avoid deleting still-needed WAL files during pg_rewind.
  * Fix race conditions associated with dropping shared statistics
    entries.
  * Count index scans in contrib/bloom indexes in the statistics
    views, such as the pg_stat_user_indexes.idx_scan counter.
  * Fix crash when checking to see if an index's opclass options
    have changed.
  * Avoid assertion failure caused by disconnected NFA sub-graphs
    in regular expression parsing.
  * https://www.postgresql.org/about/news/p-2965/
  * https://www.postgresql.org/docs/release/17.2/</changelog>
  <changelog author="JS &lt;obs.coke518@passinbox.com&gt;" date="1735214400">- Disable LLVM JIT on loongarch64</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="JS &lt;obs.coke518@passinbox.com&gt;" date="1738152000">- Apply postgresql-tzdata2025a.patch regardless of
  whether LLVM JIT is enabled</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 17.3:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/17.3/
  * https://www.postgresql.org/about/news/-3015/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 17.4:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/17.4/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 17.5:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/17.5/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to Fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Update to 17.6
  * https://www.postgresql.org/about/news/postgresql-176-1610-1514-1419-1322-and-18-beta-3-released-3118/
  * https://www.postgresql.org/docs/release/17.6/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1756036800">- switch library to pg 18</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1756987200">- Sync spec file with version 18.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Update to 17.7:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/17.7/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 17.8:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/17.8/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 17.9 to fix two regressions in 17.8:
  * https://www.postgresql.org/docs/release/17.9/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
</package>
<package pkgid="7423a2d68ce1b9222606c9cd9a87cfb4bbd2a540148131f8ad831695533fa675fc071d79f4662b984dabd47102114b01f380aa87ff5145a39cb8bb86fce942d5" name="postgresql17-devel" arch="ppc64le">
  <version epoch="0" ver="17.9" rel="55.1"/>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1727352000">- Upgrade to 17.0:
  * New memory management system for VACUUM, which reduces memory
    consumption and can improve overall vacuuming performance.
  * New SQL/JSON capabilities, including constructors, identity
    functions, and the JSON_TABLE() function, which converts JSON
    data into a table representation.
  * Various query performance improvements, including for
    sequential reads using streaming I/O, write throughput under
    high concurrency, and searches over multiple values in a btree
    index.
  * Logical replication enhancements, including:
    + Failover control
    + pg_createsubscriber, a utility that creates logical replicas
    from physical standbys
    + pg_upgrade now preserves replication slots on both publishers
    and subscribers
  * New client-side connection option, sslnegotiation=direct, that
    performs a direct TLS handshake to avoid a round-trip
    negotiation.
  * pg_basebackup now supports incremental backup.
  * COPY adds a new option, ON_ERROR ignore, that allows a copy
    operation to continue in the event of an error.
  * https://www.postgresql.org/about/news/p-2936/
  * https://www.postgresql.org/docs/17/release-17.html</changelog>
  <changelog author="Fabian Vogt &lt;fvogt@suse.com&gt;" date="1728302400">- Use cmake(LLVM) &lt; instead of &lt;= to also allow building against
  LLVM 18.1 and newer 18.x versions</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1730721600">- Add postgresql17-jsonb_jsonpath.patch as a temporary build fix.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1731499200">- Upgrade to 17.1:
  * CVE-2024-10976, bsc#1233323: Ensure cached plans are marked as
    dependent on the calling role when RLS applies to a
    non-top-level table reference.
  * CVE-2024-10977, bsc#1233325: Make libpq discard error messages
    received during SSL or GSS protocol negotiation.
  * CVE-2024-10978, bsc#1233326: Fix unintended interactions
    between SET SESSION AUTHORIZATION and SET ROLE
  * CVE-2024-10979, bsc#1233327: Prevent trusted PL/Perl code from
    changing environment variables.
  * obsoletes postgresql17-jsonb_jsonpath.patch
  * https://www.postgresql.org/about/news/p-2955/
  * https://www.postgresql.org/docs/release/17.1/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1732017600">- Upgrade to 17.2:
  * Repair ABI break for extensions that work with struct
    ResultRelInfo.
  * Restore functionality of ALTER {ROLE|DATABASE} SET role.
  * Fix cases where a logical replication slot's restart_lsn could
    go backwards.
  * Avoid deleting still-needed WAL files during pg_rewind.
  * Fix race conditions associated with dropping shared statistics
    entries.
  * Count index scans in contrib/bloom indexes in the statistics
    views, such as the pg_stat_user_indexes.idx_scan counter.
  * Fix crash when checking to see if an index's opclass options
    have changed.
  * Avoid assertion failure caused by disconnected NFA sub-graphs
    in regular expression parsing.
  * https://www.postgresql.org/about/news/p-2965/
  * https://www.postgresql.org/docs/release/17.2/</changelog>
  <changelog author="JS &lt;obs.coke518@passinbox.com&gt;" date="1735214400">- Disable LLVM JIT on loongarch64</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="JS &lt;obs.coke518@passinbox.com&gt;" date="1738152000">- Apply postgresql-tzdata2025a.patch regardless of
  whether LLVM JIT is enabled</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 17.3:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/17.3/
  * https://www.postgresql.org/about/news/-3015/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 17.4:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/17.4/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 17.5:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/17.5/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to Fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Update to 17.6
  * https://www.postgresql.org/about/news/postgresql-176-1610-1514-1419-1322-and-18-beta-3-released-3118/
  * https://www.postgresql.org/docs/release/17.6/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1756036800">- switch library to pg 18</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1756987200">- Sync spec file with version 18.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Update to 17.7:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/17.7/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 17.8:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/17.8/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 17.9 to fix two regressions in 17.8:
  * https://www.postgresql.org/docs/release/17.9/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
</package>
<package pkgid="7b5eae5663f17671f59c0bae78a3b44947c6c6b8f14d2e6e691ecee7251c1da97c6384f79a7aee1b053222854818607ca75493af4539deaa297413cc106a5824" name="postgresql17-docs" arch="noarch">
  <version epoch="0" ver="17.10" rel="69.2"/>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1731499200">- Upgrade to 17.1:
  * CVE-2024-10976, bsc#1233323: Ensure cached plans are marked as
    dependent on the calling role when RLS applies to a
    non-top-level table reference.
  * CVE-2024-10977, bsc#1233325: Make libpq discard error messages
    received during SSL or GSS protocol negotiation.
  * CVE-2024-10978, bsc#1233326: Fix unintended interactions
    between SET SESSION AUTHORIZATION and SET ROLE
  * CVE-2024-10979, bsc#1233327: Prevent trusted PL/Perl code from
    changing environment variables.
  * obsoletes postgresql17-jsonb_jsonpath.patch
  * https://www.postgresql.org/about/news/p-2955/
  * https://www.postgresql.org/docs/release/17.1/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1732017600">- Upgrade to 17.2:
  * Repair ABI break for extensions that work with struct
    ResultRelInfo.
  * Restore functionality of ALTER {ROLE|DATABASE} SET role.
  * Fix cases where a logical replication slot's restart_lsn could
    go backwards.
  * Avoid deleting still-needed WAL files during pg_rewind.
  * Fix race conditions associated with dropping shared statistics
    entries.
  * Count index scans in contrib/bloom indexes in the statistics
    views, such as the pg_stat_user_indexes.idx_scan counter.
  * Fix crash when checking to see if an index's opclass options
    have changed.
  * Avoid assertion failure caused by disconnected NFA sub-graphs
    in regular expression parsing.
  * https://www.postgresql.org/about/news/p-2965/
  * https://www.postgresql.org/docs/release/17.2/</changelog>
  <changelog author="JS &lt;obs.coke518@passinbox.com&gt;" date="1735214400">- Disable LLVM JIT on loongarch64</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="JS &lt;obs.coke518@passinbox.com&gt;" date="1738152000">- Apply postgresql-tzdata2025a.patch regardless of
  whether LLVM JIT is enabled</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 17.3:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/17.3/
  * https://www.postgresql.org/about/news/-3015/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 17.4:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/17.4/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 17.5:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/17.5/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to Fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Update to 17.6
  * https://www.postgresql.org/about/news/postgresql-176-1610-1514-1419-1322-and-18-beta-3-released-3118/
  * https://www.postgresql.org/docs/release/17.6/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1756036800">- switch library to pg 18</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1756987200">- Sync spec file with version 18.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Update to 17.7:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/17.7/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 17.8:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/17.8/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 17.9 to fix two regressions in 17.8:
  * https://www.postgresql.org/docs/release/17.9/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1774872000">- Get rid of update-alternatives for openSUSE/SLE 16.0 and newer
  to support immutable systems and transactional updates.
  (jsc#PED-14825, bsc#1245875)</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1777550400">- bsc#1263804: After dropping update-alternatives we have to
  package /usr/bin/pg_config as an actual symlink, not %ghost.
- Fix spelling of build conditionals.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1778673600">- Update to version 17.10:
  * bsc#1265172, CVE-2026-6472: ensure the user has CREATE
    privilege on the schema specified
  * bsc#1265173, CVE-2026-6473: integer overflows in
    memory-allocation calculations
  * bsc#1265174, CVE-2026-6474: Guard against malicious time zone
    names
  * bsc#1265175, CVE-2026-6475: Prevent path traversal in
    pg_basebackup and pg_rewind
  * bsc#1265176, CVE-2026-6476: Properly quote subscription names
    in pg_createsubscriber
  * bsc#1265177, CVE-2026-6477: Mark PQfn() as unsafe, and avoid
    using it within libpq
  * bsc#1265178, CVE-2026-6478: Use timing-safe string comparisons
    in authentication code
  * bsc#1265179, CVE-2026-6479: Prevent unbounded recursion while
    processing startup packets
  * bsc#1265181, CVE-2026-6637: Prevent SQL injection and buffer
    overruns in contrib/spi
  * bsc#1265182, CVE-2026-6638: Properly quote object names in
    logical replication origin checks
  * https://www.postgresql.org/docs/release/17.10/</changelog>
</package>
<package pkgid="e144d43d8ca512c30b27e081fdbf180f189de55358dcddcb2e4d7153d181047445aee9a6305124cb8458b54ea5dffdb3f883fba8008ffab671699ac2288efaed" name="postgresql17-docs" arch="noarch">
  <version epoch="0" ver="17.9" rel="53.1"/>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1727352000">- Upgrade to 17.0:
  * New memory management system for VACUUM, which reduces memory
    consumption and can improve overall vacuuming performance.
  * New SQL/JSON capabilities, including constructors, identity
    functions, and the JSON_TABLE() function, which converts JSON
    data into a table representation.
  * Various query performance improvements, including for
    sequential reads using streaming I/O, write throughput under
    high concurrency, and searches over multiple values in a btree
    index.
  * Logical replication enhancements, including:
    + Failover control
    + pg_createsubscriber, a utility that creates logical replicas
    from physical standbys
    + pg_upgrade now preserves replication slots on both publishers
    and subscribers
  * New client-side connection option, sslnegotiation=direct, that
    performs a direct TLS handshake to avoid a round-trip
    negotiation.
  * pg_basebackup now supports incremental backup.
  * COPY adds a new option, ON_ERROR ignore, that allows a copy
    operation to continue in the event of an error.
  * https://www.postgresql.org/about/news/p-2936/
  * https://www.postgresql.org/docs/17/release-17.html</changelog>
  <changelog author="Fabian Vogt &lt;fvogt@suse.com&gt;" date="1728302400">- Use cmake(LLVM) &lt; instead of &lt;= to also allow building against
  LLVM 18.1 and newer 18.x versions</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1730721600">- Add postgresql17-jsonb_jsonpath.patch as a temporary build fix.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1731499200">- Upgrade to 17.1:
  * CVE-2024-10976, bsc#1233323: Ensure cached plans are marked as
    dependent on the calling role when RLS applies to a
    non-top-level table reference.
  * CVE-2024-10977, bsc#1233325: Make libpq discard error messages
    received during SSL or GSS protocol negotiation.
  * CVE-2024-10978, bsc#1233326: Fix unintended interactions
    between SET SESSION AUTHORIZATION and SET ROLE
  * CVE-2024-10979, bsc#1233327: Prevent trusted PL/Perl code from
    changing environment variables.
  * obsoletes postgresql17-jsonb_jsonpath.patch
  * https://www.postgresql.org/about/news/p-2955/
  * https://www.postgresql.org/docs/release/17.1/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1732017600">- Upgrade to 17.2:
  * Repair ABI break for extensions that work with struct
    ResultRelInfo.
  * Restore functionality of ALTER {ROLE|DATABASE} SET role.
  * Fix cases where a logical replication slot's restart_lsn could
    go backwards.
  * Avoid deleting still-needed WAL files during pg_rewind.
  * Fix race conditions associated with dropping shared statistics
    entries.
  * Count index scans in contrib/bloom indexes in the statistics
    views, such as the pg_stat_user_indexes.idx_scan counter.
  * Fix crash when checking to see if an index's opclass options
    have changed.
  * Avoid assertion failure caused by disconnected NFA sub-graphs
    in regular expression parsing.
  * https://www.postgresql.org/about/news/p-2965/
  * https://www.postgresql.org/docs/release/17.2/</changelog>
  <changelog author="JS &lt;obs.coke518@passinbox.com&gt;" date="1735214400">- Disable LLVM JIT on loongarch64</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="JS &lt;obs.coke518@passinbox.com&gt;" date="1738152000">- Apply postgresql-tzdata2025a.patch regardless of
  whether LLVM JIT is enabled</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 17.3:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/17.3/
  * https://www.postgresql.org/about/news/-3015/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 17.4:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/17.4/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 17.5:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/17.5/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to Fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Update to 17.6
  * https://www.postgresql.org/about/news/postgresql-176-1610-1514-1419-1322-and-18-beta-3-released-3118/
  * https://www.postgresql.org/docs/release/17.6/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1756036800">- switch library to pg 18</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1756987200">- Sync spec file with version 18.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Update to 17.7:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/17.7/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 17.8:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/17.8/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 17.9 to fix two regressions in 17.8:
  * https://www.postgresql.org/docs/release/17.9/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
</package>
<package pkgid="80bc879fe3e97b6f783944f06b9651ff0043b949e29ff4d209e6a167ffe5bae0952384fa49fb2dfbb0897ee30837dd4a0ad62207ebe3bfd2b3c4e8965bdc9b6e" name="postgresql17-docs" arch="noarch">
  <version epoch="0" ver="17.9" rel="54.2"/>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1727352000">- Upgrade to 17.0:
  * New memory management system for VACUUM, which reduces memory
    consumption and can improve overall vacuuming performance.
  * New SQL/JSON capabilities, including constructors, identity
    functions, and the JSON_TABLE() function, which converts JSON
    data into a table representation.
  * Various query performance improvements, including for
    sequential reads using streaming I/O, write throughput under
    high concurrency, and searches over multiple values in a btree
    index.
  * Logical replication enhancements, including:
    + Failover control
    + pg_createsubscriber, a utility that creates logical replicas
    from physical standbys
    + pg_upgrade now preserves replication slots on both publishers
    and subscribers
  * New client-side connection option, sslnegotiation=direct, that
    performs a direct TLS handshake to avoid a round-trip
    negotiation.
  * pg_basebackup now supports incremental backup.
  * COPY adds a new option, ON_ERROR ignore, that allows a copy
    operation to continue in the event of an error.
  * https://www.postgresql.org/about/news/p-2936/
  * https://www.postgresql.org/docs/17/release-17.html</changelog>
  <changelog author="Fabian Vogt &lt;fvogt@suse.com&gt;" date="1728302400">- Use cmake(LLVM) &lt; instead of &lt;= to also allow building against
  LLVM 18.1 and newer 18.x versions</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1730721600">- Add postgresql17-jsonb_jsonpath.patch as a temporary build fix.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1731499200">- Upgrade to 17.1:
  * CVE-2024-10976, bsc#1233323: Ensure cached plans are marked as
    dependent on the calling role when RLS applies to a
    non-top-level table reference.
  * CVE-2024-10977, bsc#1233325: Make libpq discard error messages
    received during SSL or GSS protocol negotiation.
  * CVE-2024-10978, bsc#1233326: Fix unintended interactions
    between SET SESSION AUTHORIZATION and SET ROLE
  * CVE-2024-10979, bsc#1233327: Prevent trusted PL/Perl code from
    changing environment variables.
  * obsoletes postgresql17-jsonb_jsonpath.patch
  * https://www.postgresql.org/about/news/p-2955/
  * https://www.postgresql.org/docs/release/17.1/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1732017600">- Upgrade to 17.2:
  * Repair ABI break for extensions that work with struct
    ResultRelInfo.
  * Restore functionality of ALTER {ROLE|DATABASE} SET role.
  * Fix cases where a logical replication slot's restart_lsn could
    go backwards.
  * Avoid deleting still-needed WAL files during pg_rewind.
  * Fix race conditions associated with dropping shared statistics
    entries.
  * Count index scans in contrib/bloom indexes in the statistics
    views, such as the pg_stat_user_indexes.idx_scan counter.
  * Fix crash when checking to see if an index's opclass options
    have changed.
  * Avoid assertion failure caused by disconnected NFA sub-graphs
    in regular expression parsing.
  * https://www.postgresql.org/about/news/p-2965/
  * https://www.postgresql.org/docs/release/17.2/</changelog>
  <changelog author="JS &lt;obs.coke518@passinbox.com&gt;" date="1735214400">- Disable LLVM JIT on loongarch64</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="JS &lt;obs.coke518@passinbox.com&gt;" date="1738152000">- Apply postgresql-tzdata2025a.patch regardless of
  whether LLVM JIT is enabled</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 17.3:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/17.3/
  * https://www.postgresql.org/about/news/-3015/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 17.4:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/17.4/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 17.5:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/17.5/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to Fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Update to 17.6
  * https://www.postgresql.org/about/news/postgresql-176-1610-1514-1419-1322-and-18-beta-3-released-3118/
  * https://www.postgresql.org/docs/release/17.6/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1756036800">- switch library to pg 18</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1756987200">- Sync spec file with version 18.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Update to 17.7:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/17.7/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 17.8:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/17.8/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 17.9 to fix two regressions in 17.8:
  * https://www.postgresql.org/docs/release/17.9/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
</package>
<package pkgid="0eb23ac8ae11ac22229cf18438d835eaa7ecdf810b6ab77e348fb448c8ba918f137f32c69ae2e4862fcc5309aab9ab9ff9af367a78e576a81b176216707cddee" name="postgresql17-docs" arch="noarch">
  <version epoch="0" ver="17.9" rel="55.1"/>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1727352000">- Upgrade to 17.0:
  * New memory management system for VACUUM, which reduces memory
    consumption and can improve overall vacuuming performance.
  * New SQL/JSON capabilities, including constructors, identity
    functions, and the JSON_TABLE() function, which converts JSON
    data into a table representation.
  * Various query performance improvements, including for
    sequential reads using streaming I/O, write throughput under
    high concurrency, and searches over multiple values in a btree
    index.
  * Logical replication enhancements, including:
    + Failover control
    + pg_createsubscriber, a utility that creates logical replicas
    from physical standbys
    + pg_upgrade now preserves replication slots on both publishers
    and subscribers
  * New client-side connection option, sslnegotiation=direct, that
    performs a direct TLS handshake to avoid a round-trip
    negotiation.
  * pg_basebackup now supports incremental backup.
  * COPY adds a new option, ON_ERROR ignore, that allows a copy
    operation to continue in the event of an error.
  * https://www.postgresql.org/about/news/p-2936/
  * https://www.postgresql.org/docs/17/release-17.html</changelog>
  <changelog author="Fabian Vogt &lt;fvogt@suse.com&gt;" date="1728302400">- Use cmake(LLVM) &lt; instead of &lt;= to also allow building against
  LLVM 18.1 and newer 18.x versions</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1730721600">- Add postgresql17-jsonb_jsonpath.patch as a temporary build fix.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1731499200">- Upgrade to 17.1:
  * CVE-2024-10976, bsc#1233323: Ensure cached plans are marked as
    dependent on the calling role when RLS applies to a
    non-top-level table reference.
  * CVE-2024-10977, bsc#1233325: Make libpq discard error messages
    received during SSL or GSS protocol negotiation.
  * CVE-2024-10978, bsc#1233326: Fix unintended interactions
    between SET SESSION AUTHORIZATION and SET ROLE
  * CVE-2024-10979, bsc#1233327: Prevent trusted PL/Perl code from
    changing environment variables.
  * obsoletes postgresql17-jsonb_jsonpath.patch
  * https://www.postgresql.org/about/news/p-2955/
  * https://www.postgresql.org/docs/release/17.1/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1732017600">- Upgrade to 17.2:
  * Repair ABI break for extensions that work with struct
    ResultRelInfo.
  * Restore functionality of ALTER {ROLE|DATABASE} SET role.
  * Fix cases where a logical replication slot's restart_lsn could
    go backwards.
  * Avoid deleting still-needed WAL files during pg_rewind.
  * Fix race conditions associated with dropping shared statistics
    entries.
  * Count index scans in contrib/bloom indexes in the statistics
    views, such as the pg_stat_user_indexes.idx_scan counter.
  * Fix crash when checking to see if an index's opclass options
    have changed.
  * Avoid assertion failure caused by disconnected NFA sub-graphs
    in regular expression parsing.
  * https://www.postgresql.org/about/news/p-2965/
  * https://www.postgresql.org/docs/release/17.2/</changelog>
  <changelog author="JS &lt;obs.coke518@passinbox.com&gt;" date="1735214400">- Disable LLVM JIT on loongarch64</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="JS &lt;obs.coke518@passinbox.com&gt;" date="1738152000">- Apply postgresql-tzdata2025a.patch regardless of
  whether LLVM JIT is enabled</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 17.3:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/17.3/
  * https://www.postgresql.org/about/news/-3015/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 17.4:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/17.4/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 17.5:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/17.5/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to Fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Update to 17.6
  * https://www.postgresql.org/about/news/postgresql-176-1610-1514-1419-1322-and-18-beta-3-released-3118/
  * https://www.postgresql.org/docs/release/17.6/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1756036800">- switch library to pg 18</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1756987200">- Sync spec file with version 18.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Update to 17.7:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/17.7/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 17.8:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/17.8/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 17.9 to fix two regressions in 17.8:
  * https://www.postgresql.org/docs/release/17.9/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
</package>
<package pkgid="b40460ca1713d1af23b7c5dd03a3dd4d982f31ed429843ad7284c67c8c4b12925e9c6088f1b8865991eed5d00d4c68eadf1b6206e026e8fead862b5aac462b7f" name="postgresql17-llvmjit" arch="x86_64">
  <version epoch="0" ver="17.10" rel="69.2"/>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1731499200">- Upgrade to 17.1:
  * CVE-2024-10976, bsc#1233323: Ensure cached plans are marked as
    dependent on the calling role when RLS applies to a
    non-top-level table reference.
  * CVE-2024-10977, bsc#1233325: Make libpq discard error messages
    received during SSL or GSS protocol negotiation.
  * CVE-2024-10978, bsc#1233326: Fix unintended interactions
    between SET SESSION AUTHORIZATION and SET ROLE
  * CVE-2024-10979, bsc#1233327: Prevent trusted PL/Perl code from
    changing environment variables.
  * obsoletes postgresql17-jsonb_jsonpath.patch
  * https://www.postgresql.org/about/news/p-2955/
  * https://www.postgresql.org/docs/release/17.1/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1732017600">- Upgrade to 17.2:
  * Repair ABI break for extensions that work with struct
    ResultRelInfo.
  * Restore functionality of ALTER {ROLE|DATABASE} SET role.
  * Fix cases where a logical replication slot's restart_lsn could
    go backwards.
  * Avoid deleting still-needed WAL files during pg_rewind.
  * Fix race conditions associated with dropping shared statistics
    entries.
  * Count index scans in contrib/bloom indexes in the statistics
    views, such as the pg_stat_user_indexes.idx_scan counter.
  * Fix crash when checking to see if an index's opclass options
    have changed.
  * Avoid assertion failure caused by disconnected NFA sub-graphs
    in regular expression parsing.
  * https://www.postgresql.org/about/news/p-2965/
  * https://www.postgresql.org/docs/release/17.2/</changelog>
  <changelog author="JS &lt;obs.coke518@passinbox.com&gt;" date="1735214400">- Disable LLVM JIT on loongarch64</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="JS &lt;obs.coke518@passinbox.com&gt;" date="1738152000">- Apply postgresql-tzdata2025a.patch regardless of
  whether LLVM JIT is enabled</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 17.3:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/17.3/
  * https://www.postgresql.org/about/news/-3015/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 17.4:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/17.4/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 17.5:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/17.5/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to Fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Update to 17.6
  * https://www.postgresql.org/about/news/postgresql-176-1610-1514-1419-1322-and-18-beta-3-released-3118/
  * https://www.postgresql.org/docs/release/17.6/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1756036800">- switch library to pg 18</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1756987200">- Sync spec file with version 18.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Update to 17.7:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/17.7/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 17.8:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/17.8/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 17.9 to fix two regressions in 17.8:
  * https://www.postgresql.org/docs/release/17.9/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1774872000">- Get rid of update-alternatives for openSUSE/SLE 16.0 and newer
  to support immutable systems and transactional updates.
  (jsc#PED-14825, bsc#1245875)</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1777550400">- bsc#1263804: After dropping update-alternatives we have to
  package /usr/bin/pg_config as an actual symlink, not %ghost.
- Fix spelling of build conditionals.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1778673600">- Update to version 17.10:
  * bsc#1265172, CVE-2026-6472: ensure the user has CREATE
    privilege on the schema specified
  * bsc#1265173, CVE-2026-6473: integer overflows in
    memory-allocation calculations
  * bsc#1265174, CVE-2026-6474: Guard against malicious time zone
    names
  * bsc#1265175, CVE-2026-6475: Prevent path traversal in
    pg_basebackup and pg_rewind
  * bsc#1265176, CVE-2026-6476: Properly quote subscription names
    in pg_createsubscriber
  * bsc#1265177, CVE-2026-6477: Mark PQfn() as unsafe, and avoid
    using it within libpq
  * bsc#1265178, CVE-2026-6478: Use timing-safe string comparisons
    in authentication code
  * bsc#1265179, CVE-2026-6479: Prevent unbounded recursion while
    processing startup packets
  * bsc#1265181, CVE-2026-6637: Prevent SQL injection and buffer
    overruns in contrib/spi
  * bsc#1265182, CVE-2026-6638: Properly quote object names in
    logical replication origin checks
  * https://www.postgresql.org/docs/release/17.10/</changelog>
</package>
<package pkgid="7086e3d3457ad86c07b96cd875c4a47a8afe479f0f18b86873805061e958f8f74a5f79d705af4ebd355eaa2357f704cbefb656fa622bdcdf4b8460e72d8d3a70" name="postgresql17-llvmjit" arch="s390x">
  <version epoch="0" ver="17.9" rel="53.1"/>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1727352000">- Upgrade to 17.0:
  * New memory management system for VACUUM, which reduces memory
    consumption and can improve overall vacuuming performance.
  * New SQL/JSON capabilities, including constructors, identity
    functions, and the JSON_TABLE() function, which converts JSON
    data into a table representation.
  * Various query performance improvements, including for
    sequential reads using streaming I/O, write throughput under
    high concurrency, and searches over multiple values in a btree
    index.
  * Logical replication enhancements, including:
    + Failover control
    + pg_createsubscriber, a utility that creates logical replicas
    from physical standbys
    + pg_upgrade now preserves replication slots on both publishers
    and subscribers
  * New client-side connection option, sslnegotiation=direct, that
    performs a direct TLS handshake to avoid a round-trip
    negotiation.
  * pg_basebackup now supports incremental backup.
  * COPY adds a new option, ON_ERROR ignore, that allows a copy
    operation to continue in the event of an error.
  * https://www.postgresql.org/about/news/p-2936/
  * https://www.postgresql.org/docs/17/release-17.html</changelog>
  <changelog author="Fabian Vogt &lt;fvogt@suse.com&gt;" date="1728302400">- Use cmake(LLVM) &lt; instead of &lt;= to also allow building against
  LLVM 18.1 and newer 18.x versions</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1730721600">- Add postgresql17-jsonb_jsonpath.patch as a temporary build fix.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1731499200">- Upgrade to 17.1:
  * CVE-2024-10976, bsc#1233323: Ensure cached plans are marked as
    dependent on the calling role when RLS applies to a
    non-top-level table reference.
  * CVE-2024-10977, bsc#1233325: Make libpq discard error messages
    received during SSL or GSS protocol negotiation.
  * CVE-2024-10978, bsc#1233326: Fix unintended interactions
    between SET SESSION AUTHORIZATION and SET ROLE
  * CVE-2024-10979, bsc#1233327: Prevent trusted PL/Perl code from
    changing environment variables.
  * obsoletes postgresql17-jsonb_jsonpath.patch
  * https://www.postgresql.org/about/news/p-2955/
  * https://www.postgresql.org/docs/release/17.1/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1732017600">- Upgrade to 17.2:
  * Repair ABI break for extensions that work with struct
    ResultRelInfo.
  * Restore functionality of ALTER {ROLE|DATABASE} SET role.
  * Fix cases where a logical replication slot's restart_lsn could
    go backwards.
  * Avoid deleting still-needed WAL files during pg_rewind.
  * Fix race conditions associated with dropping shared statistics
    entries.
  * Count index scans in contrib/bloom indexes in the statistics
    views, such as the pg_stat_user_indexes.idx_scan counter.
  * Fix crash when checking to see if an index's opclass options
    have changed.
  * Avoid assertion failure caused by disconnected NFA sub-graphs
    in regular expression parsing.
  * https://www.postgresql.org/about/news/p-2965/
  * https://www.postgresql.org/docs/release/17.2/</changelog>
  <changelog author="JS &lt;obs.coke518@passinbox.com&gt;" date="1735214400">- Disable LLVM JIT on loongarch64</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="JS &lt;obs.coke518@passinbox.com&gt;" date="1738152000">- Apply postgresql-tzdata2025a.patch regardless of
  whether LLVM JIT is enabled</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 17.3:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/17.3/
  * https://www.postgresql.org/about/news/-3015/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 17.4:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/17.4/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 17.5:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/17.5/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to Fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Update to 17.6
  * https://www.postgresql.org/about/news/postgresql-176-1610-1514-1419-1322-and-18-beta-3-released-3118/
  * https://www.postgresql.org/docs/release/17.6/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1756036800">- switch library to pg 18</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1756987200">- Sync spec file with version 18.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Update to 17.7:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/17.7/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 17.8:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/17.8/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 17.9 to fix two regressions in 17.8:
  * https://www.postgresql.org/docs/release/17.9/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
</package>
<package pkgid="ccb8e800d9f666da9df7d6643a985afab0f6991f3438905f7e7915799fa733b7dc561be60882b40915d42991993dbcfc255b92c33c6dd07f98275b63a4ead1b9" name="postgresql17-llvmjit" arch="aarch64">
  <version epoch="0" ver="17.9" rel="54.2"/>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1727352000">- Upgrade to 17.0:
  * New memory management system for VACUUM, which reduces memory
    consumption and can improve overall vacuuming performance.
  * New SQL/JSON capabilities, including constructors, identity
    functions, and the JSON_TABLE() function, which converts JSON
    data into a table representation.
  * Various query performance improvements, including for
    sequential reads using streaming I/O, write throughput under
    high concurrency, and searches over multiple values in a btree
    index.
  * Logical replication enhancements, including:
    + Failover control
    + pg_createsubscriber, a utility that creates logical replicas
    from physical standbys
    + pg_upgrade now preserves replication slots on both publishers
    and subscribers
  * New client-side connection option, sslnegotiation=direct, that
    performs a direct TLS handshake to avoid a round-trip
    negotiation.
  * pg_basebackup now supports incremental backup.
  * COPY adds a new option, ON_ERROR ignore, that allows a copy
    operation to continue in the event of an error.
  * https://www.postgresql.org/about/news/p-2936/
  * https://www.postgresql.org/docs/17/release-17.html</changelog>
  <changelog author="Fabian Vogt &lt;fvogt@suse.com&gt;" date="1728302400">- Use cmake(LLVM) &lt; instead of &lt;= to also allow building against
  LLVM 18.1 and newer 18.x versions</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1730721600">- Add postgresql17-jsonb_jsonpath.patch as a temporary build fix.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1731499200">- Upgrade to 17.1:
  * CVE-2024-10976, bsc#1233323: Ensure cached plans are marked as
    dependent on the calling role when RLS applies to a
    non-top-level table reference.
  * CVE-2024-10977, bsc#1233325: Make libpq discard error messages
    received during SSL or GSS protocol negotiation.
  * CVE-2024-10978, bsc#1233326: Fix unintended interactions
    between SET SESSION AUTHORIZATION and SET ROLE
  * CVE-2024-10979, bsc#1233327: Prevent trusted PL/Perl code from
    changing environment variables.
  * obsoletes postgresql17-jsonb_jsonpath.patch
  * https://www.postgresql.org/about/news/p-2955/
  * https://www.postgresql.org/docs/release/17.1/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1732017600">- Upgrade to 17.2:
  * Repair ABI break for extensions that work with struct
    ResultRelInfo.
  * Restore functionality of ALTER {ROLE|DATABASE} SET role.
  * Fix cases where a logical replication slot's restart_lsn could
    go backwards.
  * Avoid deleting still-needed WAL files during pg_rewind.
  * Fix race conditions associated with dropping shared statistics
    entries.
  * Count index scans in contrib/bloom indexes in the statistics
    views, such as the pg_stat_user_indexes.idx_scan counter.
  * Fix crash when checking to see if an index's opclass options
    have changed.
  * Avoid assertion failure caused by disconnected NFA sub-graphs
    in regular expression parsing.
  * https://www.postgresql.org/about/news/p-2965/
  * https://www.postgresql.org/docs/release/17.2/</changelog>
  <changelog author="JS &lt;obs.coke518@passinbox.com&gt;" date="1735214400">- Disable LLVM JIT on loongarch64</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="JS &lt;obs.coke518@passinbox.com&gt;" date="1738152000">- Apply postgresql-tzdata2025a.patch regardless of
  whether LLVM JIT is enabled</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 17.3:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/17.3/
  * https://www.postgresql.org/about/news/-3015/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 17.4:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/17.4/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 17.5:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/17.5/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to Fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Update to 17.6
  * https://www.postgresql.org/about/news/postgresql-176-1610-1514-1419-1322-and-18-beta-3-released-3118/
  * https://www.postgresql.org/docs/release/17.6/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1756036800">- switch library to pg 18</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1756987200">- Sync spec file with version 18.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Update to 17.7:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/17.7/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 17.8:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/17.8/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 17.9 to fix two regressions in 17.8:
  * https://www.postgresql.org/docs/release/17.9/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
</package>
<package pkgid="d48438170a56d87b47058ca6358b8578bbf2c4f60fe5380e326dbba2a03f720284ad191e658f39572aed1f296d001bff38a9f2befdb3f6d87f3ffe4eb1b3a28a" name="postgresql17-llvmjit" arch="ppc64le">
  <version epoch="0" ver="17.9" rel="55.1"/>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1727352000">- Upgrade to 17.0:
  * New memory management system for VACUUM, which reduces memory
    consumption and can improve overall vacuuming performance.
  * New SQL/JSON capabilities, including constructors, identity
    functions, and the JSON_TABLE() function, which converts JSON
    data into a table representation.
  * Various query performance improvements, including for
    sequential reads using streaming I/O, write throughput under
    high concurrency, and searches over multiple values in a btree
    index.
  * Logical replication enhancements, including:
    + Failover control
    + pg_createsubscriber, a utility that creates logical replicas
    from physical standbys
    + pg_upgrade now preserves replication slots on both publishers
    and subscribers
  * New client-side connection option, sslnegotiation=direct, that
    performs a direct TLS handshake to avoid a round-trip
    negotiation.
  * pg_basebackup now supports incremental backup.
  * COPY adds a new option, ON_ERROR ignore, that allows a copy
    operation to continue in the event of an error.
  * https://www.postgresql.org/about/news/p-2936/
  * https://www.postgresql.org/docs/17/release-17.html</changelog>
  <changelog author="Fabian Vogt &lt;fvogt@suse.com&gt;" date="1728302400">- Use cmake(LLVM) &lt; instead of &lt;= to also allow building against
  LLVM 18.1 and newer 18.x versions</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1730721600">- Add postgresql17-jsonb_jsonpath.patch as a temporary build fix.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1731499200">- Upgrade to 17.1:
  * CVE-2024-10976, bsc#1233323: Ensure cached plans are marked as
    dependent on the calling role when RLS applies to a
    non-top-level table reference.
  * CVE-2024-10977, bsc#1233325: Make libpq discard error messages
    received during SSL or GSS protocol negotiation.
  * CVE-2024-10978, bsc#1233326: Fix unintended interactions
    between SET SESSION AUTHORIZATION and SET ROLE
  * CVE-2024-10979, bsc#1233327: Prevent trusted PL/Perl code from
    changing environment variables.
  * obsoletes postgresql17-jsonb_jsonpath.patch
  * https://www.postgresql.org/about/news/p-2955/
  * https://www.postgresql.org/docs/release/17.1/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1732017600">- Upgrade to 17.2:
  * Repair ABI break for extensions that work with struct
    ResultRelInfo.
  * Restore functionality of ALTER {ROLE|DATABASE} SET role.
  * Fix cases where a logical replication slot's restart_lsn could
    go backwards.
  * Avoid deleting still-needed WAL files during pg_rewind.
  * Fix race conditions associated with dropping shared statistics
    entries.
  * Count index scans in contrib/bloom indexes in the statistics
    views, such as the pg_stat_user_indexes.idx_scan counter.
  * Fix crash when checking to see if an index's opclass options
    have changed.
  * Avoid assertion failure caused by disconnected NFA sub-graphs
    in regular expression parsing.
  * https://www.postgresql.org/about/news/p-2965/
  * https://www.postgresql.org/docs/release/17.2/</changelog>
  <changelog author="JS &lt;obs.coke518@passinbox.com&gt;" date="1735214400">- Disable LLVM JIT on loongarch64</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="JS &lt;obs.coke518@passinbox.com&gt;" date="1738152000">- Apply postgresql-tzdata2025a.patch regardless of
  whether LLVM JIT is enabled</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 17.3:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/17.3/
  * https://www.postgresql.org/about/news/-3015/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 17.4:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/17.4/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 17.5:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/17.5/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to Fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Update to 17.6
  * https://www.postgresql.org/about/news/postgresql-176-1610-1514-1419-1322-and-18-beta-3-released-3118/
  * https://www.postgresql.org/docs/release/17.6/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1756036800">- switch library to pg 18</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1756987200">- Sync spec file with version 18.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Update to 17.7:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/17.7/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 17.8:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/17.8/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 17.9 to fix two regressions in 17.8:
  * https://www.postgresql.org/docs/release/17.9/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
</package>
<package pkgid="f995c2de498c259d57e6ae994e771dbcaca5599ca3e9ada25b7b75f6fe79f0516c86b1a002c3ad451de6afbf9919947c254f98a812c0fc9f32206575e017265e" name="postgresql17-llvmjit-devel" arch="x86_64">
  <version epoch="0" ver="17.10" rel="69.2"/>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1731499200">- Upgrade to 17.1:
  * CVE-2024-10976, bsc#1233323: Ensure cached plans are marked as
    dependent on the calling role when RLS applies to a
    non-top-level table reference.
  * CVE-2024-10977, bsc#1233325: Make libpq discard error messages
    received during SSL or GSS protocol negotiation.
  * CVE-2024-10978, bsc#1233326: Fix unintended interactions
    between SET SESSION AUTHORIZATION and SET ROLE
  * CVE-2024-10979, bsc#1233327: Prevent trusted PL/Perl code from
    changing environment variables.
  * obsoletes postgresql17-jsonb_jsonpath.patch
  * https://www.postgresql.org/about/news/p-2955/
  * https://www.postgresql.org/docs/release/17.1/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1732017600">- Upgrade to 17.2:
  * Repair ABI break for extensions that work with struct
    ResultRelInfo.
  * Restore functionality of ALTER {ROLE|DATABASE} SET role.
  * Fix cases where a logical replication slot's restart_lsn could
    go backwards.
  * Avoid deleting still-needed WAL files during pg_rewind.
  * Fix race conditions associated with dropping shared statistics
    entries.
  * Count index scans in contrib/bloom indexes in the statistics
    views, such as the pg_stat_user_indexes.idx_scan counter.
  * Fix crash when checking to see if an index's opclass options
    have changed.
  * Avoid assertion failure caused by disconnected NFA sub-graphs
    in regular expression parsing.
  * https://www.postgresql.org/about/news/p-2965/
  * https://www.postgresql.org/docs/release/17.2/</changelog>
  <changelog author="JS &lt;obs.coke518@passinbox.com&gt;" date="1735214400">- Disable LLVM JIT on loongarch64</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="JS &lt;obs.coke518@passinbox.com&gt;" date="1738152000">- Apply postgresql-tzdata2025a.patch regardless of
  whether LLVM JIT is enabled</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 17.3:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/17.3/
  * https://www.postgresql.org/about/news/-3015/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 17.4:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/17.4/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 17.5:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/17.5/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to Fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Update to 17.6
  * https://www.postgresql.org/about/news/postgresql-176-1610-1514-1419-1322-and-18-beta-3-released-3118/
  * https://www.postgresql.org/docs/release/17.6/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1756036800">- switch library to pg 18</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1756987200">- Sync spec file with version 18.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Update to 17.7:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/17.7/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 17.8:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/17.8/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 17.9 to fix two regressions in 17.8:
  * https://www.postgresql.org/docs/release/17.9/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1774872000">- Get rid of update-alternatives for openSUSE/SLE 16.0 and newer
  to support immutable systems and transactional updates.
  (jsc#PED-14825, bsc#1245875)</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1777550400">- bsc#1263804: After dropping update-alternatives we have to
  package /usr/bin/pg_config as an actual symlink, not %ghost.
- Fix spelling of build conditionals.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1778673600">- Update to version 17.10:
  * bsc#1265172, CVE-2026-6472: ensure the user has CREATE
    privilege on the schema specified
  * bsc#1265173, CVE-2026-6473: integer overflows in
    memory-allocation calculations
  * bsc#1265174, CVE-2026-6474: Guard against malicious time zone
    names
  * bsc#1265175, CVE-2026-6475: Prevent path traversal in
    pg_basebackup and pg_rewind
  * bsc#1265176, CVE-2026-6476: Properly quote subscription names
    in pg_createsubscriber
  * bsc#1265177, CVE-2026-6477: Mark PQfn() as unsafe, and avoid
    using it within libpq
  * bsc#1265178, CVE-2026-6478: Use timing-safe string comparisons
    in authentication code
  * bsc#1265179, CVE-2026-6479: Prevent unbounded recursion while
    processing startup packets
  * bsc#1265181, CVE-2026-6637: Prevent SQL injection and buffer
    overruns in contrib/spi
  * bsc#1265182, CVE-2026-6638: Properly quote object names in
    logical replication origin checks
  * https://www.postgresql.org/docs/release/17.10/</changelog>
</package>
<package pkgid="d229ef0ae2f1b66a78e7c191e289efbbd6187bf9990e4cb3f0a08ba1bd45921a2e76a12e0df9f3f208abd9be6e89e8e9b4e497d23dae9725306ae9682b00f604" name="postgresql17-llvmjit-devel" arch="s390x">
  <version epoch="0" ver="17.9" rel="53.1"/>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1727352000">- Upgrade to 17.0:
  * New memory management system for VACUUM, which reduces memory
    consumption and can improve overall vacuuming performance.
  * New SQL/JSON capabilities, including constructors, identity
    functions, and the JSON_TABLE() function, which converts JSON
    data into a table representation.
  * Various query performance improvements, including for
    sequential reads using streaming I/O, write throughput under
    high concurrency, and searches over multiple values in a btree
    index.
  * Logical replication enhancements, including:
    + Failover control
    + pg_createsubscriber, a utility that creates logical replicas
    from physical standbys
    + pg_upgrade now preserves replication slots on both publishers
    and subscribers
  * New client-side connection option, sslnegotiation=direct, that
    performs a direct TLS handshake to avoid a round-trip
    negotiation.
  * pg_basebackup now supports incremental backup.
  * COPY adds a new option, ON_ERROR ignore, that allows a copy
    operation to continue in the event of an error.
  * https://www.postgresql.org/about/news/p-2936/
  * https://www.postgresql.org/docs/17/release-17.html</changelog>
  <changelog author="Fabian Vogt &lt;fvogt@suse.com&gt;" date="1728302400">- Use cmake(LLVM) &lt; instead of &lt;= to also allow building against
  LLVM 18.1 and newer 18.x versions</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1730721600">- Add postgresql17-jsonb_jsonpath.patch as a temporary build fix.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1731499200">- Upgrade to 17.1:
  * CVE-2024-10976, bsc#1233323: Ensure cached plans are marked as
    dependent on the calling role when RLS applies to a
    non-top-level table reference.
  * CVE-2024-10977, bsc#1233325: Make libpq discard error messages
    received during SSL or GSS protocol negotiation.
  * CVE-2024-10978, bsc#1233326: Fix unintended interactions
    between SET SESSION AUTHORIZATION and SET ROLE
  * CVE-2024-10979, bsc#1233327: Prevent trusted PL/Perl code from
    changing environment variables.
  * obsoletes postgresql17-jsonb_jsonpath.patch
  * https://www.postgresql.org/about/news/p-2955/
  * https://www.postgresql.org/docs/release/17.1/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1732017600">- Upgrade to 17.2:
  * Repair ABI break for extensions that work with struct
    ResultRelInfo.
  * Restore functionality of ALTER {ROLE|DATABASE} SET role.
  * Fix cases where a logical replication slot's restart_lsn could
    go backwards.
  * Avoid deleting still-needed WAL files during pg_rewind.
  * Fix race conditions associated with dropping shared statistics
    entries.
  * Count index scans in contrib/bloom indexes in the statistics
    views, such as the pg_stat_user_indexes.idx_scan counter.
  * Fix crash when checking to see if an index's opclass options
    have changed.
  * Avoid assertion failure caused by disconnected NFA sub-graphs
    in regular expression parsing.
  * https://www.postgresql.org/about/news/p-2965/
  * https://www.postgresql.org/docs/release/17.2/</changelog>
  <changelog author="JS &lt;obs.coke518@passinbox.com&gt;" date="1735214400">- Disable LLVM JIT on loongarch64</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="JS &lt;obs.coke518@passinbox.com&gt;" date="1738152000">- Apply postgresql-tzdata2025a.patch regardless of
  whether LLVM JIT is enabled</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 17.3:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/17.3/
  * https://www.postgresql.org/about/news/-3015/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 17.4:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/17.4/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 17.5:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/17.5/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to Fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Update to 17.6
  * https://www.postgresql.org/about/news/postgresql-176-1610-1514-1419-1322-and-18-beta-3-released-3118/
  * https://www.postgresql.org/docs/release/17.6/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1756036800">- switch library to pg 18</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1756987200">- Sync spec file with version 18.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Update to 17.7:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/17.7/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 17.8:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/17.8/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 17.9 to fix two regressions in 17.8:
  * https://www.postgresql.org/docs/release/17.9/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
</package>
<package pkgid="1438088962086d500fb48daac8cb237cc00c8e63b9bcd3d4ebf9d72392914fbc0cde721f2b617b31fc3aa87bf10c77bb98b38aebb183d67ac32a7629d502ec46" name="postgresql17-llvmjit-devel" arch="aarch64">
  <version epoch="0" ver="17.9" rel="54.2"/>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1727352000">- Upgrade to 17.0:
  * New memory management system for VACUUM, which reduces memory
    consumption and can improve overall vacuuming performance.
  * New SQL/JSON capabilities, including constructors, identity
    functions, and the JSON_TABLE() function, which converts JSON
    data into a table representation.
  * Various query performance improvements, including for
    sequential reads using streaming I/O, write throughput under
    high concurrency, and searches over multiple values in a btree
    index.
  * Logical replication enhancements, including:
    + Failover control
    + pg_createsubscriber, a utility that creates logical replicas
    from physical standbys
    + pg_upgrade now preserves replication slots on both publishers
    and subscribers
  * New client-side connection option, sslnegotiation=direct, that
    performs a direct TLS handshake to avoid a round-trip
    negotiation.
  * pg_basebackup now supports incremental backup.
  * COPY adds a new option, ON_ERROR ignore, that allows a copy
    operation to continue in the event of an error.
  * https://www.postgresql.org/about/news/p-2936/
  * https://www.postgresql.org/docs/17/release-17.html</changelog>
  <changelog author="Fabian Vogt &lt;fvogt@suse.com&gt;" date="1728302400">- Use cmake(LLVM) &lt; instead of &lt;= to also allow building against
  LLVM 18.1 and newer 18.x versions</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1730721600">- Add postgresql17-jsonb_jsonpath.patch as a temporary build fix.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1731499200">- Upgrade to 17.1:
  * CVE-2024-10976, bsc#1233323: Ensure cached plans are marked as
    dependent on the calling role when RLS applies to a
    non-top-level table reference.
  * CVE-2024-10977, bsc#1233325: Make libpq discard error messages
    received during SSL or GSS protocol negotiation.
  * CVE-2024-10978, bsc#1233326: Fix unintended interactions
    between SET SESSION AUTHORIZATION and SET ROLE
  * CVE-2024-10979, bsc#1233327: Prevent trusted PL/Perl code from
    changing environment variables.
  * obsoletes postgresql17-jsonb_jsonpath.patch
  * https://www.postgresql.org/about/news/p-2955/
  * https://www.postgresql.org/docs/release/17.1/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1732017600">- Upgrade to 17.2:
  * Repair ABI break for extensions that work with struct
    ResultRelInfo.
  * Restore functionality of ALTER {ROLE|DATABASE} SET role.
  * Fix cases where a logical replication slot's restart_lsn could
    go backwards.
  * Avoid deleting still-needed WAL files during pg_rewind.
  * Fix race conditions associated with dropping shared statistics
    entries.
  * Count index scans in contrib/bloom indexes in the statistics
    views, such as the pg_stat_user_indexes.idx_scan counter.
  * Fix crash when checking to see if an index's opclass options
    have changed.
  * Avoid assertion failure caused by disconnected NFA sub-graphs
    in regular expression parsing.
  * https://www.postgresql.org/about/news/p-2965/
  * https://www.postgresql.org/docs/release/17.2/</changelog>
  <changelog author="JS &lt;obs.coke518@passinbox.com&gt;" date="1735214400">- Disable LLVM JIT on loongarch64</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="JS &lt;obs.coke518@passinbox.com&gt;" date="1738152000">- Apply postgresql-tzdata2025a.patch regardless of
  whether LLVM JIT is enabled</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 17.3:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/17.3/
  * https://www.postgresql.org/about/news/-3015/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 17.4:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/17.4/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 17.5:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/17.5/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to Fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Update to 17.6
  * https://www.postgresql.org/about/news/postgresql-176-1610-1514-1419-1322-and-18-beta-3-released-3118/
  * https://www.postgresql.org/docs/release/17.6/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1756036800">- switch library to pg 18</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1756987200">- Sync spec file with version 18.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Update to 17.7:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/17.7/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 17.8:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/17.8/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 17.9 to fix two regressions in 17.8:
  * https://www.postgresql.org/docs/release/17.9/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
</package>
<package pkgid="154dfe545e6b683786f50408bfa93c2e1b822184c900de706f12288c044a31a995d012637380f797b0ca7e41618867a65608c7be11983ac4567c13560ada2653" name="postgresql17-llvmjit-devel" arch="ppc64le">
  <version epoch="0" ver="17.9" rel="55.1"/>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1727352000">- Upgrade to 17.0:
  * New memory management system for VACUUM, which reduces memory
    consumption and can improve overall vacuuming performance.
  * New SQL/JSON capabilities, including constructors, identity
    functions, and the JSON_TABLE() function, which converts JSON
    data into a table representation.
  * Various query performance improvements, including for
    sequential reads using streaming I/O, write throughput under
    high concurrency, and searches over multiple values in a btree
    index.
  * Logical replication enhancements, including:
    + Failover control
    + pg_createsubscriber, a utility that creates logical replicas
    from physical standbys
    + pg_upgrade now preserves replication slots on both publishers
    and subscribers
  * New client-side connection option, sslnegotiation=direct, that
    performs a direct TLS handshake to avoid a round-trip
    negotiation.
  * pg_basebackup now supports incremental backup.
  * COPY adds a new option, ON_ERROR ignore, that allows a copy
    operation to continue in the event of an error.
  * https://www.postgresql.org/about/news/p-2936/
  * https://www.postgresql.org/docs/17/release-17.html</changelog>
  <changelog author="Fabian Vogt &lt;fvogt@suse.com&gt;" date="1728302400">- Use cmake(LLVM) &lt; instead of &lt;= to also allow building against
  LLVM 18.1 and newer 18.x versions</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1730721600">- Add postgresql17-jsonb_jsonpath.patch as a temporary build fix.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1731499200">- Upgrade to 17.1:
  * CVE-2024-10976, bsc#1233323: Ensure cached plans are marked as
    dependent on the calling role when RLS applies to a
    non-top-level table reference.
  * CVE-2024-10977, bsc#1233325: Make libpq discard error messages
    received during SSL or GSS protocol negotiation.
  * CVE-2024-10978, bsc#1233326: Fix unintended interactions
    between SET SESSION AUTHORIZATION and SET ROLE
  * CVE-2024-10979, bsc#1233327: Prevent trusted PL/Perl code from
    changing environment variables.
  * obsoletes postgresql17-jsonb_jsonpath.patch
  * https://www.postgresql.org/about/news/p-2955/
  * https://www.postgresql.org/docs/release/17.1/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1732017600">- Upgrade to 17.2:
  * Repair ABI break for extensions that work with struct
    ResultRelInfo.
  * Restore functionality of ALTER {ROLE|DATABASE} SET role.
  * Fix cases where a logical replication slot's restart_lsn could
    go backwards.
  * Avoid deleting still-needed WAL files during pg_rewind.
  * Fix race conditions associated with dropping shared statistics
    entries.
  * Count index scans in contrib/bloom indexes in the statistics
    views, such as the pg_stat_user_indexes.idx_scan counter.
  * Fix crash when checking to see if an index's opclass options
    have changed.
  * Avoid assertion failure caused by disconnected NFA sub-graphs
    in regular expression parsing.
  * https://www.postgresql.org/about/news/p-2965/
  * https://www.postgresql.org/docs/release/17.2/</changelog>
  <changelog author="JS &lt;obs.coke518@passinbox.com&gt;" date="1735214400">- Disable LLVM JIT on loongarch64</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="JS &lt;obs.coke518@passinbox.com&gt;" date="1738152000">- Apply postgresql-tzdata2025a.patch regardless of
  whether LLVM JIT is enabled</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 17.3:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/17.3/
  * https://www.postgresql.org/about/news/-3015/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 17.4:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/17.4/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 17.5:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/17.5/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to Fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Update to 17.6
  * https://www.postgresql.org/about/news/postgresql-176-1610-1514-1419-1322-and-18-beta-3-released-3118/
  * https://www.postgresql.org/docs/release/17.6/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1756036800">- switch library to pg 18</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1756987200">- Sync spec file with version 18.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Update to 17.7:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/17.7/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 17.8:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/17.8/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 17.9 to fix two regressions in 17.8:
  * https://www.postgresql.org/docs/release/17.9/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
</package>
<package pkgid="d3655eb9e9239d4e096e8efe0c7da93edd3d4a9b83b9bebbd3039270e28352acfe43746a03d9be2b08431b97ef48a893c70db296ca2ab872303593e03925cbcb" name="postgresql17-pglogical" arch="aarch64">
  <version epoch="0" ver="2.4.6" rel="5.29"/>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1639569600">- update to 2.4.1
  - Fix "snapshot still active" warnings and snapshot handling with
    domains. Problems introduced in version 2.4.0.
  - Flush error state when having failed to drop remote replication
    slot</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1666440000">- update to 2.4.2
  - Add PG 15 support</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1683806400">- Stop supporting postgresql10</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1685534400">- update to 2.4.3
  - Apply data filtering on the correct tuple during initial
    synchronization.
  - Restore the correct memory context while decoding a change.
  - Drop database never completes in PostgreSQL 15.
  - Don't replicate TRUNCATE as global message.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1696420800">- update to 2.4.4
  - add support for pg16</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1725883200">- disable pg11 builds as we will remove the EOL package soon</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1727179200">- update to 2.4.5
  - add support for pg17
  - Fix index usage for conflict resolution.
  - Maintain indexes when updating pglogical.sequence_state.
  - Fix build on PostgreSQL 9.4.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1754654400">- remove pg12 support</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755950400">- update to 2.4.6
  - Add support for PostgreSQL 18.
  - Fix additional deadlock during DROP DATABASE.
  - Fix incorrect row_filter processing after cache invalidation.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755950401">- enable pg18</changelog>
</package>
<package pkgid="0682de051fb1cbac9b386846679978b33b233bf1b5e66b1f6ab883c83892e77425718849447d084e88eb9ef0b45bd2327a378b690cc6178395fdbf844db9df89" name="postgresql17-pglogical" arch="ppc64le">
  <version epoch="0" ver="2.4.6" rel="5.29"/>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1639569600">- update to 2.4.1
  - Fix "snapshot still active" warnings and snapshot handling with
    domains. Problems introduced in version 2.4.0.
  - Flush error state when having failed to drop remote replication
    slot</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1666440000">- update to 2.4.2
  - Add PG 15 support</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1683806400">- Stop supporting postgresql10</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1685534400">- update to 2.4.3
  - Apply data filtering on the correct tuple during initial
    synchronization.
  - Restore the correct memory context while decoding a change.
  - Drop database never completes in PostgreSQL 15.
  - Don't replicate TRUNCATE as global message.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1696420800">- update to 2.4.4
  - add support for pg16</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1725883200">- disable pg11 builds as we will remove the EOL package soon</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1727179200">- update to 2.4.5
  - add support for pg17
  - Fix index usage for conflict resolution.
  - Maintain indexes when updating pglogical.sequence_state.
  - Fix build on PostgreSQL 9.4.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1754654400">- remove pg12 support</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755950400">- update to 2.4.6
  - Add support for PostgreSQL 18.
  - Fix additional deadlock during DROP DATABASE.
  - Fix incorrect row_filter processing after cache invalidation.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755950401">- enable pg18</changelog>
</package>
<package pkgid="df38b0e3f5b397a24f5fd04047108849e3752f63e52cddc535d86d04977550ccafcaf9dce8530953e2183d10135b36a31ab2f8f89d8cf9a35902d94e52310e30" name="postgresql17-pglogical" arch="s390x">
  <version epoch="0" ver="2.4.6" rel="5.29"/>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1639569600">- update to 2.4.1
  - Fix "snapshot still active" warnings and snapshot handling with
    domains. Problems introduced in version 2.4.0.
  - Flush error state when having failed to drop remote replication
    slot</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1666440000">- update to 2.4.2
  - Add PG 15 support</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1683806400">- Stop supporting postgresql10</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1685534400">- update to 2.4.3
  - Apply data filtering on the correct tuple during initial
    synchronization.
  - Restore the correct memory context while decoding a change.
  - Drop database never completes in PostgreSQL 15.
  - Don't replicate TRUNCATE as global message.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1696420800">- update to 2.4.4
  - add support for pg16</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1725883200">- disable pg11 builds as we will remove the EOL package soon</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1727179200">- update to 2.4.5
  - add support for pg17
  - Fix index usage for conflict resolution.
  - Maintain indexes when updating pglogical.sequence_state.
  - Fix build on PostgreSQL 9.4.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1754654400">- remove pg12 support</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755950400">- update to 2.4.6
  - Add support for PostgreSQL 18.
  - Fix additional deadlock during DROP DATABASE.
  - Fix incorrect row_filter processing after cache invalidation.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755950401">- enable pg18</changelog>
</package>
<package pkgid="a0a2cc274c3858921d4dbc10897c22a3500b9b6b35fadef1eaf62122f8f61c683612ef0b915b6d230b832d3afdc44e8c905e6130b30ad562473b2c1f7ef0c2d1" name="postgresql17-pglogical" arch="src">
  <version epoch="0" ver="2.4.6" rel="5.29"/>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1540641600">- limit to 9.6 and higher</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1571745600">- update to 2.2.2
  - Support for replication of tables which have covering unique
    indexes.
  - Improve failover slot detection.
  - Improve tests of column filtering and row filtering
  - Fix error messages to conform better to PostgreSQL standard.
  - Fix crash in DDL replication when parallelization is used when
    executing the DDL on subscriber.
- split out the llvmjit files into a subpackage</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1588680000">- update to 2.3.0
  The pglogical 2.3.0 is a minor update to the pglogical 2 which
  includes support for PostgreSQL 12 and several new minor features
  and bug fixes.
  - Support for PostgreSQL 12
  - Allow replicating tables and sequences to different names on
    the target
  - Add option to only synchronize the structure of replicated
    relations
  - Add a new option to force a text transfer format for a
    subscription
  - Allow tables to be resynchronized in state SYNC_STATUS_SYNCDONE
  - Fix pglogical_wait_for_sync_complete with unknown table
  - Use write lsn rather than insert lsn by default in
    wait_slot_confirm_lsn</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1604232000">- update to 2.3.3
  - This release adds support for PostgreSQL 13.
  - fixes the build against the latest PostgreSQL minor releases
  - pglogical 2.3.1 contains several fixes that prevented users
    from upgrading to version 2.3.0.  The features "Allow
    replicating tables and sequences to different names on the
    target" and "Add option to only synchronize the structure of
    replicated relations" from pglogical 2.3.0 have been removed in
    this release for the time being and will be added again in a
    later release.
- enable pg13</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1622116800">- CVE-2021-3515, bsc#1186121, pglogical-CVE-2021-3515.patch:
  Shell injection by pglogical users with CREATEDB access</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1622548800">- update to 2.3.4: (bsc#1186121)
  - Fix pg_dump/pg_restore execution (CVE-2021-3515)
    Correctly escape the connection string for both pg_dump and
    pg_restore so that exotic database and user names are handled
    correctly.  Reported by Pedro Gallegos
  - Assign collation to the index scan key
    When doing lookups for INSERT/UPDATE/DELETE, either to find
    conflicts or key for the operation to be applied, we should use
    correct collation.
    This fixes issues with PostgreSQL 12+ primary key lookups when
    primary key is on column using one of the textual types.
  - Execute pg_ctl with appropriate verbosity in
    pglogical_create_subscriber
    When -v is passed to pglogical_create_subscriber, it will now
    call pg_ctl without silent mode. This is useful for
    troubleshooting.
  - Clarify documentation regarding REPLICA IDENTITY requirements
    and support
- drop pglogical-CVE-2021-3515.patch: included in update
- drop do-not-link-unneeded-libs.patch: no longer applicable</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1629115200">- update to 2.4.0
  - Add preliminary support for PostgreSQL 14 (beta)
  - Fix pglogical_show_subscription_table to return row rather than
    set of rows
  - Fix snapshot handling in output plugin and apply worker
  - Fix command quoting on Windows so that it actually works
  - Seems like the API used before has 1024 limit on command line
    length
  - Make sure that the schema syncing process can be interrupted on
    Windows
  - Fix compilation issues with pglogical_create_subscriber on
    Windows
  - Fix double closing of relation when a BEFORE ROW DELETE trigger
    returns NULL in the apply worker
  - Fix multi-insert crash in the SPI apply worker
  - Fix multi-insert doing insert of last tuple multiple times in
    apply worker
  - Make sure debug_query_string is always set Newer versions of
    PostgreSQL require that debug_query_string is always set.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1636891200">- port to postgresql macros</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1638273600">- switch to %{pg_name}-llvmjit-devel</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1638446400">- fix postgresql_has_llvm usage</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1639569600">- update to 2.4.1
  - Fix "snapshot still active" warnings and snapshot handling with
    domains. Problems introduced in version 2.4.0.
  - Flush error state when having failed to drop remote replication
    slot</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1666440000">- update to 2.4.2
  - Add PG 15 support</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1683806400">- Stop supporting postgresql10</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1685534400">- update to 2.4.3
  - Apply data filtering on the correct tuple during initial
    synchronization.
  - Restore the correct memory context while decoding a change.
  - Drop database never completes in PostgreSQL 15.
  - Don't replicate TRUNCATE as global message.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1696420800">- update to 2.4.4
  - add support for pg16</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1725883200">- disable pg11 builds as we will remove the EOL package soon</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1727179200">- update to 2.4.5
  - add support for pg17
  - Fix index usage for conflict resolution.
  - Maintain indexes when updating pglogical.sequence_state.
  - Fix build on PostgreSQL 9.4.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1754654400">- remove pg12 support</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755950400">- update to 2.4.6
  - Add support for PostgreSQL 18.
  - Fix additional deadlock during DROP DATABASE.
  - Fix incorrect row_filter processing after cache invalidation.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755950401">- enable pg18</changelog>
</package>
<package pkgid="832609d8ad0fda5cd67c52c103a028025ca8a02e390dba7550b832a69fc927fc6d626f54b1f4845c253e534bc8b934cdf2d431c65368566231d299c883497bf2" name="postgresql17-pglogical" arch="src">
  <version epoch="0" ver="2.4.7" rel="4.2"/>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1588680000">- update to 2.3.0
  The pglogical 2.3.0 is a minor update to the pglogical 2 which
  includes support for PostgreSQL 12 and several new minor features
  and bug fixes.
  - Support for PostgreSQL 12
  - Allow replicating tables and sequences to different names on
    the target
  - Add option to only synchronize the structure of replicated
    relations
  - Add a new option to force a text transfer format for a
    subscription
  - Allow tables to be resynchronized in state SYNC_STATUS_SYNCDONE
  - Fix pglogical_wait_for_sync_complete with unknown table
  - Use write lsn rather than insert lsn by default in
    wait_slot_confirm_lsn</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1604232000">- update to 2.3.3
  - This release adds support for PostgreSQL 13.
  - fixes the build against the latest PostgreSQL minor releases
  - pglogical 2.3.1 contains several fixes that prevented users
    from upgrading to version 2.3.0.  The features "Allow
    replicating tables and sequences to different names on the
    target" and "Add option to only synchronize the structure of
    replicated relations" from pglogical 2.3.0 have been removed in
    this release for the time being and will be added again in a
    later release.
- enable pg13</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1622116800">- CVE-2021-3515, bsc#1186121, pglogical-CVE-2021-3515.patch:
  Shell injection by pglogical users with CREATEDB access</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1622548800">- update to 2.3.4: (bsc#1186121)
  - Fix pg_dump/pg_restore execution (CVE-2021-3515)
    Correctly escape the connection string for both pg_dump and
    pg_restore so that exotic database and user names are handled
    correctly.  Reported by Pedro Gallegos
  - Assign collation to the index scan key
    When doing lookups for INSERT/UPDATE/DELETE, either to find
    conflicts or key for the operation to be applied, we should use
    correct collation.
    This fixes issues with PostgreSQL 12+ primary key lookups when
    primary key is on column using one of the textual types.
  - Execute pg_ctl with appropriate verbosity in
    pglogical_create_subscriber
    When -v is passed to pglogical_create_subscriber, it will now
    call pg_ctl without silent mode. This is useful for
    troubleshooting.
  - Clarify documentation regarding REPLICA IDENTITY requirements
    and support
- drop pglogical-CVE-2021-3515.patch: included in update
- drop do-not-link-unneeded-libs.patch: no longer applicable</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1629115200">- update to 2.4.0
  - Add preliminary support for PostgreSQL 14 (beta)
  - Fix pglogical_show_subscription_table to return row rather than
    set of rows
  - Fix snapshot handling in output plugin and apply worker
  - Fix command quoting on Windows so that it actually works
  - Seems like the API used before has 1024 limit on command line
    length
  - Make sure that the schema syncing process can be interrupted on
    Windows
  - Fix compilation issues with pglogical_create_subscriber on
    Windows
  - Fix double closing of relation when a BEFORE ROW DELETE trigger
    returns NULL in the apply worker
  - Fix multi-insert crash in the SPI apply worker
  - Fix multi-insert doing insert of last tuple multiple times in
    apply worker
  - Make sure debug_query_string is always set Newer versions of
    PostgreSQL require that debug_query_string is always set.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1636891200">- port to postgresql macros</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1638273600">- switch to %{pg_name}-llvmjit-devel</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1638446400">- fix postgresql_has_llvm usage</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1639569600">- update to 2.4.1
  - Fix "snapshot still active" warnings and snapshot handling with
    domains. Problems introduced in version 2.4.0.
  - Flush error state when having failed to drop remote replication
    slot</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1666440000">- update to 2.4.2
  - Add PG 15 support</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1683806400">- Stop supporting postgresql10</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1685534400">- update to 2.4.3
  - Apply data filtering on the correct tuple during initial
    synchronization.
  - Restore the correct memory context while decoding a change.
  - Drop database never completes in PostgreSQL 15.
  - Don't replicate TRUNCATE as global message.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1696420800">- update to 2.4.4
  - add support for pg16</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1725883200">- disable pg11 builds as we will remove the EOL package soon</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1727179200">- update to 2.4.5
  - add support for pg17
  - Fix index usage for conflict resolution.
  - Maintain indexes when updating pglogical.sequence_state.
  - Fix build on PostgreSQL 9.4.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1754654400">- remove pg12 support</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755950400">- update to 2.4.6
  - Add support for PostgreSQL 18.
  - Fix additional deadlock during DROP DATABASE.
  - Fix incorrect row_filter processing after cache invalidation.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755950401">- enable pg18</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1778068800">- Disable pg13</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1780315200">- update to 2.4.7
  - Add support for PostgreSQL 19.
  - Fix sync worker hang with idle source database.
  - Fix some memory leaks.</changelog>
</package>
<package pkgid="2df7ea58ec284a658d0a969cf07ec6879242b4e6f52cf9d3dfcdc023a3ccbb6e926ebebfd0152b8f671b952a82ce27d6e79c551fb3e79389f33b0864682df56e" name="postgresql17-pglogical" arch="x86_64">
  <version epoch="0" ver="2.4.7" rel="4.2"/>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1683806400">- Stop supporting postgresql10</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1685534400">- update to 2.4.3
  - Apply data filtering on the correct tuple during initial
    synchronization.
  - Restore the correct memory context while decoding a change.
  - Drop database never completes in PostgreSQL 15.
  - Don't replicate TRUNCATE as global message.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1696420800">- update to 2.4.4
  - add support for pg16</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1725883200">- disable pg11 builds as we will remove the EOL package soon</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1727179200">- update to 2.4.5
  - add support for pg17
  - Fix index usage for conflict resolution.
  - Maintain indexes when updating pglogical.sequence_state.
  - Fix build on PostgreSQL 9.4.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1754654400">- remove pg12 support</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755950400">- update to 2.4.6
  - Add support for PostgreSQL 18.
  - Fix additional deadlock during DROP DATABASE.
  - Fix incorrect row_filter processing after cache invalidation.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755950401">- enable pg18</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1778068800">- Disable pg13</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1780315200">- update to 2.4.7
  - Add support for PostgreSQL 19.
  - Fix sync worker hang with idle source database.
  - Fix some memory leaks.</changelog>
</package>
<package pkgid="b65f8e0bb19c093dccebe36ce479c0c13bc7460d1e149225cf76f6ac0f4b1547becad43e845a926ab81d872ad6d27a4880d109e7c3e020507fc1215e5f237c1c" name="postgresql17-plperl" arch="x86_64">
  <version epoch="0" ver="17.10" rel="69.2"/>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1731499200">- Upgrade to 17.1:
  * CVE-2024-10976, bsc#1233323: Ensure cached plans are marked as
    dependent on the calling role when RLS applies to a
    non-top-level table reference.
  * CVE-2024-10977, bsc#1233325: Make libpq discard error messages
    received during SSL or GSS protocol negotiation.
  * CVE-2024-10978, bsc#1233326: Fix unintended interactions
    between SET SESSION AUTHORIZATION and SET ROLE
  * CVE-2024-10979, bsc#1233327: Prevent trusted PL/Perl code from
    changing environment variables.
  * obsoletes postgresql17-jsonb_jsonpath.patch
  * https://www.postgresql.org/about/news/p-2955/
  * https://www.postgresql.org/docs/release/17.1/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1732017600">- Upgrade to 17.2:
  * Repair ABI break for extensions that work with struct
    ResultRelInfo.
  * Restore functionality of ALTER {ROLE|DATABASE} SET role.
  * Fix cases where a logical replication slot's restart_lsn could
    go backwards.
  * Avoid deleting still-needed WAL files during pg_rewind.
  * Fix race conditions associated with dropping shared statistics
    entries.
  * Count index scans in contrib/bloom indexes in the statistics
    views, such as the pg_stat_user_indexes.idx_scan counter.
  * Fix crash when checking to see if an index's opclass options
    have changed.
  * Avoid assertion failure caused by disconnected NFA sub-graphs
    in regular expression parsing.
  * https://www.postgresql.org/about/news/p-2965/
  * https://www.postgresql.org/docs/release/17.2/</changelog>
  <changelog author="JS &lt;obs.coke518@passinbox.com&gt;" date="1735214400">- Disable LLVM JIT on loongarch64</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="JS &lt;obs.coke518@passinbox.com&gt;" date="1738152000">- Apply postgresql-tzdata2025a.patch regardless of
  whether LLVM JIT is enabled</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 17.3:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/17.3/
  * https://www.postgresql.org/about/news/-3015/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 17.4:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/17.4/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 17.5:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/17.5/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to Fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Update to 17.6
  * https://www.postgresql.org/about/news/postgresql-176-1610-1514-1419-1322-and-18-beta-3-released-3118/
  * https://www.postgresql.org/docs/release/17.6/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1756036800">- switch library to pg 18</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1756987200">- Sync spec file with version 18.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Update to 17.7:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/17.7/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 17.8:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/17.8/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 17.9 to fix two regressions in 17.8:
  * https://www.postgresql.org/docs/release/17.9/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1774872000">- Get rid of update-alternatives for openSUSE/SLE 16.0 and newer
  to support immutable systems and transactional updates.
  (jsc#PED-14825, bsc#1245875)</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1777550400">- bsc#1263804: After dropping update-alternatives we have to
  package /usr/bin/pg_config as an actual symlink, not %ghost.
- Fix spelling of build conditionals.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1778673600">- Update to version 17.10:
  * bsc#1265172, CVE-2026-6472: ensure the user has CREATE
    privilege on the schema specified
  * bsc#1265173, CVE-2026-6473: integer overflows in
    memory-allocation calculations
  * bsc#1265174, CVE-2026-6474: Guard against malicious time zone
    names
  * bsc#1265175, CVE-2026-6475: Prevent path traversal in
    pg_basebackup and pg_rewind
  * bsc#1265176, CVE-2026-6476: Properly quote subscription names
    in pg_createsubscriber
  * bsc#1265177, CVE-2026-6477: Mark PQfn() as unsafe, and avoid
    using it within libpq
  * bsc#1265178, CVE-2026-6478: Use timing-safe string comparisons
    in authentication code
  * bsc#1265179, CVE-2026-6479: Prevent unbounded recursion while
    processing startup packets
  * bsc#1265181, CVE-2026-6637: Prevent SQL injection and buffer
    overruns in contrib/spi
  * bsc#1265182, CVE-2026-6638: Properly quote object names in
    logical replication origin checks
  * https://www.postgresql.org/docs/release/17.10/</changelog>
</package>
<package pkgid="6cae267ef69705c99537eb29353151719dca514d92556fa66b097e9d373574732ce2cff7b3371037cb866b759e6f850b12d99d54c616fd412b2629b3f0cbb0e8" name="postgresql17-plperl" arch="s390x">
  <version epoch="0" ver="17.9" rel="53.1"/>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1727352000">- Upgrade to 17.0:
  * New memory management system for VACUUM, which reduces memory
    consumption and can improve overall vacuuming performance.
  * New SQL/JSON capabilities, including constructors, identity
    functions, and the JSON_TABLE() function, which converts JSON
    data into a table representation.
  * Various query performance improvements, including for
    sequential reads using streaming I/O, write throughput under
    high concurrency, and searches over multiple values in a btree
    index.
  * Logical replication enhancements, including:
    + Failover control
    + pg_createsubscriber, a utility that creates logical replicas
    from physical standbys
    + pg_upgrade now preserves replication slots on both publishers
    and subscribers
  * New client-side connection option, sslnegotiation=direct, that
    performs a direct TLS handshake to avoid a round-trip
    negotiation.
  * pg_basebackup now supports incremental backup.
  * COPY adds a new option, ON_ERROR ignore, that allows a copy
    operation to continue in the event of an error.
  * https://www.postgresql.org/about/news/p-2936/
  * https://www.postgresql.org/docs/17/release-17.html</changelog>
  <changelog author="Fabian Vogt &lt;fvogt@suse.com&gt;" date="1728302400">- Use cmake(LLVM) &lt; instead of &lt;= to also allow building against
  LLVM 18.1 and newer 18.x versions</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1730721600">- Add postgresql17-jsonb_jsonpath.patch as a temporary build fix.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1731499200">- Upgrade to 17.1:
  * CVE-2024-10976, bsc#1233323: Ensure cached plans are marked as
    dependent on the calling role when RLS applies to a
    non-top-level table reference.
  * CVE-2024-10977, bsc#1233325: Make libpq discard error messages
    received during SSL or GSS protocol negotiation.
  * CVE-2024-10978, bsc#1233326: Fix unintended interactions
    between SET SESSION AUTHORIZATION and SET ROLE
  * CVE-2024-10979, bsc#1233327: Prevent trusted PL/Perl code from
    changing environment variables.
  * obsoletes postgresql17-jsonb_jsonpath.patch
  * https://www.postgresql.org/about/news/p-2955/
  * https://www.postgresql.org/docs/release/17.1/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1732017600">- Upgrade to 17.2:
  * Repair ABI break for extensions that work with struct
    ResultRelInfo.
  * Restore functionality of ALTER {ROLE|DATABASE} SET role.
  * Fix cases where a logical replication slot's restart_lsn could
    go backwards.
  * Avoid deleting still-needed WAL files during pg_rewind.
  * Fix race conditions associated with dropping shared statistics
    entries.
  * Count index scans in contrib/bloom indexes in the statistics
    views, such as the pg_stat_user_indexes.idx_scan counter.
  * Fix crash when checking to see if an index's opclass options
    have changed.
  * Avoid assertion failure caused by disconnected NFA sub-graphs
    in regular expression parsing.
  * https://www.postgresql.org/about/news/p-2965/
  * https://www.postgresql.org/docs/release/17.2/</changelog>
  <changelog author="JS &lt;obs.coke518@passinbox.com&gt;" date="1735214400">- Disable LLVM JIT on loongarch64</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="JS &lt;obs.coke518@passinbox.com&gt;" date="1738152000">- Apply postgresql-tzdata2025a.patch regardless of
  whether LLVM JIT is enabled</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 17.3:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/17.3/
  * https://www.postgresql.org/about/news/-3015/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 17.4:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/17.4/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 17.5:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/17.5/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to Fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Update to 17.6
  * https://www.postgresql.org/about/news/postgresql-176-1610-1514-1419-1322-and-18-beta-3-released-3118/
  * https://www.postgresql.org/docs/release/17.6/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1756036800">- switch library to pg 18</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1756987200">- Sync spec file with version 18.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Update to 17.7:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/17.7/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 17.8:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/17.8/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 17.9 to fix two regressions in 17.8:
  * https://www.postgresql.org/docs/release/17.9/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
</package>
<package pkgid="b166bfc6dded1cbb302899e22264bac16ead5e4661f1fdf8c7147dd60799c0c61abfd1546506cb5da967b1dcd5d78ab924b2cb310534ac769fe3e0032a2388b9" name="postgresql17-plperl" arch="aarch64">
  <version epoch="0" ver="17.9" rel="54.2"/>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1727352000">- Upgrade to 17.0:
  * New memory management system for VACUUM, which reduces memory
    consumption and can improve overall vacuuming performance.
  * New SQL/JSON capabilities, including constructors, identity
    functions, and the JSON_TABLE() function, which converts JSON
    data into a table representation.
  * Various query performance improvements, including for
    sequential reads using streaming I/O, write throughput under
    high concurrency, and searches over multiple values in a btree
    index.
  * Logical replication enhancements, including:
    + Failover control
    + pg_createsubscriber, a utility that creates logical replicas
    from physical standbys
    + pg_upgrade now preserves replication slots on both publishers
    and subscribers
  * New client-side connection option, sslnegotiation=direct, that
    performs a direct TLS handshake to avoid a round-trip
    negotiation.
  * pg_basebackup now supports incremental backup.
  * COPY adds a new option, ON_ERROR ignore, that allows a copy
    operation to continue in the event of an error.
  * https://www.postgresql.org/about/news/p-2936/
  * https://www.postgresql.org/docs/17/release-17.html</changelog>
  <changelog author="Fabian Vogt &lt;fvogt@suse.com&gt;" date="1728302400">- Use cmake(LLVM) &lt; instead of &lt;= to also allow building against
  LLVM 18.1 and newer 18.x versions</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1730721600">- Add postgresql17-jsonb_jsonpath.patch as a temporary build fix.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1731499200">- Upgrade to 17.1:
  * CVE-2024-10976, bsc#1233323: Ensure cached plans are marked as
    dependent on the calling role when RLS applies to a
    non-top-level table reference.
  * CVE-2024-10977, bsc#1233325: Make libpq discard error messages
    received during SSL or GSS protocol negotiation.
  * CVE-2024-10978, bsc#1233326: Fix unintended interactions
    between SET SESSION AUTHORIZATION and SET ROLE
  * CVE-2024-10979, bsc#1233327: Prevent trusted PL/Perl code from
    changing environment variables.
  * obsoletes postgresql17-jsonb_jsonpath.patch
  * https://www.postgresql.org/about/news/p-2955/
  * https://www.postgresql.org/docs/release/17.1/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1732017600">- Upgrade to 17.2:
  * Repair ABI break for extensions that work with struct
    ResultRelInfo.
  * Restore functionality of ALTER {ROLE|DATABASE} SET role.
  * Fix cases where a logical replication slot's restart_lsn could
    go backwards.
  * Avoid deleting still-needed WAL files during pg_rewind.
  * Fix race conditions associated with dropping shared statistics
    entries.
  * Count index scans in contrib/bloom indexes in the statistics
    views, such as the pg_stat_user_indexes.idx_scan counter.
  * Fix crash when checking to see if an index's opclass options
    have changed.
  * Avoid assertion failure caused by disconnected NFA sub-graphs
    in regular expression parsing.
  * https://www.postgresql.org/about/news/p-2965/
  * https://www.postgresql.org/docs/release/17.2/</changelog>
  <changelog author="JS &lt;obs.coke518@passinbox.com&gt;" date="1735214400">- Disable LLVM JIT on loongarch64</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="JS &lt;obs.coke518@passinbox.com&gt;" date="1738152000">- Apply postgresql-tzdata2025a.patch regardless of
  whether LLVM JIT is enabled</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 17.3:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/17.3/
  * https://www.postgresql.org/about/news/-3015/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 17.4:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/17.4/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 17.5:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/17.5/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to Fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Update to 17.6
  * https://www.postgresql.org/about/news/postgresql-176-1610-1514-1419-1322-and-18-beta-3-released-3118/
  * https://www.postgresql.org/docs/release/17.6/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1756036800">- switch library to pg 18</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1756987200">- Sync spec file with version 18.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Update to 17.7:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/17.7/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 17.8:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/17.8/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 17.9 to fix two regressions in 17.8:
  * https://www.postgresql.org/docs/release/17.9/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
</package>
<package pkgid="6f76458e90beb98009421707908955951a1883f386931040c5f917eb39e32b0aca9908fc7ca2fe61f96b02e3d266426bcc463cc2a656cb5cd41813631db187cc" name="postgresql17-plperl" arch="ppc64le">
  <version epoch="0" ver="17.9" rel="55.1"/>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1727352000">- Upgrade to 17.0:
  * New memory management system for VACUUM, which reduces memory
    consumption and can improve overall vacuuming performance.
  * New SQL/JSON capabilities, including constructors, identity
    functions, and the JSON_TABLE() function, which converts JSON
    data into a table representation.
  * Various query performance improvements, including for
    sequential reads using streaming I/O, write throughput under
    high concurrency, and searches over multiple values in a btree
    index.
  * Logical replication enhancements, including:
    + Failover control
    + pg_createsubscriber, a utility that creates logical replicas
    from physical standbys
    + pg_upgrade now preserves replication slots on both publishers
    and subscribers
  * New client-side connection option, sslnegotiation=direct, that
    performs a direct TLS handshake to avoid a round-trip
    negotiation.
  * pg_basebackup now supports incremental backup.
  * COPY adds a new option, ON_ERROR ignore, that allows a copy
    operation to continue in the event of an error.
  * https://www.postgresql.org/about/news/p-2936/
  * https://www.postgresql.org/docs/17/release-17.html</changelog>
  <changelog author="Fabian Vogt &lt;fvogt@suse.com&gt;" date="1728302400">- Use cmake(LLVM) &lt; instead of &lt;= to also allow building against
  LLVM 18.1 and newer 18.x versions</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1730721600">- Add postgresql17-jsonb_jsonpath.patch as a temporary build fix.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1731499200">- Upgrade to 17.1:
  * CVE-2024-10976, bsc#1233323: Ensure cached plans are marked as
    dependent on the calling role when RLS applies to a
    non-top-level table reference.
  * CVE-2024-10977, bsc#1233325: Make libpq discard error messages
    received during SSL or GSS protocol negotiation.
  * CVE-2024-10978, bsc#1233326: Fix unintended interactions
    between SET SESSION AUTHORIZATION and SET ROLE
  * CVE-2024-10979, bsc#1233327: Prevent trusted PL/Perl code from
    changing environment variables.
  * obsoletes postgresql17-jsonb_jsonpath.patch
  * https://www.postgresql.org/about/news/p-2955/
  * https://www.postgresql.org/docs/release/17.1/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1732017600">- Upgrade to 17.2:
  * Repair ABI break for extensions that work with struct
    ResultRelInfo.
  * Restore functionality of ALTER {ROLE|DATABASE} SET role.
  * Fix cases where a logical replication slot's restart_lsn could
    go backwards.
  * Avoid deleting still-needed WAL files during pg_rewind.
  * Fix race conditions associated with dropping shared statistics
    entries.
  * Count index scans in contrib/bloom indexes in the statistics
    views, such as the pg_stat_user_indexes.idx_scan counter.
  * Fix crash when checking to see if an index's opclass options
    have changed.
  * Avoid assertion failure caused by disconnected NFA sub-graphs
    in regular expression parsing.
  * https://www.postgresql.org/about/news/p-2965/
  * https://www.postgresql.org/docs/release/17.2/</changelog>
  <changelog author="JS &lt;obs.coke518@passinbox.com&gt;" date="1735214400">- Disable LLVM JIT on loongarch64</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="JS &lt;obs.coke518@passinbox.com&gt;" date="1738152000">- Apply postgresql-tzdata2025a.patch regardless of
  whether LLVM JIT is enabled</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 17.3:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/17.3/
  * https://www.postgresql.org/about/news/-3015/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 17.4:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/17.4/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 17.5:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/17.5/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to Fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Update to 17.6
  * https://www.postgresql.org/about/news/postgresql-176-1610-1514-1419-1322-and-18-beta-3-released-3118/
  * https://www.postgresql.org/docs/release/17.6/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1756036800">- switch library to pg 18</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1756987200">- Sync spec file with version 18.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Update to 17.7:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/17.7/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 17.8:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/17.8/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 17.9 to fix two regressions in 17.8:
  * https://www.postgresql.org/docs/release/17.9/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
</package>
<package pkgid="fa7d5357f04ca5ec095672f13ef3c77afe7cca366402aa205e6216ac7f9e7a4974914def27d5a57f276d8bb7c8b936497b2431ab15a7cd6f8bb9aee64840404e" name="postgresql17-plpython" arch="x86_64">
  <version epoch="0" ver="17.10" rel="69.2"/>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1731499200">- Upgrade to 17.1:
  * CVE-2024-10976, bsc#1233323: Ensure cached plans are marked as
    dependent on the calling role when RLS applies to a
    non-top-level table reference.
  * CVE-2024-10977, bsc#1233325: Make libpq discard error messages
    received during SSL or GSS protocol negotiation.
  * CVE-2024-10978, bsc#1233326: Fix unintended interactions
    between SET SESSION AUTHORIZATION and SET ROLE
  * CVE-2024-10979, bsc#1233327: Prevent trusted PL/Perl code from
    changing environment variables.
  * obsoletes postgresql17-jsonb_jsonpath.patch
  * https://www.postgresql.org/about/news/p-2955/
  * https://www.postgresql.org/docs/release/17.1/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1732017600">- Upgrade to 17.2:
  * Repair ABI break for extensions that work with struct
    ResultRelInfo.
  * Restore functionality of ALTER {ROLE|DATABASE} SET role.
  * Fix cases where a logical replication slot's restart_lsn could
    go backwards.
  * Avoid deleting still-needed WAL files during pg_rewind.
  * Fix race conditions associated with dropping shared statistics
    entries.
  * Count index scans in contrib/bloom indexes in the statistics
    views, such as the pg_stat_user_indexes.idx_scan counter.
  * Fix crash when checking to see if an index's opclass options
    have changed.
  * Avoid assertion failure caused by disconnected NFA sub-graphs
    in regular expression parsing.
  * https://www.postgresql.org/about/news/p-2965/
  * https://www.postgresql.org/docs/release/17.2/</changelog>
  <changelog author="JS &lt;obs.coke518@passinbox.com&gt;" date="1735214400">- Disable LLVM JIT on loongarch64</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="JS &lt;obs.coke518@passinbox.com&gt;" date="1738152000">- Apply postgresql-tzdata2025a.patch regardless of
  whether LLVM JIT is enabled</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 17.3:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/17.3/
  * https://www.postgresql.org/about/news/-3015/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 17.4:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/17.4/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 17.5:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/17.5/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to Fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Update to 17.6
  * https://www.postgresql.org/about/news/postgresql-176-1610-1514-1419-1322-and-18-beta-3-released-3118/
  * https://www.postgresql.org/docs/release/17.6/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1756036800">- switch library to pg 18</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1756987200">- Sync spec file with version 18.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Update to 17.7:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/17.7/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 17.8:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/17.8/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 17.9 to fix two regressions in 17.8:
  * https://www.postgresql.org/docs/release/17.9/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1774872000">- Get rid of update-alternatives for openSUSE/SLE 16.0 and newer
  to support immutable systems and transactional updates.
  (jsc#PED-14825, bsc#1245875)</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1777550400">- bsc#1263804: After dropping update-alternatives we have to
  package /usr/bin/pg_config as an actual symlink, not %ghost.
- Fix spelling of build conditionals.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1778673600">- Update to version 17.10:
  * bsc#1265172, CVE-2026-6472: ensure the user has CREATE
    privilege on the schema specified
  * bsc#1265173, CVE-2026-6473: integer overflows in
    memory-allocation calculations
  * bsc#1265174, CVE-2026-6474: Guard against malicious time zone
    names
  * bsc#1265175, CVE-2026-6475: Prevent path traversal in
    pg_basebackup and pg_rewind
  * bsc#1265176, CVE-2026-6476: Properly quote subscription names
    in pg_createsubscriber
  * bsc#1265177, CVE-2026-6477: Mark PQfn() as unsafe, and avoid
    using it within libpq
  * bsc#1265178, CVE-2026-6478: Use timing-safe string comparisons
    in authentication code
  * bsc#1265179, CVE-2026-6479: Prevent unbounded recursion while
    processing startup packets
  * bsc#1265181, CVE-2026-6637: Prevent SQL injection and buffer
    overruns in contrib/spi
  * bsc#1265182, CVE-2026-6638: Properly quote object names in
    logical replication origin checks
  * https://www.postgresql.org/docs/release/17.10/</changelog>
</package>
<package pkgid="aea2ca4cd9f3986adccf435c3e61293d479d794679300b9b07283c828393191c9225172b6cb2151e95273c514dcf7d8192541887c836ad05e579772a19b59f32" name="postgresql17-plpython" arch="s390x">
  <version epoch="0" ver="17.9" rel="53.1"/>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1727352000">- Upgrade to 17.0:
  * New memory management system for VACUUM, which reduces memory
    consumption and can improve overall vacuuming performance.
  * New SQL/JSON capabilities, including constructors, identity
    functions, and the JSON_TABLE() function, which converts JSON
    data into a table representation.
  * Various query performance improvements, including for
    sequential reads using streaming I/O, write throughput under
    high concurrency, and searches over multiple values in a btree
    index.
  * Logical replication enhancements, including:
    + Failover control
    + pg_createsubscriber, a utility that creates logical replicas
    from physical standbys
    + pg_upgrade now preserves replication slots on both publishers
    and subscribers
  * New client-side connection option, sslnegotiation=direct, that
    performs a direct TLS handshake to avoid a round-trip
    negotiation.
  * pg_basebackup now supports incremental backup.
  * COPY adds a new option, ON_ERROR ignore, that allows a copy
    operation to continue in the event of an error.
  * https://www.postgresql.org/about/news/p-2936/
  * https://www.postgresql.org/docs/17/release-17.html</changelog>
  <changelog author="Fabian Vogt &lt;fvogt@suse.com&gt;" date="1728302400">- Use cmake(LLVM) &lt; instead of &lt;= to also allow building against
  LLVM 18.1 and newer 18.x versions</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1730721600">- Add postgresql17-jsonb_jsonpath.patch as a temporary build fix.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1731499200">- Upgrade to 17.1:
  * CVE-2024-10976, bsc#1233323: Ensure cached plans are marked as
    dependent on the calling role when RLS applies to a
    non-top-level table reference.
  * CVE-2024-10977, bsc#1233325: Make libpq discard error messages
    received during SSL or GSS protocol negotiation.
  * CVE-2024-10978, bsc#1233326: Fix unintended interactions
    between SET SESSION AUTHORIZATION and SET ROLE
  * CVE-2024-10979, bsc#1233327: Prevent trusted PL/Perl code from
    changing environment variables.
  * obsoletes postgresql17-jsonb_jsonpath.patch
  * https://www.postgresql.org/about/news/p-2955/
  * https://www.postgresql.org/docs/release/17.1/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1732017600">- Upgrade to 17.2:
  * Repair ABI break for extensions that work with struct
    ResultRelInfo.
  * Restore functionality of ALTER {ROLE|DATABASE} SET role.
  * Fix cases where a logical replication slot's restart_lsn could
    go backwards.
  * Avoid deleting still-needed WAL files during pg_rewind.
  * Fix race conditions associated with dropping shared statistics
    entries.
  * Count index scans in contrib/bloom indexes in the statistics
    views, such as the pg_stat_user_indexes.idx_scan counter.
  * Fix crash when checking to see if an index's opclass options
    have changed.
  * Avoid assertion failure caused by disconnected NFA sub-graphs
    in regular expression parsing.
  * https://www.postgresql.org/about/news/p-2965/
  * https://www.postgresql.org/docs/release/17.2/</changelog>
  <changelog author="JS &lt;obs.coke518@passinbox.com&gt;" date="1735214400">- Disable LLVM JIT on loongarch64</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="JS &lt;obs.coke518@passinbox.com&gt;" date="1738152000">- Apply postgresql-tzdata2025a.patch regardless of
  whether LLVM JIT is enabled</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 17.3:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/17.3/
  * https://www.postgresql.org/about/news/-3015/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 17.4:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/17.4/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 17.5:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/17.5/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to Fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Update to 17.6
  * https://www.postgresql.org/about/news/postgresql-176-1610-1514-1419-1322-and-18-beta-3-released-3118/
  * https://www.postgresql.org/docs/release/17.6/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1756036800">- switch library to pg 18</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1756987200">- Sync spec file with version 18.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Update to 17.7:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/17.7/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 17.8:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/17.8/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 17.9 to fix two regressions in 17.8:
  * https://www.postgresql.org/docs/release/17.9/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
</package>
<package pkgid="014440294f9cb148449f1f60333638203993373412e1f50cffe6dc5aa99c6479a965a93d65e2b4a6381a5e1af45daa3480343329bde99018541986850e73cfe1" name="postgresql17-plpython" arch="aarch64">
  <version epoch="0" ver="17.9" rel="54.2"/>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1727352000">- Upgrade to 17.0:
  * New memory management system for VACUUM, which reduces memory
    consumption and can improve overall vacuuming performance.
  * New SQL/JSON capabilities, including constructors, identity
    functions, and the JSON_TABLE() function, which converts JSON
    data into a table representation.
  * Various query performance improvements, including for
    sequential reads using streaming I/O, write throughput under
    high concurrency, and searches over multiple values in a btree
    index.
  * Logical replication enhancements, including:
    + Failover control
    + pg_createsubscriber, a utility that creates logical replicas
    from physical standbys
    + pg_upgrade now preserves replication slots on both publishers
    and subscribers
  * New client-side connection option, sslnegotiation=direct, that
    performs a direct TLS handshake to avoid a round-trip
    negotiation.
  * pg_basebackup now supports incremental backup.
  * COPY adds a new option, ON_ERROR ignore, that allows a copy
    operation to continue in the event of an error.
  * https://www.postgresql.org/about/news/p-2936/
  * https://www.postgresql.org/docs/17/release-17.html</changelog>
  <changelog author="Fabian Vogt &lt;fvogt@suse.com&gt;" date="1728302400">- Use cmake(LLVM) &lt; instead of &lt;= to also allow building against
  LLVM 18.1 and newer 18.x versions</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1730721600">- Add postgresql17-jsonb_jsonpath.patch as a temporary build fix.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1731499200">- Upgrade to 17.1:
  * CVE-2024-10976, bsc#1233323: Ensure cached plans are marked as
    dependent on the calling role when RLS applies to a
    non-top-level table reference.
  * CVE-2024-10977, bsc#1233325: Make libpq discard error messages
    received during SSL or GSS protocol negotiation.
  * CVE-2024-10978, bsc#1233326: Fix unintended interactions
    between SET SESSION AUTHORIZATION and SET ROLE
  * CVE-2024-10979, bsc#1233327: Prevent trusted PL/Perl code from
    changing environment variables.
  * obsoletes postgresql17-jsonb_jsonpath.patch
  * https://www.postgresql.org/about/news/p-2955/
  * https://www.postgresql.org/docs/release/17.1/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1732017600">- Upgrade to 17.2:
  * Repair ABI break for extensions that work with struct
    ResultRelInfo.
  * Restore functionality of ALTER {ROLE|DATABASE} SET role.
  * Fix cases where a logical replication slot's restart_lsn could
    go backwards.
  * Avoid deleting still-needed WAL files during pg_rewind.
  * Fix race conditions associated with dropping shared statistics
    entries.
  * Count index scans in contrib/bloom indexes in the statistics
    views, such as the pg_stat_user_indexes.idx_scan counter.
  * Fix crash when checking to see if an index's opclass options
    have changed.
  * Avoid assertion failure caused by disconnected NFA sub-graphs
    in regular expression parsing.
  * https://www.postgresql.org/about/news/p-2965/
  * https://www.postgresql.org/docs/release/17.2/</changelog>
  <changelog author="JS &lt;obs.coke518@passinbox.com&gt;" date="1735214400">- Disable LLVM JIT on loongarch64</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="JS &lt;obs.coke518@passinbox.com&gt;" date="1738152000">- Apply postgresql-tzdata2025a.patch regardless of
  whether LLVM JIT is enabled</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 17.3:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/17.3/
  * https://www.postgresql.org/about/news/-3015/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 17.4:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/17.4/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 17.5:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/17.5/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to Fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Update to 17.6
  * https://www.postgresql.org/about/news/postgresql-176-1610-1514-1419-1322-and-18-beta-3-released-3118/
  * https://www.postgresql.org/docs/release/17.6/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1756036800">- switch library to pg 18</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1756987200">- Sync spec file with version 18.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Update to 17.7:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/17.7/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 17.8:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/17.8/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 17.9 to fix two regressions in 17.8:
  * https://www.postgresql.org/docs/release/17.9/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
</package>
<package pkgid="2bd77a9746d2512657bae3098086db7fb529385f452bb5ccc634114159608594793f3186e6c8178726a7eade76d15aace6c00d8021c1177fbe23bccf9df9ad36" name="postgresql17-plpython" arch="ppc64le">
  <version epoch="0" ver="17.9" rel="55.1"/>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1727352000">- Upgrade to 17.0:
  * New memory management system for VACUUM, which reduces memory
    consumption and can improve overall vacuuming performance.
  * New SQL/JSON capabilities, including constructors, identity
    functions, and the JSON_TABLE() function, which converts JSON
    data into a table representation.
  * Various query performance improvements, including for
    sequential reads using streaming I/O, write throughput under
    high concurrency, and searches over multiple values in a btree
    index.
  * Logical replication enhancements, including:
    + Failover control
    + pg_createsubscriber, a utility that creates logical replicas
    from physical standbys
    + pg_upgrade now preserves replication slots on both publishers
    and subscribers
  * New client-side connection option, sslnegotiation=direct, that
    performs a direct TLS handshake to avoid a round-trip
    negotiation.
  * pg_basebackup now supports incremental backup.
  * COPY adds a new option, ON_ERROR ignore, that allows a copy
    operation to continue in the event of an error.
  * https://www.postgresql.org/about/news/p-2936/
  * https://www.postgresql.org/docs/17/release-17.html</changelog>
  <changelog author="Fabian Vogt &lt;fvogt@suse.com&gt;" date="1728302400">- Use cmake(LLVM) &lt; instead of &lt;= to also allow building against
  LLVM 18.1 and newer 18.x versions</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1730721600">- Add postgresql17-jsonb_jsonpath.patch as a temporary build fix.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1731499200">- Upgrade to 17.1:
  * CVE-2024-10976, bsc#1233323: Ensure cached plans are marked as
    dependent on the calling role when RLS applies to a
    non-top-level table reference.
  * CVE-2024-10977, bsc#1233325: Make libpq discard error messages
    received during SSL or GSS protocol negotiation.
  * CVE-2024-10978, bsc#1233326: Fix unintended interactions
    between SET SESSION AUTHORIZATION and SET ROLE
  * CVE-2024-10979, bsc#1233327: Prevent trusted PL/Perl code from
    changing environment variables.
  * obsoletes postgresql17-jsonb_jsonpath.patch
  * https://www.postgresql.org/about/news/p-2955/
  * https://www.postgresql.org/docs/release/17.1/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1732017600">- Upgrade to 17.2:
  * Repair ABI break for extensions that work with struct
    ResultRelInfo.
  * Restore functionality of ALTER {ROLE|DATABASE} SET role.
  * Fix cases where a logical replication slot's restart_lsn could
    go backwards.
  * Avoid deleting still-needed WAL files during pg_rewind.
  * Fix race conditions associated with dropping shared statistics
    entries.
  * Count index scans in contrib/bloom indexes in the statistics
    views, such as the pg_stat_user_indexes.idx_scan counter.
  * Fix crash when checking to see if an index's opclass options
    have changed.
  * Avoid assertion failure caused by disconnected NFA sub-graphs
    in regular expression parsing.
  * https://www.postgresql.org/about/news/p-2965/
  * https://www.postgresql.org/docs/release/17.2/</changelog>
  <changelog author="JS &lt;obs.coke518@passinbox.com&gt;" date="1735214400">- Disable LLVM JIT on loongarch64</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="JS &lt;obs.coke518@passinbox.com&gt;" date="1738152000">- Apply postgresql-tzdata2025a.patch regardless of
  whether LLVM JIT is enabled</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 17.3:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/17.3/
  * https://www.postgresql.org/about/news/-3015/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 17.4:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/17.4/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 17.5:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/17.5/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to Fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Update to 17.6
  * https://www.postgresql.org/about/news/postgresql-176-1610-1514-1419-1322-and-18-beta-3-released-3118/
  * https://www.postgresql.org/docs/release/17.6/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1756036800">- switch library to pg 18</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1756987200">- Sync spec file with version 18.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Update to 17.7:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/17.7/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 17.8:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/17.8/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 17.9 to fix two regressions in 17.8:
  * https://www.postgresql.org/docs/release/17.9/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
</package>
<package pkgid="219996018775539edecb29a05d1e8062ac233746a1281c3600a505592132476a01e0e3947f6e090e7e67fb4b1a997473a504bbd484f25288a3c1517a44c073b2" name="postgresql17-pltcl" arch="x86_64">
  <version epoch="0" ver="17.10" rel="69.2"/>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1731499200">- Upgrade to 17.1:
  * CVE-2024-10976, bsc#1233323: Ensure cached plans are marked as
    dependent on the calling role when RLS applies to a
    non-top-level table reference.
  * CVE-2024-10977, bsc#1233325: Make libpq discard error messages
    received during SSL or GSS protocol negotiation.
  * CVE-2024-10978, bsc#1233326: Fix unintended interactions
    between SET SESSION AUTHORIZATION and SET ROLE
  * CVE-2024-10979, bsc#1233327: Prevent trusted PL/Perl code from
    changing environment variables.
  * obsoletes postgresql17-jsonb_jsonpath.patch
  * https://www.postgresql.org/about/news/p-2955/
  * https://www.postgresql.org/docs/release/17.1/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1732017600">- Upgrade to 17.2:
  * Repair ABI break for extensions that work with struct
    ResultRelInfo.
  * Restore functionality of ALTER {ROLE|DATABASE} SET role.
  * Fix cases where a logical replication slot's restart_lsn could
    go backwards.
  * Avoid deleting still-needed WAL files during pg_rewind.
  * Fix race conditions associated with dropping shared statistics
    entries.
  * Count index scans in contrib/bloom indexes in the statistics
    views, such as the pg_stat_user_indexes.idx_scan counter.
  * Fix crash when checking to see if an index's opclass options
    have changed.
  * Avoid assertion failure caused by disconnected NFA sub-graphs
    in regular expression parsing.
  * https://www.postgresql.org/about/news/p-2965/
  * https://www.postgresql.org/docs/release/17.2/</changelog>
  <changelog author="JS &lt;obs.coke518@passinbox.com&gt;" date="1735214400">- Disable LLVM JIT on loongarch64</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="JS &lt;obs.coke518@passinbox.com&gt;" date="1738152000">- Apply postgresql-tzdata2025a.patch regardless of
  whether LLVM JIT is enabled</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 17.3:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/17.3/
  * https://www.postgresql.org/about/news/-3015/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 17.4:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/17.4/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 17.5:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/17.5/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to Fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Update to 17.6
  * https://www.postgresql.org/about/news/postgresql-176-1610-1514-1419-1322-and-18-beta-3-released-3118/
  * https://www.postgresql.org/docs/release/17.6/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1756036800">- switch library to pg 18</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1756987200">- Sync spec file with version 18.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Update to 17.7:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/17.7/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 17.8:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/17.8/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 17.9 to fix two regressions in 17.8:
  * https://www.postgresql.org/docs/release/17.9/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1774872000">- Get rid of update-alternatives for openSUSE/SLE 16.0 and newer
  to support immutable systems and transactional updates.
  (jsc#PED-14825, bsc#1245875)</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1777550400">- bsc#1263804: After dropping update-alternatives we have to
  package /usr/bin/pg_config as an actual symlink, not %ghost.
- Fix spelling of build conditionals.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1778673600">- Update to version 17.10:
  * bsc#1265172, CVE-2026-6472: ensure the user has CREATE
    privilege on the schema specified
  * bsc#1265173, CVE-2026-6473: integer overflows in
    memory-allocation calculations
  * bsc#1265174, CVE-2026-6474: Guard against malicious time zone
    names
  * bsc#1265175, CVE-2026-6475: Prevent path traversal in
    pg_basebackup and pg_rewind
  * bsc#1265176, CVE-2026-6476: Properly quote subscription names
    in pg_createsubscriber
  * bsc#1265177, CVE-2026-6477: Mark PQfn() as unsafe, and avoid
    using it within libpq
  * bsc#1265178, CVE-2026-6478: Use timing-safe string comparisons
    in authentication code
  * bsc#1265179, CVE-2026-6479: Prevent unbounded recursion while
    processing startup packets
  * bsc#1265181, CVE-2026-6637: Prevent SQL injection and buffer
    overruns in contrib/spi
  * bsc#1265182, CVE-2026-6638: Properly quote object names in
    logical replication origin checks
  * https://www.postgresql.org/docs/release/17.10/</changelog>
</package>
<package pkgid="d47f68967db20ea1be4e250b282abd5e95a21524127772ceb56a8700a7dd87ae7ab8675a6e2e49651deb69a062283c5430b4c471a343960cfb884aee5247e884" name="postgresql17-pltcl" arch="s390x">
  <version epoch="0" ver="17.9" rel="53.1"/>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1727352000">- Upgrade to 17.0:
  * New memory management system for VACUUM, which reduces memory
    consumption and can improve overall vacuuming performance.
  * New SQL/JSON capabilities, including constructors, identity
    functions, and the JSON_TABLE() function, which converts JSON
    data into a table representation.
  * Various query performance improvements, including for
    sequential reads using streaming I/O, write throughput under
    high concurrency, and searches over multiple values in a btree
    index.
  * Logical replication enhancements, including:
    + Failover control
    + pg_createsubscriber, a utility that creates logical replicas
    from physical standbys
    + pg_upgrade now preserves replication slots on both publishers
    and subscribers
  * New client-side connection option, sslnegotiation=direct, that
    performs a direct TLS handshake to avoid a round-trip
    negotiation.
  * pg_basebackup now supports incremental backup.
  * COPY adds a new option, ON_ERROR ignore, that allows a copy
    operation to continue in the event of an error.
  * https://www.postgresql.org/about/news/p-2936/
  * https://www.postgresql.org/docs/17/release-17.html</changelog>
  <changelog author="Fabian Vogt &lt;fvogt@suse.com&gt;" date="1728302400">- Use cmake(LLVM) &lt; instead of &lt;= to also allow building against
  LLVM 18.1 and newer 18.x versions</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1730721600">- Add postgresql17-jsonb_jsonpath.patch as a temporary build fix.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1731499200">- Upgrade to 17.1:
  * CVE-2024-10976, bsc#1233323: Ensure cached plans are marked as
    dependent on the calling role when RLS applies to a
    non-top-level table reference.
  * CVE-2024-10977, bsc#1233325: Make libpq discard error messages
    received during SSL or GSS protocol negotiation.
  * CVE-2024-10978, bsc#1233326: Fix unintended interactions
    between SET SESSION AUTHORIZATION and SET ROLE
  * CVE-2024-10979, bsc#1233327: Prevent trusted PL/Perl code from
    changing environment variables.
  * obsoletes postgresql17-jsonb_jsonpath.patch
  * https://www.postgresql.org/about/news/p-2955/
  * https://www.postgresql.org/docs/release/17.1/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1732017600">- Upgrade to 17.2:
  * Repair ABI break for extensions that work with struct
    ResultRelInfo.
  * Restore functionality of ALTER {ROLE|DATABASE} SET role.
  * Fix cases where a logical replication slot's restart_lsn could
    go backwards.
  * Avoid deleting still-needed WAL files during pg_rewind.
  * Fix race conditions associated with dropping shared statistics
    entries.
  * Count index scans in contrib/bloom indexes in the statistics
    views, such as the pg_stat_user_indexes.idx_scan counter.
  * Fix crash when checking to see if an index's opclass options
    have changed.
  * Avoid assertion failure caused by disconnected NFA sub-graphs
    in regular expression parsing.
  * https://www.postgresql.org/about/news/p-2965/
  * https://www.postgresql.org/docs/release/17.2/</changelog>
  <changelog author="JS &lt;obs.coke518@passinbox.com&gt;" date="1735214400">- Disable LLVM JIT on loongarch64</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="JS &lt;obs.coke518@passinbox.com&gt;" date="1738152000">- Apply postgresql-tzdata2025a.patch regardless of
  whether LLVM JIT is enabled</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 17.3:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/17.3/
  * https://www.postgresql.org/about/news/-3015/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 17.4:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/17.4/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 17.5:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/17.5/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to Fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Update to 17.6
  * https://www.postgresql.org/about/news/postgresql-176-1610-1514-1419-1322-and-18-beta-3-released-3118/
  * https://www.postgresql.org/docs/release/17.6/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1756036800">- switch library to pg 18</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1756987200">- Sync spec file with version 18.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Update to 17.7:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/17.7/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 17.8:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/17.8/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 17.9 to fix two regressions in 17.8:
  * https://www.postgresql.org/docs/release/17.9/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
</package>
<package pkgid="52718d8d6d505f18c7d24d02ace5a2d88a9bcec8e8bcbbf5dd9d381f5621e791215192ee760f82741a69877f1dfabc8874f79eecbc64ed70bd33f24d825fca12" name="postgresql17-pltcl" arch="aarch64">
  <version epoch="0" ver="17.9" rel="54.2"/>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1727352000">- Upgrade to 17.0:
  * New memory management system for VACUUM, which reduces memory
    consumption and can improve overall vacuuming performance.
  * New SQL/JSON capabilities, including constructors, identity
    functions, and the JSON_TABLE() function, which converts JSON
    data into a table representation.
  * Various query performance improvements, including for
    sequential reads using streaming I/O, write throughput under
    high concurrency, and searches over multiple values in a btree
    index.
  * Logical replication enhancements, including:
    + Failover control
    + pg_createsubscriber, a utility that creates logical replicas
    from physical standbys
    + pg_upgrade now preserves replication slots on both publishers
    and subscribers
  * New client-side connection option, sslnegotiation=direct, that
    performs a direct TLS handshake to avoid a round-trip
    negotiation.
  * pg_basebackup now supports incremental backup.
  * COPY adds a new option, ON_ERROR ignore, that allows a copy
    operation to continue in the event of an error.
  * https://www.postgresql.org/about/news/p-2936/
  * https://www.postgresql.org/docs/17/release-17.html</changelog>
  <changelog author="Fabian Vogt &lt;fvogt@suse.com&gt;" date="1728302400">- Use cmake(LLVM) &lt; instead of &lt;= to also allow building against
  LLVM 18.1 and newer 18.x versions</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1730721600">- Add postgresql17-jsonb_jsonpath.patch as a temporary build fix.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1731499200">- Upgrade to 17.1:
  * CVE-2024-10976, bsc#1233323: Ensure cached plans are marked as
    dependent on the calling role when RLS applies to a
    non-top-level table reference.
  * CVE-2024-10977, bsc#1233325: Make libpq discard error messages
    received during SSL or GSS protocol negotiation.
  * CVE-2024-10978, bsc#1233326: Fix unintended interactions
    between SET SESSION AUTHORIZATION and SET ROLE
  * CVE-2024-10979, bsc#1233327: Prevent trusted PL/Perl code from
    changing environment variables.
  * obsoletes postgresql17-jsonb_jsonpath.patch
  * https://www.postgresql.org/about/news/p-2955/
  * https://www.postgresql.org/docs/release/17.1/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1732017600">- Upgrade to 17.2:
  * Repair ABI break for extensions that work with struct
    ResultRelInfo.
  * Restore functionality of ALTER {ROLE|DATABASE} SET role.
  * Fix cases where a logical replication slot's restart_lsn could
    go backwards.
  * Avoid deleting still-needed WAL files during pg_rewind.
  * Fix race conditions associated with dropping shared statistics
    entries.
  * Count index scans in contrib/bloom indexes in the statistics
    views, such as the pg_stat_user_indexes.idx_scan counter.
  * Fix crash when checking to see if an index's opclass options
    have changed.
  * Avoid assertion failure caused by disconnected NFA sub-graphs
    in regular expression parsing.
  * https://www.postgresql.org/about/news/p-2965/
  * https://www.postgresql.org/docs/release/17.2/</changelog>
  <changelog author="JS &lt;obs.coke518@passinbox.com&gt;" date="1735214400">- Disable LLVM JIT on loongarch64</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="JS &lt;obs.coke518@passinbox.com&gt;" date="1738152000">- Apply postgresql-tzdata2025a.patch regardless of
  whether LLVM JIT is enabled</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 17.3:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/17.3/
  * https://www.postgresql.org/about/news/-3015/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 17.4:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/17.4/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 17.5:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/17.5/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to Fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Update to 17.6
  * https://www.postgresql.org/about/news/postgresql-176-1610-1514-1419-1322-and-18-beta-3-released-3118/
  * https://www.postgresql.org/docs/release/17.6/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1756036800">- switch library to pg 18</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1756987200">- Sync spec file with version 18.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Update to 17.7:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/17.7/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 17.8:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/17.8/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 17.9 to fix two regressions in 17.8:
  * https://www.postgresql.org/docs/release/17.9/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
</package>
<package pkgid="dfe60d4f0e343e3fe922b3878ae35315fafef3dcbf13bc634c10cb8aa3a0357874f70cec21b5b27bdca63a005727110f0d0aef2d3fc14d543ff02fed5a6618f2" name="postgresql17-pltcl" arch="ppc64le">
  <version epoch="0" ver="17.9" rel="55.1"/>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1727352000">- Upgrade to 17.0:
  * New memory management system for VACUUM, which reduces memory
    consumption and can improve overall vacuuming performance.
  * New SQL/JSON capabilities, including constructors, identity
    functions, and the JSON_TABLE() function, which converts JSON
    data into a table representation.
  * Various query performance improvements, including for
    sequential reads using streaming I/O, write throughput under
    high concurrency, and searches over multiple values in a btree
    index.
  * Logical replication enhancements, including:
    + Failover control
    + pg_createsubscriber, a utility that creates logical replicas
    from physical standbys
    + pg_upgrade now preserves replication slots on both publishers
    and subscribers
  * New client-side connection option, sslnegotiation=direct, that
    performs a direct TLS handshake to avoid a round-trip
    negotiation.
  * pg_basebackup now supports incremental backup.
  * COPY adds a new option, ON_ERROR ignore, that allows a copy
    operation to continue in the event of an error.
  * https://www.postgresql.org/about/news/p-2936/
  * https://www.postgresql.org/docs/17/release-17.html</changelog>
  <changelog author="Fabian Vogt &lt;fvogt@suse.com&gt;" date="1728302400">- Use cmake(LLVM) &lt; instead of &lt;= to also allow building against
  LLVM 18.1 and newer 18.x versions</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1730721600">- Add postgresql17-jsonb_jsonpath.patch as a temporary build fix.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1731499200">- Upgrade to 17.1:
  * CVE-2024-10976, bsc#1233323: Ensure cached plans are marked as
    dependent on the calling role when RLS applies to a
    non-top-level table reference.
  * CVE-2024-10977, bsc#1233325: Make libpq discard error messages
    received during SSL or GSS protocol negotiation.
  * CVE-2024-10978, bsc#1233326: Fix unintended interactions
    between SET SESSION AUTHORIZATION and SET ROLE
  * CVE-2024-10979, bsc#1233327: Prevent trusted PL/Perl code from
    changing environment variables.
  * obsoletes postgresql17-jsonb_jsonpath.patch
  * https://www.postgresql.org/about/news/p-2955/
  * https://www.postgresql.org/docs/release/17.1/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1732017600">- Upgrade to 17.2:
  * Repair ABI break for extensions that work with struct
    ResultRelInfo.
  * Restore functionality of ALTER {ROLE|DATABASE} SET role.
  * Fix cases where a logical replication slot's restart_lsn could
    go backwards.
  * Avoid deleting still-needed WAL files during pg_rewind.
  * Fix race conditions associated with dropping shared statistics
    entries.
  * Count index scans in contrib/bloom indexes in the statistics
    views, such as the pg_stat_user_indexes.idx_scan counter.
  * Fix crash when checking to see if an index's opclass options
    have changed.
  * Avoid assertion failure caused by disconnected NFA sub-graphs
    in regular expression parsing.
  * https://www.postgresql.org/about/news/p-2965/
  * https://www.postgresql.org/docs/release/17.2/</changelog>
  <changelog author="JS &lt;obs.coke518@passinbox.com&gt;" date="1735214400">- Disable LLVM JIT on loongarch64</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="JS &lt;obs.coke518@passinbox.com&gt;" date="1738152000">- Apply postgresql-tzdata2025a.patch regardless of
  whether LLVM JIT is enabled</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 17.3:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/17.3/
  * https://www.postgresql.org/about/news/-3015/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 17.4:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/17.4/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 17.5:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/17.5/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to Fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Update to 17.6
  * https://www.postgresql.org/about/news/postgresql-176-1610-1514-1419-1322-and-18-beta-3-released-3118/
  * https://www.postgresql.org/docs/release/17.6/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1756036800">- switch library to pg 18</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1756987200">- Sync spec file with version 18.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Update to 17.7:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/17.7/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 17.8:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/17.8/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 17.9 to fix two regressions in 17.8:
  * https://www.postgresql.org/docs/release/17.9/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
</package>
<package pkgid="53a53cd2364805b55cc02b9da03a3c0d973c00efd94ccbc460c5a466c52342fa095b2df5c77fcbbc92e97f881a6eb539cb1f0ac76143d39dff6d0f7ea63d8e60" name="postgresql17-server" arch="x86_64">
  <version epoch="0" ver="17.10" rel="69.2"/>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1731499200">- Upgrade to 17.1:
  * CVE-2024-10976, bsc#1233323: Ensure cached plans are marked as
    dependent on the calling role when RLS applies to a
    non-top-level table reference.
  * CVE-2024-10977, bsc#1233325: Make libpq discard error messages
    received during SSL or GSS protocol negotiation.
  * CVE-2024-10978, bsc#1233326: Fix unintended interactions
    between SET SESSION AUTHORIZATION and SET ROLE
  * CVE-2024-10979, bsc#1233327: Prevent trusted PL/Perl code from
    changing environment variables.
  * obsoletes postgresql17-jsonb_jsonpath.patch
  * https://www.postgresql.org/about/news/p-2955/
  * https://www.postgresql.org/docs/release/17.1/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1732017600">- Upgrade to 17.2:
  * Repair ABI break for extensions that work with struct
    ResultRelInfo.
  * Restore functionality of ALTER {ROLE|DATABASE} SET role.
  * Fix cases where a logical replication slot's restart_lsn could
    go backwards.
  * Avoid deleting still-needed WAL files during pg_rewind.
  * Fix race conditions associated with dropping shared statistics
    entries.
  * Count index scans in contrib/bloom indexes in the statistics
    views, such as the pg_stat_user_indexes.idx_scan counter.
  * Fix crash when checking to see if an index's opclass options
    have changed.
  * Avoid assertion failure caused by disconnected NFA sub-graphs
    in regular expression parsing.
  * https://www.postgresql.org/about/news/p-2965/
  * https://www.postgresql.org/docs/release/17.2/</changelog>
  <changelog author="JS &lt;obs.coke518@passinbox.com&gt;" date="1735214400">- Disable LLVM JIT on loongarch64</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="JS &lt;obs.coke518@passinbox.com&gt;" date="1738152000">- Apply postgresql-tzdata2025a.patch regardless of
  whether LLVM JIT is enabled</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 17.3:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/17.3/
  * https://www.postgresql.org/about/news/-3015/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 17.4:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/17.4/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 17.5:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/17.5/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to Fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Update to 17.6
  * https://www.postgresql.org/about/news/postgresql-176-1610-1514-1419-1322-and-18-beta-3-released-3118/
  * https://www.postgresql.org/docs/release/17.6/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1756036800">- switch library to pg 18</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1756987200">- Sync spec file with version 18.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Update to 17.7:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/17.7/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 17.8:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/17.8/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 17.9 to fix two regressions in 17.8:
  * https://www.postgresql.org/docs/release/17.9/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1774872000">- Get rid of update-alternatives for openSUSE/SLE 16.0 and newer
  to support immutable systems and transactional updates.
  (jsc#PED-14825, bsc#1245875)</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1777550400">- bsc#1263804: After dropping update-alternatives we have to
  package /usr/bin/pg_config as an actual symlink, not %ghost.
- Fix spelling of build conditionals.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1778673600">- Update to version 17.10:
  * bsc#1265172, CVE-2026-6472: ensure the user has CREATE
    privilege on the schema specified
  * bsc#1265173, CVE-2026-6473: integer overflows in
    memory-allocation calculations
  * bsc#1265174, CVE-2026-6474: Guard against malicious time zone
    names
  * bsc#1265175, CVE-2026-6475: Prevent path traversal in
    pg_basebackup and pg_rewind
  * bsc#1265176, CVE-2026-6476: Properly quote subscription names
    in pg_createsubscriber
  * bsc#1265177, CVE-2026-6477: Mark PQfn() as unsafe, and avoid
    using it within libpq
  * bsc#1265178, CVE-2026-6478: Use timing-safe string comparisons
    in authentication code
  * bsc#1265179, CVE-2026-6479: Prevent unbounded recursion while
    processing startup packets
  * bsc#1265181, CVE-2026-6637: Prevent SQL injection and buffer
    overruns in contrib/spi
  * bsc#1265182, CVE-2026-6638: Properly quote object names in
    logical replication origin checks
  * https://www.postgresql.org/docs/release/17.10/</changelog>
</package>
<package pkgid="4c323e1680b3ad6c5bf821caeb913e91f40cdcf0d16394965788517548e9e8d2e30fc6d81c9e64b4b5f0b78294d18c36adc61cdba9dfe524dee9826f04e12e2e" name="postgresql17-server" arch="s390x">
  <version epoch="0" ver="17.9" rel="53.1"/>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1727352000">- Upgrade to 17.0:
  * New memory management system for VACUUM, which reduces memory
    consumption and can improve overall vacuuming performance.
  * New SQL/JSON capabilities, including constructors, identity
    functions, and the JSON_TABLE() function, which converts JSON
    data into a table representation.
  * Various query performance improvements, including for
    sequential reads using streaming I/O, write throughput under
    high concurrency, and searches over multiple values in a btree
    index.
  * Logical replication enhancements, including:
    + Failover control
    + pg_createsubscriber, a utility that creates logical replicas
    from physical standbys
    + pg_upgrade now preserves replication slots on both publishers
    and subscribers
  * New client-side connection option, sslnegotiation=direct, that
    performs a direct TLS handshake to avoid a round-trip
    negotiation.
  * pg_basebackup now supports incremental backup.
  * COPY adds a new option, ON_ERROR ignore, that allows a copy
    operation to continue in the event of an error.
  * https://www.postgresql.org/about/news/p-2936/
  * https://www.postgresql.org/docs/17/release-17.html</changelog>
  <changelog author="Fabian Vogt &lt;fvogt@suse.com&gt;" date="1728302400">- Use cmake(LLVM) &lt; instead of &lt;= to also allow building against
  LLVM 18.1 and newer 18.x versions</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1730721600">- Add postgresql17-jsonb_jsonpath.patch as a temporary build fix.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1731499200">- Upgrade to 17.1:
  * CVE-2024-10976, bsc#1233323: Ensure cached plans are marked as
    dependent on the calling role when RLS applies to a
    non-top-level table reference.
  * CVE-2024-10977, bsc#1233325: Make libpq discard error messages
    received during SSL or GSS protocol negotiation.
  * CVE-2024-10978, bsc#1233326: Fix unintended interactions
    between SET SESSION AUTHORIZATION and SET ROLE
  * CVE-2024-10979, bsc#1233327: Prevent trusted PL/Perl code from
    changing environment variables.
  * obsoletes postgresql17-jsonb_jsonpath.patch
  * https://www.postgresql.org/about/news/p-2955/
  * https://www.postgresql.org/docs/release/17.1/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1732017600">- Upgrade to 17.2:
  * Repair ABI break for extensions that work with struct
    ResultRelInfo.
  * Restore functionality of ALTER {ROLE|DATABASE} SET role.
  * Fix cases where a logical replication slot's restart_lsn could
    go backwards.
  * Avoid deleting still-needed WAL files during pg_rewind.
  * Fix race conditions associated with dropping shared statistics
    entries.
  * Count index scans in contrib/bloom indexes in the statistics
    views, such as the pg_stat_user_indexes.idx_scan counter.
  * Fix crash when checking to see if an index's opclass options
    have changed.
  * Avoid assertion failure caused by disconnected NFA sub-graphs
    in regular expression parsing.
  * https://www.postgresql.org/about/news/p-2965/
  * https://www.postgresql.org/docs/release/17.2/</changelog>
  <changelog author="JS &lt;obs.coke518@passinbox.com&gt;" date="1735214400">- Disable LLVM JIT on loongarch64</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="JS &lt;obs.coke518@passinbox.com&gt;" date="1738152000">- Apply postgresql-tzdata2025a.patch regardless of
  whether LLVM JIT is enabled</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 17.3:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/17.3/
  * https://www.postgresql.org/about/news/-3015/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 17.4:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/17.4/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 17.5:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/17.5/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to Fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Update to 17.6
  * https://www.postgresql.org/about/news/postgresql-176-1610-1514-1419-1322-and-18-beta-3-released-3118/
  * https://www.postgresql.org/docs/release/17.6/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1756036800">- switch library to pg 18</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1756987200">- Sync spec file with version 18.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Update to 17.7:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/17.7/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 17.8:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/17.8/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 17.9 to fix two regressions in 17.8:
  * https://www.postgresql.org/docs/release/17.9/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
</package>
<package pkgid="cd10dcbc95b69a673ba58e542f0b71be3e20cd367a32bc9b88f9c24a5f6c2a4745c730d1d6748a4f1f83170cd8f35bae2e6e21ac4c94dea658ff391f4b0730a0" name="postgresql17-server" arch="aarch64">
  <version epoch="0" ver="17.9" rel="54.2"/>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1727352000">- Upgrade to 17.0:
  * New memory management system for VACUUM, which reduces memory
    consumption and can improve overall vacuuming performance.
  * New SQL/JSON capabilities, including constructors, identity
    functions, and the JSON_TABLE() function, which converts JSON
    data into a table representation.
  * Various query performance improvements, including for
    sequential reads using streaming I/O, write throughput under
    high concurrency, and searches over multiple values in a btree
    index.
  * Logical replication enhancements, including:
    + Failover control
    + pg_createsubscriber, a utility that creates logical replicas
    from physical standbys
    + pg_upgrade now preserves replication slots on both publishers
    and subscribers
  * New client-side connection option, sslnegotiation=direct, that
    performs a direct TLS handshake to avoid a round-trip
    negotiation.
  * pg_basebackup now supports incremental backup.
  * COPY adds a new option, ON_ERROR ignore, that allows a copy
    operation to continue in the event of an error.
  * https://www.postgresql.org/about/news/p-2936/
  * https://www.postgresql.org/docs/17/release-17.html</changelog>
  <changelog author="Fabian Vogt &lt;fvogt@suse.com&gt;" date="1728302400">- Use cmake(LLVM) &lt; instead of &lt;= to also allow building against
  LLVM 18.1 and newer 18.x versions</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1730721600">- Add postgresql17-jsonb_jsonpath.patch as a temporary build fix.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1731499200">- Upgrade to 17.1:
  * CVE-2024-10976, bsc#1233323: Ensure cached plans are marked as
    dependent on the calling role when RLS applies to a
    non-top-level table reference.
  * CVE-2024-10977, bsc#1233325: Make libpq discard error messages
    received during SSL or GSS protocol negotiation.
  * CVE-2024-10978, bsc#1233326: Fix unintended interactions
    between SET SESSION AUTHORIZATION and SET ROLE
  * CVE-2024-10979, bsc#1233327: Prevent trusted PL/Perl code from
    changing environment variables.
  * obsoletes postgresql17-jsonb_jsonpath.patch
  * https://www.postgresql.org/about/news/p-2955/
  * https://www.postgresql.org/docs/release/17.1/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1732017600">- Upgrade to 17.2:
  * Repair ABI break for extensions that work with struct
    ResultRelInfo.
  * Restore functionality of ALTER {ROLE|DATABASE} SET role.
  * Fix cases where a logical replication slot's restart_lsn could
    go backwards.
  * Avoid deleting still-needed WAL files during pg_rewind.
  * Fix race conditions associated with dropping shared statistics
    entries.
  * Count index scans in contrib/bloom indexes in the statistics
    views, such as the pg_stat_user_indexes.idx_scan counter.
  * Fix crash when checking to see if an index's opclass options
    have changed.
  * Avoid assertion failure caused by disconnected NFA sub-graphs
    in regular expression parsing.
  * https://www.postgresql.org/about/news/p-2965/
  * https://www.postgresql.org/docs/release/17.2/</changelog>
  <changelog author="JS &lt;obs.coke518@passinbox.com&gt;" date="1735214400">- Disable LLVM JIT on loongarch64</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="JS &lt;obs.coke518@passinbox.com&gt;" date="1738152000">- Apply postgresql-tzdata2025a.patch regardless of
  whether LLVM JIT is enabled</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 17.3:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/17.3/
  * https://www.postgresql.org/about/news/-3015/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 17.4:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/17.4/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 17.5:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/17.5/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to Fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Update to 17.6
  * https://www.postgresql.org/about/news/postgresql-176-1610-1514-1419-1322-and-18-beta-3-released-3118/
  * https://www.postgresql.org/docs/release/17.6/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1756036800">- switch library to pg 18</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1756987200">- Sync spec file with version 18.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Update to 17.7:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/17.7/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 17.8:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/17.8/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 17.9 to fix two regressions in 17.8:
  * https://www.postgresql.org/docs/release/17.9/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
</package>
<package pkgid="7402178f7b9d765a0c4bfad7a5267b631090997143ca9300b7123defc1705a4527dc9c584b05730256b91272d6cab6507ef8bb5006a3edc17146f8dbc87ef9c1" name="postgresql17-server" arch="ppc64le">
  <version epoch="0" ver="17.9" rel="55.1"/>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1727352000">- Upgrade to 17.0:
  * New memory management system for VACUUM, which reduces memory
    consumption and can improve overall vacuuming performance.
  * New SQL/JSON capabilities, including constructors, identity
    functions, and the JSON_TABLE() function, which converts JSON
    data into a table representation.
  * Various query performance improvements, including for
    sequential reads using streaming I/O, write throughput under
    high concurrency, and searches over multiple values in a btree
    index.
  * Logical replication enhancements, including:
    + Failover control
    + pg_createsubscriber, a utility that creates logical replicas
    from physical standbys
    + pg_upgrade now preserves replication slots on both publishers
    and subscribers
  * New client-side connection option, sslnegotiation=direct, that
    performs a direct TLS handshake to avoid a round-trip
    negotiation.
  * pg_basebackup now supports incremental backup.
  * COPY adds a new option, ON_ERROR ignore, that allows a copy
    operation to continue in the event of an error.
  * https://www.postgresql.org/about/news/p-2936/
  * https://www.postgresql.org/docs/17/release-17.html</changelog>
  <changelog author="Fabian Vogt &lt;fvogt@suse.com&gt;" date="1728302400">- Use cmake(LLVM) &lt; instead of &lt;= to also allow building against
  LLVM 18.1 and newer 18.x versions</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1730721600">- Add postgresql17-jsonb_jsonpath.patch as a temporary build fix.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1731499200">- Upgrade to 17.1:
  * CVE-2024-10976, bsc#1233323: Ensure cached plans are marked as
    dependent on the calling role when RLS applies to a
    non-top-level table reference.
  * CVE-2024-10977, bsc#1233325: Make libpq discard error messages
    received during SSL or GSS protocol negotiation.
  * CVE-2024-10978, bsc#1233326: Fix unintended interactions
    between SET SESSION AUTHORIZATION and SET ROLE
  * CVE-2024-10979, bsc#1233327: Prevent trusted PL/Perl code from
    changing environment variables.
  * obsoletes postgresql17-jsonb_jsonpath.patch
  * https://www.postgresql.org/about/news/p-2955/
  * https://www.postgresql.org/docs/release/17.1/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1732017600">- Upgrade to 17.2:
  * Repair ABI break for extensions that work with struct
    ResultRelInfo.
  * Restore functionality of ALTER {ROLE|DATABASE} SET role.
  * Fix cases where a logical replication slot's restart_lsn could
    go backwards.
  * Avoid deleting still-needed WAL files during pg_rewind.
  * Fix race conditions associated with dropping shared statistics
    entries.
  * Count index scans in contrib/bloom indexes in the statistics
    views, such as the pg_stat_user_indexes.idx_scan counter.
  * Fix crash when checking to see if an index's opclass options
    have changed.
  * Avoid assertion failure caused by disconnected NFA sub-graphs
    in regular expression parsing.
  * https://www.postgresql.org/about/news/p-2965/
  * https://www.postgresql.org/docs/release/17.2/</changelog>
  <changelog author="JS &lt;obs.coke518@passinbox.com&gt;" date="1735214400">- Disable LLVM JIT on loongarch64</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="JS &lt;obs.coke518@passinbox.com&gt;" date="1738152000">- Apply postgresql-tzdata2025a.patch regardless of
  whether LLVM JIT is enabled</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 17.3:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/17.3/
  * https://www.postgresql.org/about/news/-3015/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 17.4:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/17.4/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 17.5:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/17.5/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to Fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Update to 17.6
  * https://www.postgresql.org/about/news/postgresql-176-1610-1514-1419-1322-and-18-beta-3-released-3118/
  * https://www.postgresql.org/docs/release/17.6/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1756036800">- switch library to pg 18</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1756987200">- Sync spec file with version 18.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Update to 17.7:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/17.7/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 17.8:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/17.8/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 17.9 to fix two regressions in 17.8:
  * https://www.postgresql.org/docs/release/17.9/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
</package>
<package pkgid="e509f66a3d1e8aaa0786f2985adef69e89d1364920bfc5c409f6b60688be28f7269e68ffebcaa9a4f639e1ea156d6a3d846dfe542e3105676308a61a00faa58e" name="postgresql17-server-devel" arch="x86_64">
  <version epoch="0" ver="17.10" rel="69.2"/>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1731499200">- Upgrade to 17.1:
  * CVE-2024-10976, bsc#1233323: Ensure cached plans are marked as
    dependent on the calling role when RLS applies to a
    non-top-level table reference.
  * CVE-2024-10977, bsc#1233325: Make libpq discard error messages
    received during SSL or GSS protocol negotiation.
  * CVE-2024-10978, bsc#1233326: Fix unintended interactions
    between SET SESSION AUTHORIZATION and SET ROLE
  * CVE-2024-10979, bsc#1233327: Prevent trusted PL/Perl code from
    changing environment variables.
  * obsoletes postgresql17-jsonb_jsonpath.patch
  * https://www.postgresql.org/about/news/p-2955/
  * https://www.postgresql.org/docs/release/17.1/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1732017600">- Upgrade to 17.2:
  * Repair ABI break for extensions that work with struct
    ResultRelInfo.
  * Restore functionality of ALTER {ROLE|DATABASE} SET role.
  * Fix cases where a logical replication slot's restart_lsn could
    go backwards.
  * Avoid deleting still-needed WAL files during pg_rewind.
  * Fix race conditions associated with dropping shared statistics
    entries.
  * Count index scans in contrib/bloom indexes in the statistics
    views, such as the pg_stat_user_indexes.idx_scan counter.
  * Fix crash when checking to see if an index's opclass options
    have changed.
  * Avoid assertion failure caused by disconnected NFA sub-graphs
    in regular expression parsing.
  * https://www.postgresql.org/about/news/p-2965/
  * https://www.postgresql.org/docs/release/17.2/</changelog>
  <changelog author="JS &lt;obs.coke518@passinbox.com&gt;" date="1735214400">- Disable LLVM JIT on loongarch64</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="JS &lt;obs.coke518@passinbox.com&gt;" date="1738152000">- Apply postgresql-tzdata2025a.patch regardless of
  whether LLVM JIT is enabled</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 17.3:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/17.3/
  * https://www.postgresql.org/about/news/-3015/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 17.4:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/17.4/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 17.5:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/17.5/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to Fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Update to 17.6
  * https://www.postgresql.org/about/news/postgresql-176-1610-1514-1419-1322-and-18-beta-3-released-3118/
  * https://www.postgresql.org/docs/release/17.6/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1756036800">- switch library to pg 18</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1756987200">- Sync spec file with version 18.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Update to 17.7:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/17.7/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 17.8:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/17.8/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 17.9 to fix two regressions in 17.8:
  * https://www.postgresql.org/docs/release/17.9/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1774872000">- Get rid of update-alternatives for openSUSE/SLE 16.0 and newer
  to support immutable systems and transactional updates.
  (jsc#PED-14825, bsc#1245875)</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1777550400">- bsc#1263804: After dropping update-alternatives we have to
  package /usr/bin/pg_config as an actual symlink, not %ghost.
- Fix spelling of build conditionals.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1778673600">- Update to version 17.10:
  * bsc#1265172, CVE-2026-6472: ensure the user has CREATE
    privilege on the schema specified
  * bsc#1265173, CVE-2026-6473: integer overflows in
    memory-allocation calculations
  * bsc#1265174, CVE-2026-6474: Guard against malicious time zone
    names
  * bsc#1265175, CVE-2026-6475: Prevent path traversal in
    pg_basebackup and pg_rewind
  * bsc#1265176, CVE-2026-6476: Properly quote subscription names
    in pg_createsubscriber
  * bsc#1265177, CVE-2026-6477: Mark PQfn() as unsafe, and avoid
    using it within libpq
  * bsc#1265178, CVE-2026-6478: Use timing-safe string comparisons
    in authentication code
  * bsc#1265179, CVE-2026-6479: Prevent unbounded recursion while
    processing startup packets
  * bsc#1265181, CVE-2026-6637: Prevent SQL injection and buffer
    overruns in contrib/spi
  * bsc#1265182, CVE-2026-6638: Properly quote object names in
    logical replication origin checks
  * https://www.postgresql.org/docs/release/17.10/</changelog>
</package>
<package pkgid="cc58b103bcd8be814543c414badfdfd49901d061ab5e2af4255c9a03ab8a7533fe35aa2f027627ab19ee0dbd4f71fa60fc3130519e036d0ad7e099776724933e" name="postgresql17-server-devel" arch="s390x">
  <version epoch="0" ver="17.9" rel="53.1"/>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1727352000">- Upgrade to 17.0:
  * New memory management system for VACUUM, which reduces memory
    consumption and can improve overall vacuuming performance.
  * New SQL/JSON capabilities, including constructors, identity
    functions, and the JSON_TABLE() function, which converts JSON
    data into a table representation.
  * Various query performance improvements, including for
    sequential reads using streaming I/O, write throughput under
    high concurrency, and searches over multiple values in a btree
    index.
  * Logical replication enhancements, including:
    + Failover control
    + pg_createsubscriber, a utility that creates logical replicas
    from physical standbys
    + pg_upgrade now preserves replication slots on both publishers
    and subscribers
  * New client-side connection option, sslnegotiation=direct, that
    performs a direct TLS handshake to avoid a round-trip
    negotiation.
  * pg_basebackup now supports incremental backup.
  * COPY adds a new option, ON_ERROR ignore, that allows a copy
    operation to continue in the event of an error.
  * https://www.postgresql.org/about/news/p-2936/
  * https://www.postgresql.org/docs/17/release-17.html</changelog>
  <changelog author="Fabian Vogt &lt;fvogt@suse.com&gt;" date="1728302400">- Use cmake(LLVM) &lt; instead of &lt;= to also allow building against
  LLVM 18.1 and newer 18.x versions</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1730721600">- Add postgresql17-jsonb_jsonpath.patch as a temporary build fix.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1731499200">- Upgrade to 17.1:
  * CVE-2024-10976, bsc#1233323: Ensure cached plans are marked as
    dependent on the calling role when RLS applies to a
    non-top-level table reference.
  * CVE-2024-10977, bsc#1233325: Make libpq discard error messages
    received during SSL or GSS protocol negotiation.
  * CVE-2024-10978, bsc#1233326: Fix unintended interactions
    between SET SESSION AUTHORIZATION and SET ROLE
  * CVE-2024-10979, bsc#1233327: Prevent trusted PL/Perl code from
    changing environment variables.
  * obsoletes postgresql17-jsonb_jsonpath.patch
  * https://www.postgresql.org/about/news/p-2955/
  * https://www.postgresql.org/docs/release/17.1/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1732017600">- Upgrade to 17.2:
  * Repair ABI break for extensions that work with struct
    ResultRelInfo.
  * Restore functionality of ALTER {ROLE|DATABASE} SET role.
  * Fix cases where a logical replication slot's restart_lsn could
    go backwards.
  * Avoid deleting still-needed WAL files during pg_rewind.
  * Fix race conditions associated with dropping shared statistics
    entries.
  * Count index scans in contrib/bloom indexes in the statistics
    views, such as the pg_stat_user_indexes.idx_scan counter.
  * Fix crash when checking to see if an index's opclass options
    have changed.
  * Avoid assertion failure caused by disconnected NFA sub-graphs
    in regular expression parsing.
  * https://www.postgresql.org/about/news/p-2965/
  * https://www.postgresql.org/docs/release/17.2/</changelog>
  <changelog author="JS &lt;obs.coke518@passinbox.com&gt;" date="1735214400">- Disable LLVM JIT on loongarch64</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="JS &lt;obs.coke518@passinbox.com&gt;" date="1738152000">- Apply postgresql-tzdata2025a.patch regardless of
  whether LLVM JIT is enabled</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 17.3:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/17.3/
  * https://www.postgresql.org/about/news/-3015/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 17.4:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/17.4/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 17.5:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/17.5/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to Fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Update to 17.6
  * https://www.postgresql.org/about/news/postgresql-176-1610-1514-1419-1322-and-18-beta-3-released-3118/
  * https://www.postgresql.org/docs/release/17.6/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1756036800">- switch library to pg 18</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1756987200">- Sync spec file with version 18.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Update to 17.7:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/17.7/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 17.8:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/17.8/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 17.9 to fix two regressions in 17.8:
  * https://www.postgresql.org/docs/release/17.9/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
</package>
<package pkgid="07d07bd0108543596b3ed6e3bad76cb6fc82e80bf07615e0af64d6a6da7af20ae514b41f273fcfd0f308a4bdd707652c70b75be4bc5fdac035a7cc5aea547459" name="postgresql17-server-devel" arch="aarch64">
  <version epoch="0" ver="17.9" rel="54.2"/>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1727352000">- Upgrade to 17.0:
  * New memory management system for VACUUM, which reduces memory
    consumption and can improve overall vacuuming performance.
  * New SQL/JSON capabilities, including constructors, identity
    functions, and the JSON_TABLE() function, which converts JSON
    data into a table representation.
  * Various query performance improvements, including for
    sequential reads using streaming I/O, write throughput under
    high concurrency, and searches over multiple values in a btree
    index.
  * Logical replication enhancements, including:
    + Failover control
    + pg_createsubscriber, a utility that creates logical replicas
    from physical standbys
    + pg_upgrade now preserves replication slots on both publishers
    and subscribers
  * New client-side connection option, sslnegotiation=direct, that
    performs a direct TLS handshake to avoid a round-trip
    negotiation.
  * pg_basebackup now supports incremental backup.
  * COPY adds a new option, ON_ERROR ignore, that allows a copy
    operation to continue in the event of an error.
  * https://www.postgresql.org/about/news/p-2936/
  * https://www.postgresql.org/docs/17/release-17.html</changelog>
  <changelog author="Fabian Vogt &lt;fvogt@suse.com&gt;" date="1728302400">- Use cmake(LLVM) &lt; instead of &lt;= to also allow building against
  LLVM 18.1 and newer 18.x versions</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1730721600">- Add postgresql17-jsonb_jsonpath.patch as a temporary build fix.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1731499200">- Upgrade to 17.1:
  * CVE-2024-10976, bsc#1233323: Ensure cached plans are marked as
    dependent on the calling role when RLS applies to a
    non-top-level table reference.
  * CVE-2024-10977, bsc#1233325: Make libpq discard error messages
    received during SSL or GSS protocol negotiation.
  * CVE-2024-10978, bsc#1233326: Fix unintended interactions
    between SET SESSION AUTHORIZATION and SET ROLE
  * CVE-2024-10979, bsc#1233327: Prevent trusted PL/Perl code from
    changing environment variables.
  * obsoletes postgresql17-jsonb_jsonpath.patch
  * https://www.postgresql.org/about/news/p-2955/
  * https://www.postgresql.org/docs/release/17.1/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1732017600">- Upgrade to 17.2:
  * Repair ABI break for extensions that work with struct
    ResultRelInfo.
  * Restore functionality of ALTER {ROLE|DATABASE} SET role.
  * Fix cases where a logical replication slot's restart_lsn could
    go backwards.
  * Avoid deleting still-needed WAL files during pg_rewind.
  * Fix race conditions associated with dropping shared statistics
    entries.
  * Count index scans in contrib/bloom indexes in the statistics
    views, such as the pg_stat_user_indexes.idx_scan counter.
  * Fix crash when checking to see if an index's opclass options
    have changed.
  * Avoid assertion failure caused by disconnected NFA sub-graphs
    in regular expression parsing.
  * https://www.postgresql.org/about/news/p-2965/
  * https://www.postgresql.org/docs/release/17.2/</changelog>
  <changelog author="JS &lt;obs.coke518@passinbox.com&gt;" date="1735214400">- Disable LLVM JIT on loongarch64</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="JS &lt;obs.coke518@passinbox.com&gt;" date="1738152000">- Apply postgresql-tzdata2025a.patch regardless of
  whether LLVM JIT is enabled</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 17.3:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/17.3/
  * https://www.postgresql.org/about/news/-3015/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 17.4:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/17.4/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 17.5:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/17.5/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to Fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Update to 17.6
  * https://www.postgresql.org/about/news/postgresql-176-1610-1514-1419-1322-and-18-beta-3-released-3118/
  * https://www.postgresql.org/docs/release/17.6/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1756036800">- switch library to pg 18</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1756987200">- Sync spec file with version 18.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Update to 17.7:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/17.7/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 17.8:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/17.8/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 17.9 to fix two regressions in 17.8:
  * https://www.postgresql.org/docs/release/17.9/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
</package>
<package pkgid="2e2946475cf68606e6a37703cb88f0e60b2ada071b03349bf0dd1d245fb88dbf0da34ebcdf2f75307d1aff8a1d0a4f70f05236a47c1ac46bd1e53dadf6acae69" name="postgresql17-server-devel" arch="ppc64le">
  <version epoch="0" ver="17.9" rel="55.1"/>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1727352000">- Upgrade to 17.0:
  * New memory management system for VACUUM, which reduces memory
    consumption and can improve overall vacuuming performance.
  * New SQL/JSON capabilities, including constructors, identity
    functions, and the JSON_TABLE() function, which converts JSON
    data into a table representation.
  * Various query performance improvements, including for
    sequential reads using streaming I/O, write throughput under
    high concurrency, and searches over multiple values in a btree
    index.
  * Logical replication enhancements, including:
    + Failover control
    + pg_createsubscriber, a utility that creates logical replicas
    from physical standbys
    + pg_upgrade now preserves replication slots on both publishers
    and subscribers
  * New client-side connection option, sslnegotiation=direct, that
    performs a direct TLS handshake to avoid a round-trip
    negotiation.
  * pg_basebackup now supports incremental backup.
  * COPY adds a new option, ON_ERROR ignore, that allows a copy
    operation to continue in the event of an error.
  * https://www.postgresql.org/about/news/p-2936/
  * https://www.postgresql.org/docs/17/release-17.html</changelog>
  <changelog author="Fabian Vogt &lt;fvogt@suse.com&gt;" date="1728302400">- Use cmake(LLVM) &lt; instead of &lt;= to also allow building against
  LLVM 18.1 and newer 18.x versions</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1730721600">- Add postgresql17-jsonb_jsonpath.patch as a temporary build fix.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1731499200">- Upgrade to 17.1:
  * CVE-2024-10976, bsc#1233323: Ensure cached plans are marked as
    dependent on the calling role when RLS applies to a
    non-top-level table reference.
  * CVE-2024-10977, bsc#1233325: Make libpq discard error messages
    received during SSL or GSS protocol negotiation.
  * CVE-2024-10978, bsc#1233326: Fix unintended interactions
    between SET SESSION AUTHORIZATION and SET ROLE
  * CVE-2024-10979, bsc#1233327: Prevent trusted PL/Perl code from
    changing environment variables.
  * obsoletes postgresql17-jsonb_jsonpath.patch
  * https://www.postgresql.org/about/news/p-2955/
  * https://www.postgresql.org/docs/release/17.1/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1732017600">- Upgrade to 17.2:
  * Repair ABI break for extensions that work with struct
    ResultRelInfo.
  * Restore functionality of ALTER {ROLE|DATABASE} SET role.
  * Fix cases where a logical replication slot's restart_lsn could
    go backwards.
  * Avoid deleting still-needed WAL files during pg_rewind.
  * Fix race conditions associated with dropping shared statistics
    entries.
  * Count index scans in contrib/bloom indexes in the statistics
    views, such as the pg_stat_user_indexes.idx_scan counter.
  * Fix crash when checking to see if an index's opclass options
    have changed.
  * Avoid assertion failure caused by disconnected NFA sub-graphs
    in regular expression parsing.
  * https://www.postgresql.org/about/news/p-2965/
  * https://www.postgresql.org/docs/release/17.2/</changelog>
  <changelog author="JS &lt;obs.coke518@passinbox.com&gt;" date="1735214400">- Disable LLVM JIT on loongarch64</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="JS &lt;obs.coke518@passinbox.com&gt;" date="1738152000">- Apply postgresql-tzdata2025a.patch regardless of
  whether LLVM JIT is enabled</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 17.3:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/17.3/
  * https://www.postgresql.org/about/news/-3015/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 17.4:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/17.4/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 17.5:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/17.5/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to Fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Update to 17.6
  * https://www.postgresql.org/about/news/postgresql-176-1610-1514-1419-1322-and-18-beta-3-released-3118/
  * https://www.postgresql.org/docs/release/17.6/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1756036800">- switch library to pg 18</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1756987200">- Sync spec file with version 18.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Update to 17.7:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/17.7/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 17.8:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/17.8/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 17.9 to fix two regressions in 17.8:
  * https://www.postgresql.org/docs/release/17.9/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
</package>
<package pkgid="44679dbdeaec4af4bc9c53fdeea7f84391592cd31fbdcd98c7ccff7db842945e0ac9533f7fdcd5b0066c44f36d2947cce63996370449e03d011d4d3c51f78c2a" name="postgresql17-test" arch="x86_64">
  <version epoch="0" ver="17.10" rel="69.2"/>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1731499200">- Upgrade to 17.1:
  * CVE-2024-10976, bsc#1233323: Ensure cached plans are marked as
    dependent on the calling role when RLS applies to a
    non-top-level table reference.
  * CVE-2024-10977, bsc#1233325: Make libpq discard error messages
    received during SSL or GSS protocol negotiation.
  * CVE-2024-10978, bsc#1233326: Fix unintended interactions
    between SET SESSION AUTHORIZATION and SET ROLE
  * CVE-2024-10979, bsc#1233327: Prevent trusted PL/Perl code from
    changing environment variables.
  * obsoletes postgresql17-jsonb_jsonpath.patch
  * https://www.postgresql.org/about/news/p-2955/
  * https://www.postgresql.org/docs/release/17.1/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1732017600">- Upgrade to 17.2:
  * Repair ABI break for extensions that work with struct
    ResultRelInfo.
  * Restore functionality of ALTER {ROLE|DATABASE} SET role.
  * Fix cases where a logical replication slot's restart_lsn could
    go backwards.
  * Avoid deleting still-needed WAL files during pg_rewind.
  * Fix race conditions associated with dropping shared statistics
    entries.
  * Count index scans in contrib/bloom indexes in the statistics
    views, such as the pg_stat_user_indexes.idx_scan counter.
  * Fix crash when checking to see if an index's opclass options
    have changed.
  * Avoid assertion failure caused by disconnected NFA sub-graphs
    in regular expression parsing.
  * https://www.postgresql.org/about/news/p-2965/
  * https://www.postgresql.org/docs/release/17.2/</changelog>
  <changelog author="JS &lt;obs.coke518@passinbox.com&gt;" date="1735214400">- Disable LLVM JIT on loongarch64</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="JS &lt;obs.coke518@passinbox.com&gt;" date="1738152000">- Apply postgresql-tzdata2025a.patch regardless of
  whether LLVM JIT is enabled</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 17.3:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/17.3/
  * https://www.postgresql.org/about/news/-3015/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 17.4:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/17.4/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 17.5:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/17.5/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to Fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Update to 17.6
  * https://www.postgresql.org/about/news/postgresql-176-1610-1514-1419-1322-and-18-beta-3-released-3118/
  * https://www.postgresql.org/docs/release/17.6/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1756036800">- switch library to pg 18</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1756987200">- Sync spec file with version 18.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Update to 17.7:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/17.7/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 17.8:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/17.8/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 17.9 to fix two regressions in 17.8:
  * https://www.postgresql.org/docs/release/17.9/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1774872000">- Get rid of update-alternatives for openSUSE/SLE 16.0 and newer
  to support immutable systems and transactional updates.
  (jsc#PED-14825, bsc#1245875)</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1777550400">- bsc#1263804: After dropping update-alternatives we have to
  package /usr/bin/pg_config as an actual symlink, not %ghost.
- Fix spelling of build conditionals.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1778673600">- Update to version 17.10:
  * bsc#1265172, CVE-2026-6472: ensure the user has CREATE
    privilege on the schema specified
  * bsc#1265173, CVE-2026-6473: integer overflows in
    memory-allocation calculations
  * bsc#1265174, CVE-2026-6474: Guard against malicious time zone
    names
  * bsc#1265175, CVE-2026-6475: Prevent path traversal in
    pg_basebackup and pg_rewind
  * bsc#1265176, CVE-2026-6476: Properly quote subscription names
    in pg_createsubscriber
  * bsc#1265177, CVE-2026-6477: Mark PQfn() as unsafe, and avoid
    using it within libpq
  * bsc#1265178, CVE-2026-6478: Use timing-safe string comparisons
    in authentication code
  * bsc#1265179, CVE-2026-6479: Prevent unbounded recursion while
    processing startup packets
  * bsc#1265181, CVE-2026-6637: Prevent SQL injection and buffer
    overruns in contrib/spi
  * bsc#1265182, CVE-2026-6638: Properly quote object names in
    logical replication origin checks
  * https://www.postgresql.org/docs/release/17.10/</changelog>
</package>
<package pkgid="1066cc84fb49c2a3ffa764c7d6975bc41f843aa8ca1b3a01f949143aa59377f695be9d21f76f8d00a33bb3590faa44a208c936a019239825629d257ffbec2532" name="postgresql17-test" arch="s390x">
  <version epoch="0" ver="17.9" rel="53.1"/>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1727352000">- Upgrade to 17.0:
  * New memory management system for VACUUM, which reduces memory
    consumption and can improve overall vacuuming performance.
  * New SQL/JSON capabilities, including constructors, identity
    functions, and the JSON_TABLE() function, which converts JSON
    data into a table representation.
  * Various query performance improvements, including for
    sequential reads using streaming I/O, write throughput under
    high concurrency, and searches over multiple values in a btree
    index.
  * Logical replication enhancements, including:
    + Failover control
    + pg_createsubscriber, a utility that creates logical replicas
    from physical standbys
    + pg_upgrade now preserves replication slots on both publishers
    and subscribers
  * New client-side connection option, sslnegotiation=direct, that
    performs a direct TLS handshake to avoid a round-trip
    negotiation.
  * pg_basebackup now supports incremental backup.
  * COPY adds a new option, ON_ERROR ignore, that allows a copy
    operation to continue in the event of an error.
  * https://www.postgresql.org/about/news/p-2936/
  * https://www.postgresql.org/docs/17/release-17.html</changelog>
  <changelog author="Fabian Vogt &lt;fvogt@suse.com&gt;" date="1728302400">- Use cmake(LLVM) &lt; instead of &lt;= to also allow building against
  LLVM 18.1 and newer 18.x versions</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1730721600">- Add postgresql17-jsonb_jsonpath.patch as a temporary build fix.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1731499200">- Upgrade to 17.1:
  * CVE-2024-10976, bsc#1233323: Ensure cached plans are marked as
    dependent on the calling role when RLS applies to a
    non-top-level table reference.
  * CVE-2024-10977, bsc#1233325: Make libpq discard error messages
    received during SSL or GSS protocol negotiation.
  * CVE-2024-10978, bsc#1233326: Fix unintended interactions
    between SET SESSION AUTHORIZATION and SET ROLE
  * CVE-2024-10979, bsc#1233327: Prevent trusted PL/Perl code from
    changing environment variables.
  * obsoletes postgresql17-jsonb_jsonpath.patch
  * https://www.postgresql.org/about/news/p-2955/
  * https://www.postgresql.org/docs/release/17.1/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1732017600">- Upgrade to 17.2:
  * Repair ABI break for extensions that work with struct
    ResultRelInfo.
  * Restore functionality of ALTER {ROLE|DATABASE} SET role.
  * Fix cases where a logical replication slot's restart_lsn could
    go backwards.
  * Avoid deleting still-needed WAL files during pg_rewind.
  * Fix race conditions associated with dropping shared statistics
    entries.
  * Count index scans in contrib/bloom indexes in the statistics
    views, such as the pg_stat_user_indexes.idx_scan counter.
  * Fix crash when checking to see if an index's opclass options
    have changed.
  * Avoid assertion failure caused by disconnected NFA sub-graphs
    in regular expression parsing.
  * https://www.postgresql.org/about/news/p-2965/
  * https://www.postgresql.org/docs/release/17.2/</changelog>
  <changelog author="JS &lt;obs.coke518@passinbox.com&gt;" date="1735214400">- Disable LLVM JIT on loongarch64</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="JS &lt;obs.coke518@passinbox.com&gt;" date="1738152000">- Apply postgresql-tzdata2025a.patch regardless of
  whether LLVM JIT is enabled</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 17.3:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/17.3/
  * https://www.postgresql.org/about/news/-3015/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 17.4:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/17.4/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 17.5:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/17.5/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to Fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Update to 17.6
  * https://www.postgresql.org/about/news/postgresql-176-1610-1514-1419-1322-and-18-beta-3-released-3118/
  * https://www.postgresql.org/docs/release/17.6/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1756036800">- switch library to pg 18</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1756987200">- Sync spec file with version 18.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Update to 17.7:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/17.7/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 17.8:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/17.8/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 17.9 to fix two regressions in 17.8:
  * https://www.postgresql.org/docs/release/17.9/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
</package>
<package pkgid="cb328e5b65119c526ab8cf1aaf7e9b29eb0eea97301fadc9441bf95c0271c5d3c2f750e7a1527cd521926aec286c7910d8fb3c95264b2df8e77f4bc11b9e2fe3" name="postgresql17-test" arch="aarch64">
  <version epoch="0" ver="17.9" rel="54.2"/>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1727352000">- Upgrade to 17.0:
  * New memory management system for VACUUM, which reduces memory
    consumption and can improve overall vacuuming performance.
  * New SQL/JSON capabilities, including constructors, identity
    functions, and the JSON_TABLE() function, which converts JSON
    data into a table representation.
  * Various query performance improvements, including for
    sequential reads using streaming I/O, write throughput under
    high concurrency, and searches over multiple values in a btree
    index.
  * Logical replication enhancements, including:
    + Failover control
    + pg_createsubscriber, a utility that creates logical replicas
    from physical standbys
    + pg_upgrade now preserves replication slots on both publishers
    and subscribers
  * New client-side connection option, sslnegotiation=direct, that
    performs a direct TLS handshake to avoid a round-trip
    negotiation.
  * pg_basebackup now supports incremental backup.
  * COPY adds a new option, ON_ERROR ignore, that allows a copy
    operation to continue in the event of an error.
  * https://www.postgresql.org/about/news/p-2936/
  * https://www.postgresql.org/docs/17/release-17.html</changelog>
  <changelog author="Fabian Vogt &lt;fvogt@suse.com&gt;" date="1728302400">- Use cmake(LLVM) &lt; instead of &lt;= to also allow building against
  LLVM 18.1 and newer 18.x versions</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1730721600">- Add postgresql17-jsonb_jsonpath.patch as a temporary build fix.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1731499200">- Upgrade to 17.1:
  * CVE-2024-10976, bsc#1233323: Ensure cached plans are marked as
    dependent on the calling role when RLS applies to a
    non-top-level table reference.
  * CVE-2024-10977, bsc#1233325: Make libpq discard error messages
    received during SSL or GSS protocol negotiation.
  * CVE-2024-10978, bsc#1233326: Fix unintended interactions
    between SET SESSION AUTHORIZATION and SET ROLE
  * CVE-2024-10979, bsc#1233327: Prevent trusted PL/Perl code from
    changing environment variables.
  * obsoletes postgresql17-jsonb_jsonpath.patch
  * https://www.postgresql.org/about/news/p-2955/
  * https://www.postgresql.org/docs/release/17.1/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1732017600">- Upgrade to 17.2:
  * Repair ABI break for extensions that work with struct
    ResultRelInfo.
  * Restore functionality of ALTER {ROLE|DATABASE} SET role.
  * Fix cases where a logical replication slot's restart_lsn could
    go backwards.
  * Avoid deleting still-needed WAL files during pg_rewind.
  * Fix race conditions associated with dropping shared statistics
    entries.
  * Count index scans in contrib/bloom indexes in the statistics
    views, such as the pg_stat_user_indexes.idx_scan counter.
  * Fix crash when checking to see if an index's opclass options
    have changed.
  * Avoid assertion failure caused by disconnected NFA sub-graphs
    in regular expression parsing.
  * https://www.postgresql.org/about/news/p-2965/
  * https://www.postgresql.org/docs/release/17.2/</changelog>
  <changelog author="JS &lt;obs.coke518@passinbox.com&gt;" date="1735214400">- Disable LLVM JIT on loongarch64</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="JS &lt;obs.coke518@passinbox.com&gt;" date="1738152000">- Apply postgresql-tzdata2025a.patch regardless of
  whether LLVM JIT is enabled</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 17.3:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/17.3/
  * https://www.postgresql.org/about/news/-3015/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 17.4:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/17.4/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 17.5:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/17.5/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to Fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Update to 17.6
  * https://www.postgresql.org/about/news/postgresql-176-1610-1514-1419-1322-and-18-beta-3-released-3118/
  * https://www.postgresql.org/docs/release/17.6/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1756036800">- switch library to pg 18</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1756987200">- Sync spec file with version 18.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Update to 17.7:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/17.7/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 17.8:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/17.8/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 17.9 to fix two regressions in 17.8:
  * https://www.postgresql.org/docs/release/17.9/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
</package>
<package pkgid="2126d65d2ec90d52ef3485e02b35b46cce089863b62c0110f5591ca21ce6bcf575501ada5893e911118a39225b2c6a6f3b2cb7b4a3f6815b97cd761ae124a081" name="postgresql17-test" arch="ppc64le">
  <version epoch="0" ver="17.9" rel="55.1"/>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1727352000">- Upgrade to 17.0:
  * New memory management system for VACUUM, which reduces memory
    consumption and can improve overall vacuuming performance.
  * New SQL/JSON capabilities, including constructors, identity
    functions, and the JSON_TABLE() function, which converts JSON
    data into a table representation.
  * Various query performance improvements, including for
    sequential reads using streaming I/O, write throughput under
    high concurrency, and searches over multiple values in a btree
    index.
  * Logical replication enhancements, including:
    + Failover control
    + pg_createsubscriber, a utility that creates logical replicas
    from physical standbys
    + pg_upgrade now preserves replication slots on both publishers
    and subscribers
  * New client-side connection option, sslnegotiation=direct, that
    performs a direct TLS handshake to avoid a round-trip
    negotiation.
  * pg_basebackup now supports incremental backup.
  * COPY adds a new option, ON_ERROR ignore, that allows a copy
    operation to continue in the event of an error.
  * https://www.postgresql.org/about/news/p-2936/
  * https://www.postgresql.org/docs/17/release-17.html</changelog>
  <changelog author="Fabian Vogt &lt;fvogt@suse.com&gt;" date="1728302400">- Use cmake(LLVM) &lt; instead of &lt;= to also allow building against
  LLVM 18.1 and newer 18.x versions</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1730721600">- Add postgresql17-jsonb_jsonpath.patch as a temporary build fix.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1731499200">- Upgrade to 17.1:
  * CVE-2024-10976, bsc#1233323: Ensure cached plans are marked as
    dependent on the calling role when RLS applies to a
    non-top-level table reference.
  * CVE-2024-10977, bsc#1233325: Make libpq discard error messages
    received during SSL or GSS protocol negotiation.
  * CVE-2024-10978, bsc#1233326: Fix unintended interactions
    between SET SESSION AUTHORIZATION and SET ROLE
  * CVE-2024-10979, bsc#1233327: Prevent trusted PL/Perl code from
    changing environment variables.
  * obsoletes postgresql17-jsonb_jsonpath.patch
  * https://www.postgresql.org/about/news/p-2955/
  * https://www.postgresql.org/docs/release/17.1/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1732017600">- Upgrade to 17.2:
  * Repair ABI break for extensions that work with struct
    ResultRelInfo.
  * Restore functionality of ALTER {ROLE|DATABASE} SET role.
  * Fix cases where a logical replication slot's restart_lsn could
    go backwards.
  * Avoid deleting still-needed WAL files during pg_rewind.
  * Fix race conditions associated with dropping shared statistics
    entries.
  * Count index scans in contrib/bloom indexes in the statistics
    views, such as the pg_stat_user_indexes.idx_scan counter.
  * Fix crash when checking to see if an index's opclass options
    have changed.
  * Avoid assertion failure caused by disconnected NFA sub-graphs
    in regular expression parsing.
  * https://www.postgresql.org/about/news/p-2965/
  * https://www.postgresql.org/docs/release/17.2/</changelog>
  <changelog author="JS &lt;obs.coke518@passinbox.com&gt;" date="1735214400">- Disable LLVM JIT on loongarch64</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="JS &lt;obs.coke518@passinbox.com&gt;" date="1738152000">- Apply postgresql-tzdata2025a.patch regardless of
  whether LLVM JIT is enabled</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 17.3:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/17.3/
  * https://www.postgresql.org/about/news/-3015/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 17.4:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/17.4/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 17.5:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/17.5/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to Fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Update to 17.6
  * https://www.postgresql.org/about/news/postgresql-176-1610-1514-1419-1322-and-18-beta-3-released-3118/
  * https://www.postgresql.org/docs/release/17.6/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1756036800">- switch library to pg 18</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1756987200">- Sync spec file with version 18.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Update to 17.7:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/17.7/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 17.8:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/17.8/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 17.9 to fix two regressions in 17.8:
  * https://www.postgresql.org/docs/release/17.9/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
</package>
<package pkgid="f74367de2a86c05954ddf2b68f293eb4f378d40be1c365e71344c34cb4dd6f34a443a9e66c6746f3bc5f12ffb240503e4299c3ca6104285fdc14445c18ba51b0" name="postgresql18" arch="s390x">
  <version epoch="0" ver="18.3" rel="2.3"/>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="JS &lt;obs.coke518@passinbox.com&gt;" date="1738152000">- Apply postgresql-tzdata2025a.patch regardless of
  whether LLVM JIT is enabled</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 17.3:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/17.3/
  * https://www.postgresql.org/about/news/-3015/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 17.4:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/17.4/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 17.5:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/17.5/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to Fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1746792001">- Fork package for postgresql 18
  https://www.postgresql.org/about/news/p-3070/</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1753272000">- Update to 18~beta2
  https://www.postgresql.org/about/news/p-3103/</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Update to 18~beta3
  * https://www.postgresql.org/about/news/p-3118/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755518400">- enable liburing and libnuma support
- prepare oauth support. but it creates broken symlinks at the
  moment</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755518401">- In the symlinking loop for *.so files only handle symlinks and
  not also files.
  This allows us to enable oauth support</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755604800">- move libpq-oauth into the libpq5  package. it is a plugin that
  will be loaded via dlopen() if libpq encounters an oauth workflow
  during a connection.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1756987200">- Update to 18 RC1.
  * https://www.postgresql.org/about/news/p-3130/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1758628800">- Update to 18.0.
  * https://www.postgresql.org/about/news/p-3142/
  * https://www.postgresql.org/docs/18/release-18.html</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1758801600">- pg_config --libs returns -lnuma so we need to require it.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Update to 18.1:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/18.1/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 18.2:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/18.2/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * bsc#1258012, CVE-2026-2007: Harden contrib/pg_trgm against
    changes in string lowercasing behavior.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 18.3 to fix two regressions in 18.2:
  * https://www.postgresql.org/docs/release/18.3/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
</package>
<package pkgid="5eb3e1da3cafce8a9c9e5dfdbb3118b801e4d50100cd52a6a1be412cb6b65d5364a78cd3d89528e7619d3f34765ed35f9700921928d3a4c3fee8ec1852e0f131" name="postgresql18" arch="src">
  <version epoch="0" ver="18.3" rel="2.3"/>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="JS &lt;obs.coke518@passinbox.com&gt;" date="1738152000">- Apply postgresql-tzdata2025a.patch regardless of
  whether LLVM JIT is enabled</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 17.3:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/17.3/
  * https://www.postgresql.org/about/news/-3015/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 17.4:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/17.4/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 17.5:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/17.5/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to Fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1746792001">- Fork package for postgresql 18
  https://www.postgresql.org/about/news/p-3070/</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1753272000">- Update to 18~beta2
  https://www.postgresql.org/about/news/p-3103/</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Update to 18~beta3
  * https://www.postgresql.org/about/news/p-3118/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755518400">- enable liburing and libnuma support
- prepare oauth support. but it creates broken symlinks at the
  moment</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755518401">- In the symlinking loop for *.so files only handle symlinks and
  not also files.
  This allows us to enable oauth support</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755604800">- move libpq-oauth into the libpq5  package. it is a plugin that
  will be loaded via dlopen() if libpq encounters an oauth workflow
  during a connection.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1756987200">- Update to 18 RC1.
  * https://www.postgresql.org/about/news/p-3130/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1758628800">- Update to 18.0.
  * https://www.postgresql.org/about/news/p-3142/
  * https://www.postgresql.org/docs/18/release-18.html</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1758801600">- pg_config --libs returns -lnuma so we need to require it.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Update to 18.1:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/18.1/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 18.2:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/18.2/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * bsc#1258012, CVE-2026-2007: Harden contrib/pg_trgm against
    changes in string lowercasing behavior.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 18.3 to fix two regressions in 18.2:
  * https://www.postgresql.org/docs/release/18.3/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
</package>
<package pkgid="e2da2e81b2e21486c7fb6f32c78d6931e7b0e2b8bf2260bcdbd4600b51b95854fa221643d9a6bbc80af5f5906a8cdf7b388b30725863dbe2ca0848aecf9c1126" name="postgresql18" arch="aarch64">
  <version epoch="0" ver="18.3" rel="3.1"/>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="JS &lt;obs.coke518@passinbox.com&gt;" date="1738152000">- Apply postgresql-tzdata2025a.patch regardless of
  whether LLVM JIT is enabled</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 17.3:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/17.3/
  * https://www.postgresql.org/about/news/-3015/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 17.4:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/17.4/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 17.5:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/17.5/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to Fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1746792001">- Fork package for postgresql 18
  https://www.postgresql.org/about/news/p-3070/</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1753272000">- Update to 18~beta2
  https://www.postgresql.org/about/news/p-3103/</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Update to 18~beta3
  * https://www.postgresql.org/about/news/p-3118/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755518400">- enable liburing and libnuma support
- prepare oauth support. but it creates broken symlinks at the
  moment</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755518401">- In the symlinking loop for *.so files only handle symlinks and
  not also files.
  This allows us to enable oauth support</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755604800">- move libpq-oauth into the libpq5  package. it is a plugin that
  will be loaded via dlopen() if libpq encounters an oauth workflow
  during a connection.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1756987200">- Update to 18 RC1.
  * https://www.postgresql.org/about/news/p-3130/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1758628800">- Update to 18.0.
  * https://www.postgresql.org/about/news/p-3142/
  * https://www.postgresql.org/docs/18/release-18.html</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1758801600">- pg_config --libs returns -lnuma so we need to require it.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Update to 18.1:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/18.1/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 18.2:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/18.2/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * bsc#1258012, CVE-2026-2007: Harden contrib/pg_trgm against
    changes in string lowercasing behavior.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 18.3 to fix two regressions in 18.2:
  * https://www.postgresql.org/docs/release/18.3/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
</package>
<package pkgid="dc73652b78755f09144409f75c5a71fc17bf167c48888bf77aac0deee8c2ded74b23c144aac8f2da9a4bf89473f4a1d56553272e61c04142a0b45a62e0411dea" name="postgresql18" arch="ppc64le">
  <version epoch="0" ver="18.3" rel="3.1"/>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="JS &lt;obs.coke518@passinbox.com&gt;" date="1738152000">- Apply postgresql-tzdata2025a.patch regardless of
  whether LLVM JIT is enabled</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 17.3:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/17.3/
  * https://www.postgresql.org/about/news/-3015/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 17.4:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/17.4/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 17.5:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/17.5/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to Fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1746792001">- Fork package for postgresql 18
  https://www.postgresql.org/about/news/p-3070/</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1753272000">- Update to 18~beta2
  https://www.postgresql.org/about/news/p-3103/</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Update to 18~beta3
  * https://www.postgresql.org/about/news/p-3118/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755518400">- enable liburing and libnuma support
- prepare oauth support. but it creates broken symlinks at the
  moment</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755518401">- In the symlinking loop for *.so files only handle symlinks and
  not also files.
  This allows us to enable oauth support</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755604800">- move libpq-oauth into the libpq5  package. it is a plugin that
  will be loaded via dlopen() if libpq encounters an oauth workflow
  during a connection.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1756987200">- Update to 18 RC1.
  * https://www.postgresql.org/about/news/p-3130/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1758628800">- Update to 18.0.
  * https://www.postgresql.org/about/news/p-3142/
  * https://www.postgresql.org/docs/18/release-18.html</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1758801600">- pg_config --libs returns -lnuma so we need to require it.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Update to 18.1:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/18.1/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 18.2:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/18.2/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * bsc#1258012, CVE-2026-2007: Harden contrib/pg_trgm against
    changes in string lowercasing behavior.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 18.3 to fix two regressions in 18.2:
  * https://www.postgresql.org/docs/release/18.3/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
</package>
<package pkgid="4b17c4626c5f43ad324a3701a965212aeb3db760b9c0861b3bb3d2e98750b7de0ae1e51902d4d425f2a5e9c504331423b617a028c3302ea12f25b12452fc0536" name="postgresql18" arch="src">
  <version epoch="0" ver="18.3" rel="3.1"/>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="JS &lt;obs.coke518@passinbox.com&gt;" date="1738152000">- Apply postgresql-tzdata2025a.patch regardless of
  whether LLVM JIT is enabled</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 17.3:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/17.3/
  * https://www.postgresql.org/about/news/-3015/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 17.4:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/17.4/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 17.5:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/17.5/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to Fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1746792001">- Fork package for postgresql 18
  https://www.postgresql.org/about/news/p-3070/</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1753272000">- Update to 18~beta2
  https://www.postgresql.org/about/news/p-3103/</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Update to 18~beta3
  * https://www.postgresql.org/about/news/p-3118/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755518400">- enable liburing and libnuma support
- prepare oauth support. but it creates broken symlinks at the
  moment</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755518401">- In the symlinking loop for *.so files only handle symlinks and
  not also files.
  This allows us to enable oauth support</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755604800">- move libpq-oauth into the libpq5  package. it is a plugin that
  will be loaded via dlopen() if libpq encounters an oauth workflow
  during a connection.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1756987200">- Update to 18 RC1.
  * https://www.postgresql.org/about/news/p-3130/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1758628800">- Update to 18.0.
  * https://www.postgresql.org/about/news/p-3142/
  * https://www.postgresql.org/docs/18/release-18.html</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1758801600">- pg_config --libs returns -lnuma so we need to require it.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Update to 18.1:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/18.1/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 18.2:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/18.2/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * bsc#1258012, CVE-2026-2007: Harden contrib/pg_trgm against
    changes in string lowercasing behavior.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 18.3 to fix two regressions in 18.2:
  * https://www.postgresql.org/docs/release/18.3/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
</package>
<package pkgid="c8e4efdb961f5e9af85bd03ef2d76410fe742c7e4df437f8f0779e7c94d0a13b68400226907a7b191ed1fc654bf190cfe4589d575cf83cf5b6e459e4886d0bc7" name="postgresql18" arch="src">
  <version epoch="0" ver="18.4" rel="18.3"/>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 17.4:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/17.4/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 17.5:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/17.5/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to Fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1746792001">- Fork package for postgresql 18
  https://www.postgresql.org/about/news/p-3070/</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1753272000">- Update to 18~beta2
  https://www.postgresql.org/about/news/p-3103/</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Update to 18~beta3
  * https://www.postgresql.org/about/news/p-3118/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755518400">- enable liburing and libnuma support
- prepare oauth support. but it creates broken symlinks at the
  moment</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755518401">- In the symlinking loop for *.so files only handle symlinks and
  not also files.
  This allows us to enable oauth support</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755604800">- move libpq-oauth into the libpq5  package. it is a plugin that
  will be loaded via dlopen() if libpq encounters an oauth workflow
  during a connection.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1756987200">- Update to 18 RC1.
  * https://www.postgresql.org/about/news/p-3130/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1758628800">- Update to 18.0.
  * https://www.postgresql.org/about/news/p-3142/
  * https://www.postgresql.org/docs/18/release-18.html</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1758801600">- pg_config --libs returns -lnuma so we need to require it.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Update to 18.1:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/18.1/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 18.2:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/18.2/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * bsc#1258012, CVE-2026-2007: Harden contrib/pg_trgm against
    changes in string lowercasing behavior.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 18.3 to fix two regressions in 18.2:
  * https://www.postgresql.org/docs/release/18.3/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1774526400">- Get rid of update-alternatives for openSUSE/SLE 16.0 and newer
  to support immutable systems and transactional updates.
  (jsc#PED-14820)</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1777550400">- bsc#1263804: After dropping update-alternatives we have to
  package /usr/bin/pg_config as an actual symlink, not %ghost.
- Fix spelling of build conditionals.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1778673600">- Update to version 18.4:
  * bsc#1265172, CVE-2026-6472: ensure the user has CREATE
    privilege on the schema specified
  * bsc#1265173, CVE-2026-6473: integer overflows in
    memory-allocation calculations
  * bsc#1265174, CVE-2026-6474: Guard against malicious time zone
    names
  * bsc#1265175, CVE-2026-6475: Prevent path traversal in
    pg_basebackup and pg_rewind
  * bsc#1265176, CVE-2026-6476: Properly quote subscription names
    in pg_createsubscriber
  * bsc#1265177, CVE-2026-6477: Mark PQfn() as unsafe, and avoid
    using it within libpq
  * bsc#1265178, CVE-2026-6478: Use timing-safe string comparisons
    in authentication code
  * bsc#1265179, CVE-2026-6479: Prevent unbounded recursion while
    processing startup packets
  * bsc#1265180, CVE-2026-6575: Detect faulty input when restoring
    attribute MCV statistics
  * bsc#1265181, CVE-2026-6637: Prevent SQL injection and buffer
    overruns in contrib/spi
  * bsc#1265182, CVE-2026-6638: Properly quote object names in
    logical replication origin checks
  * https://www.postgresql.org/docs/release/18.4/</changelog>
</package>
<package pkgid="5ce65581038258e55169de203fe3831518aa335d2fd995d0dcef9d5cdb21d91f8d1ff1417b81226c63c8b1797251d6b80a405313ac3b1d0a68c93a3e16da2347" name="postgresql18" arch="x86_64">
  <version epoch="0" ver="18.4" rel="18.3"/>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 17.4:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/17.4/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 17.5:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/17.5/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to Fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1746792001">- Fork package for postgresql 18
  https://www.postgresql.org/about/news/p-3070/</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1753272000">- Update to 18~beta2
  https://www.postgresql.org/about/news/p-3103/</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Update to 18~beta3
  * https://www.postgresql.org/about/news/p-3118/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755518400">- enable liburing and libnuma support
- prepare oauth support. but it creates broken symlinks at the
  moment</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755518401">- In the symlinking loop for *.so files only handle symlinks and
  not also files.
  This allows us to enable oauth support</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755604800">- move libpq-oauth into the libpq5  package. it is a plugin that
  will be loaded via dlopen() if libpq encounters an oauth workflow
  during a connection.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1756987200">- Update to 18 RC1.
  * https://www.postgresql.org/about/news/p-3130/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1758628800">- Update to 18.0.
  * https://www.postgresql.org/about/news/p-3142/
  * https://www.postgresql.org/docs/18/release-18.html</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1758801600">- pg_config --libs returns -lnuma so we need to require it.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Update to 18.1:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/18.1/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 18.2:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/18.2/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * bsc#1258012, CVE-2026-2007: Harden contrib/pg_trgm against
    changes in string lowercasing behavior.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 18.3 to fix two regressions in 18.2:
  * https://www.postgresql.org/docs/release/18.3/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1774526400">- Get rid of update-alternatives for openSUSE/SLE 16.0 and newer
  to support immutable systems and transactional updates.
  (jsc#PED-14820)</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1777550400">- bsc#1263804: After dropping update-alternatives we have to
  package /usr/bin/pg_config as an actual symlink, not %ghost.
- Fix spelling of build conditionals.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1778673600">- Update to version 18.4:
  * bsc#1265172, CVE-2026-6472: ensure the user has CREATE
    privilege on the schema specified
  * bsc#1265173, CVE-2026-6473: integer overflows in
    memory-allocation calculations
  * bsc#1265174, CVE-2026-6474: Guard against malicious time zone
    names
  * bsc#1265175, CVE-2026-6475: Prevent path traversal in
    pg_basebackup and pg_rewind
  * bsc#1265176, CVE-2026-6476: Properly quote subscription names
    in pg_createsubscriber
  * bsc#1265177, CVE-2026-6477: Mark PQfn() as unsafe, and avoid
    using it within libpq
  * bsc#1265178, CVE-2026-6478: Use timing-safe string comparisons
    in authentication code
  * bsc#1265179, CVE-2026-6479: Prevent unbounded recursion while
    processing startup packets
  * bsc#1265180, CVE-2026-6575: Detect faulty input when restoring
    attribute MCV statistics
  * bsc#1265181, CVE-2026-6637: Prevent SQL injection and buffer
    overruns in contrib/spi
  * bsc#1265182, CVE-2026-6638: Properly quote object names in
    logical replication origin checks
  * https://www.postgresql.org/docs/release/18.4/</changelog>
</package>
<package pkgid="1d769d653c01de8a229211d74a1edefc2dcc00b07a9f078680652d7314ace6c9d9952a07f096db06a379db5a59bc3ae281da18c85fa950512b4cd53421ec91af" name="postgresql18-contrib" arch="s390x">
  <version epoch="0" ver="18.3" rel="2.3"/>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="JS &lt;obs.coke518@passinbox.com&gt;" date="1738152000">- Apply postgresql-tzdata2025a.patch regardless of
  whether LLVM JIT is enabled</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 17.3:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/17.3/
  * https://www.postgresql.org/about/news/-3015/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 17.4:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/17.4/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 17.5:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/17.5/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to Fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1746792001">- Fork package for postgresql 18
  https://www.postgresql.org/about/news/p-3070/</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1753272000">- Update to 18~beta2
  https://www.postgresql.org/about/news/p-3103/</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Update to 18~beta3
  * https://www.postgresql.org/about/news/p-3118/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755518400">- enable liburing and libnuma support
- prepare oauth support. but it creates broken symlinks at the
  moment</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755518401">- In the symlinking loop for *.so files only handle symlinks and
  not also files.
  This allows us to enable oauth support</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755604800">- move libpq-oauth into the libpq5  package. it is a plugin that
  will be loaded via dlopen() if libpq encounters an oauth workflow
  during a connection.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1756987200">- Update to 18 RC1.
  * https://www.postgresql.org/about/news/p-3130/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1758628800">- Update to 18.0.
  * https://www.postgresql.org/about/news/p-3142/
  * https://www.postgresql.org/docs/18/release-18.html</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1758801600">- pg_config --libs returns -lnuma so we need to require it.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Update to 18.1:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/18.1/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 18.2:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/18.2/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * bsc#1258012, CVE-2026-2007: Harden contrib/pg_trgm against
    changes in string lowercasing behavior.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 18.3 to fix two regressions in 18.2:
  * https://www.postgresql.org/docs/release/18.3/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
</package>
<package pkgid="476f037e3ea408ee0ecbc4c9ebbdc77f4693bab5f73180b95ee06323f86a9da58b17d073eff811f0b16f368fc18a251cd0f29850fc205269fafdf81298aff640" name="postgresql18-contrib" arch="aarch64">
  <version epoch="0" ver="18.3" rel="3.1"/>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="JS &lt;obs.coke518@passinbox.com&gt;" date="1738152000">- Apply postgresql-tzdata2025a.patch regardless of
  whether LLVM JIT is enabled</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 17.3:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/17.3/
  * https://www.postgresql.org/about/news/-3015/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 17.4:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/17.4/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 17.5:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/17.5/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to Fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1746792001">- Fork package for postgresql 18
  https://www.postgresql.org/about/news/p-3070/</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1753272000">- Update to 18~beta2
  https://www.postgresql.org/about/news/p-3103/</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Update to 18~beta3
  * https://www.postgresql.org/about/news/p-3118/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755518400">- enable liburing and libnuma support
- prepare oauth support. but it creates broken symlinks at the
  moment</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755518401">- In the symlinking loop for *.so files only handle symlinks and
  not also files.
  This allows us to enable oauth support</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755604800">- move libpq-oauth into the libpq5  package. it is a plugin that
  will be loaded via dlopen() if libpq encounters an oauth workflow
  during a connection.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1756987200">- Update to 18 RC1.
  * https://www.postgresql.org/about/news/p-3130/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1758628800">- Update to 18.0.
  * https://www.postgresql.org/about/news/p-3142/
  * https://www.postgresql.org/docs/18/release-18.html</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1758801600">- pg_config --libs returns -lnuma so we need to require it.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Update to 18.1:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/18.1/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 18.2:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/18.2/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * bsc#1258012, CVE-2026-2007: Harden contrib/pg_trgm against
    changes in string lowercasing behavior.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 18.3 to fix two regressions in 18.2:
  * https://www.postgresql.org/docs/release/18.3/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
</package>
<package pkgid="c5ff9d19e87357ac54b25acee8d1092a3ee847d16f2c3aab6b54bd598abccc0d32e3e195d01b302a9313e92c8271e296203a1994cd80838c35df143d64037e39" name="postgresql18-contrib" arch="ppc64le">
  <version epoch="0" ver="18.3" rel="3.1"/>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="JS &lt;obs.coke518@passinbox.com&gt;" date="1738152000">- Apply postgresql-tzdata2025a.patch regardless of
  whether LLVM JIT is enabled</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 17.3:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/17.3/
  * https://www.postgresql.org/about/news/-3015/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 17.4:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/17.4/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 17.5:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/17.5/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to Fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1746792001">- Fork package for postgresql 18
  https://www.postgresql.org/about/news/p-3070/</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1753272000">- Update to 18~beta2
  https://www.postgresql.org/about/news/p-3103/</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Update to 18~beta3
  * https://www.postgresql.org/about/news/p-3118/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755518400">- enable liburing and libnuma support
- prepare oauth support. but it creates broken symlinks at the
  moment</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755518401">- In the symlinking loop for *.so files only handle symlinks and
  not also files.
  This allows us to enable oauth support</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755604800">- move libpq-oauth into the libpq5  package. it is a plugin that
  will be loaded via dlopen() if libpq encounters an oauth workflow
  during a connection.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1756987200">- Update to 18 RC1.
  * https://www.postgresql.org/about/news/p-3130/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1758628800">- Update to 18.0.
  * https://www.postgresql.org/about/news/p-3142/
  * https://www.postgresql.org/docs/18/release-18.html</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1758801600">- pg_config --libs returns -lnuma so we need to require it.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Update to 18.1:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/18.1/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 18.2:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/18.2/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * bsc#1258012, CVE-2026-2007: Harden contrib/pg_trgm against
    changes in string lowercasing behavior.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 18.3 to fix two regressions in 18.2:
  * https://www.postgresql.org/docs/release/18.3/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
</package>
<package pkgid="b6da6c540338a45e60c425f5f4218f89bf4a681a4623795fa9e0eb64ab5cdca54d566d0a8ac84a4dda0b150af24d4d0d939fa862da1feacc614d54518b9e5f6a" name="postgresql18-contrib" arch="x86_64">
  <version epoch="0" ver="18.4" rel="18.3"/>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 17.4:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/17.4/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 17.5:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/17.5/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to Fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1746792001">- Fork package for postgresql 18
  https://www.postgresql.org/about/news/p-3070/</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1753272000">- Update to 18~beta2
  https://www.postgresql.org/about/news/p-3103/</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Update to 18~beta3
  * https://www.postgresql.org/about/news/p-3118/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755518400">- enable liburing and libnuma support
- prepare oauth support. but it creates broken symlinks at the
  moment</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755518401">- In the symlinking loop for *.so files only handle symlinks and
  not also files.
  This allows us to enable oauth support</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755604800">- move libpq-oauth into the libpq5  package. it is a plugin that
  will be loaded via dlopen() if libpq encounters an oauth workflow
  during a connection.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1756987200">- Update to 18 RC1.
  * https://www.postgresql.org/about/news/p-3130/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1758628800">- Update to 18.0.
  * https://www.postgresql.org/about/news/p-3142/
  * https://www.postgresql.org/docs/18/release-18.html</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1758801600">- pg_config --libs returns -lnuma so we need to require it.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Update to 18.1:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/18.1/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 18.2:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/18.2/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * bsc#1258012, CVE-2026-2007: Harden contrib/pg_trgm against
    changes in string lowercasing behavior.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 18.3 to fix two regressions in 18.2:
  * https://www.postgresql.org/docs/release/18.3/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1774526400">- Get rid of update-alternatives for openSUSE/SLE 16.0 and newer
  to support immutable systems and transactional updates.
  (jsc#PED-14820)</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1777550400">- bsc#1263804: After dropping update-alternatives we have to
  package /usr/bin/pg_config as an actual symlink, not %ghost.
- Fix spelling of build conditionals.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1778673600">- Update to version 18.4:
  * bsc#1265172, CVE-2026-6472: ensure the user has CREATE
    privilege on the schema specified
  * bsc#1265173, CVE-2026-6473: integer overflows in
    memory-allocation calculations
  * bsc#1265174, CVE-2026-6474: Guard against malicious time zone
    names
  * bsc#1265175, CVE-2026-6475: Prevent path traversal in
    pg_basebackup and pg_rewind
  * bsc#1265176, CVE-2026-6476: Properly quote subscription names
    in pg_createsubscriber
  * bsc#1265177, CVE-2026-6477: Mark PQfn() as unsafe, and avoid
    using it within libpq
  * bsc#1265178, CVE-2026-6478: Use timing-safe string comparisons
    in authentication code
  * bsc#1265179, CVE-2026-6479: Prevent unbounded recursion while
    processing startup packets
  * bsc#1265180, CVE-2026-6575: Detect faulty input when restoring
    attribute MCV statistics
  * bsc#1265181, CVE-2026-6637: Prevent SQL injection and buffer
    overruns in contrib/spi
  * bsc#1265182, CVE-2026-6638: Properly quote object names in
    logical replication origin checks
  * https://www.postgresql.org/docs/release/18.4/</changelog>
</package>
<package pkgid="03026507e0a3279503a190f771a6ba5e6e1b64db53a215d9502933ee558fd995cfef7da1cdda04789c9d7b9a3e57b223426ce1189e0920f6f3c420ccd63fea0a" name="postgresql18-devel" arch="s390x">
  <version epoch="0" ver="18.3" rel="2.3"/>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="JS &lt;obs.coke518@passinbox.com&gt;" date="1738152000">- Apply postgresql-tzdata2025a.patch regardless of
  whether LLVM JIT is enabled</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 17.3:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/17.3/
  * https://www.postgresql.org/about/news/-3015/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 17.4:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/17.4/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 17.5:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/17.5/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to Fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1746792001">- Fork package for postgresql 18
  https://www.postgresql.org/about/news/p-3070/</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1753272000">- Update to 18~beta2
  https://www.postgresql.org/about/news/p-3103/</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Update to 18~beta3
  * https://www.postgresql.org/about/news/p-3118/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755518400">- enable liburing and libnuma support
- prepare oauth support. but it creates broken symlinks at the
  moment</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755518401">- In the symlinking loop for *.so files only handle symlinks and
  not also files.
  This allows us to enable oauth support</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755604800">- move libpq-oauth into the libpq5  package. it is a plugin that
  will be loaded via dlopen() if libpq encounters an oauth workflow
  during a connection.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1756987200">- Update to 18 RC1.
  * https://www.postgresql.org/about/news/p-3130/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1758628800">- Update to 18.0.
  * https://www.postgresql.org/about/news/p-3142/
  * https://www.postgresql.org/docs/18/release-18.html</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1758801600">- pg_config --libs returns -lnuma so we need to require it.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Update to 18.1:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/18.1/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 18.2:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/18.2/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * bsc#1258012, CVE-2026-2007: Harden contrib/pg_trgm against
    changes in string lowercasing behavior.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 18.3 to fix two regressions in 18.2:
  * https://www.postgresql.org/docs/release/18.3/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
</package>
<package pkgid="fea8dbca0a913a9497421a24a0e9119e623ba604b41dacfde5f563a14c56f6a33bf38b1eae0153f19847b0839acbc44e570c5a8bbac2c733d39bb2ef49a1697e" name="postgresql18-devel" arch="aarch64">
  <version epoch="0" ver="18.3" rel="3.1"/>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="JS &lt;obs.coke518@passinbox.com&gt;" date="1738152000">- Apply postgresql-tzdata2025a.patch regardless of
  whether LLVM JIT is enabled</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 17.3:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/17.3/
  * https://www.postgresql.org/about/news/-3015/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 17.4:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/17.4/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 17.5:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/17.5/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to Fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1746792001">- Fork package for postgresql 18
  https://www.postgresql.org/about/news/p-3070/</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1753272000">- Update to 18~beta2
  https://www.postgresql.org/about/news/p-3103/</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Update to 18~beta3
  * https://www.postgresql.org/about/news/p-3118/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755518400">- enable liburing and libnuma support
- prepare oauth support. but it creates broken symlinks at the
  moment</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755518401">- In the symlinking loop for *.so files only handle symlinks and
  not also files.
  This allows us to enable oauth support</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755604800">- move libpq-oauth into the libpq5  package. it is a plugin that
  will be loaded via dlopen() if libpq encounters an oauth workflow
  during a connection.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1756987200">- Update to 18 RC1.
  * https://www.postgresql.org/about/news/p-3130/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1758628800">- Update to 18.0.
  * https://www.postgresql.org/about/news/p-3142/
  * https://www.postgresql.org/docs/18/release-18.html</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1758801600">- pg_config --libs returns -lnuma so we need to require it.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Update to 18.1:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/18.1/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 18.2:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/18.2/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * bsc#1258012, CVE-2026-2007: Harden contrib/pg_trgm against
    changes in string lowercasing behavior.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 18.3 to fix two regressions in 18.2:
  * https://www.postgresql.org/docs/release/18.3/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
</package>
<package pkgid="95710baaca2f37bd774025b465269dd6110b01ae4179faf8ec88dc10f68456161f57600f8050f1d73419d99cddfd9893cee532c1285140d3e9f3fb38a5816373" name="postgresql18-devel" arch="ppc64le">
  <version epoch="0" ver="18.3" rel="3.1"/>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="JS &lt;obs.coke518@passinbox.com&gt;" date="1738152000">- Apply postgresql-tzdata2025a.patch regardless of
  whether LLVM JIT is enabled</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 17.3:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/17.3/
  * https://www.postgresql.org/about/news/-3015/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 17.4:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/17.4/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 17.5:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/17.5/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to Fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1746792001">- Fork package for postgresql 18
  https://www.postgresql.org/about/news/p-3070/</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1753272000">- Update to 18~beta2
  https://www.postgresql.org/about/news/p-3103/</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Update to 18~beta3
  * https://www.postgresql.org/about/news/p-3118/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755518400">- enable liburing and libnuma support
- prepare oauth support. but it creates broken symlinks at the
  moment</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755518401">- In the symlinking loop for *.so files only handle symlinks and
  not also files.
  This allows us to enable oauth support</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755604800">- move libpq-oauth into the libpq5  package. it is a plugin that
  will be loaded via dlopen() if libpq encounters an oauth workflow
  during a connection.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1756987200">- Update to 18 RC1.
  * https://www.postgresql.org/about/news/p-3130/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1758628800">- Update to 18.0.
  * https://www.postgresql.org/about/news/p-3142/
  * https://www.postgresql.org/docs/18/release-18.html</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1758801600">- pg_config --libs returns -lnuma so we need to require it.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Update to 18.1:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/18.1/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 18.2:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/18.2/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * bsc#1258012, CVE-2026-2007: Harden contrib/pg_trgm against
    changes in string lowercasing behavior.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 18.3 to fix two regressions in 18.2:
  * https://www.postgresql.org/docs/release/18.3/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
</package>
<package pkgid="29a13f826087066d275df6716b7c0157b0e277607b3bc039747d793bd499a2d9f48d79ccb9d0db69ff0283662a239007da649c109ab14a4d53ba414b71810341" name="postgresql18-devel" arch="x86_64">
  <version epoch="0" ver="18.4" rel="18.3"/>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 17.4:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/17.4/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 17.5:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/17.5/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to Fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1746792001">- Fork package for postgresql 18
  https://www.postgresql.org/about/news/p-3070/</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1753272000">- Update to 18~beta2
  https://www.postgresql.org/about/news/p-3103/</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Update to 18~beta3
  * https://www.postgresql.org/about/news/p-3118/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755518400">- enable liburing and libnuma support
- prepare oauth support. but it creates broken symlinks at the
  moment</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755518401">- In the symlinking loop for *.so files only handle symlinks and
  not also files.
  This allows us to enable oauth support</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755604800">- move libpq-oauth into the libpq5  package. it is a plugin that
  will be loaded via dlopen() if libpq encounters an oauth workflow
  during a connection.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1756987200">- Update to 18 RC1.
  * https://www.postgresql.org/about/news/p-3130/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1758628800">- Update to 18.0.
  * https://www.postgresql.org/about/news/p-3142/
  * https://www.postgresql.org/docs/18/release-18.html</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1758801600">- pg_config --libs returns -lnuma so we need to require it.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Update to 18.1:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/18.1/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 18.2:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/18.2/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * bsc#1258012, CVE-2026-2007: Harden contrib/pg_trgm against
    changes in string lowercasing behavior.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 18.3 to fix two regressions in 18.2:
  * https://www.postgresql.org/docs/release/18.3/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1774526400">- Get rid of update-alternatives for openSUSE/SLE 16.0 and newer
  to support immutable systems and transactional updates.
  (jsc#PED-14820)</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1777550400">- bsc#1263804: After dropping update-alternatives we have to
  package /usr/bin/pg_config as an actual symlink, not %ghost.
- Fix spelling of build conditionals.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1778673600">- Update to version 18.4:
  * bsc#1265172, CVE-2026-6472: ensure the user has CREATE
    privilege on the schema specified
  * bsc#1265173, CVE-2026-6473: integer overflows in
    memory-allocation calculations
  * bsc#1265174, CVE-2026-6474: Guard against malicious time zone
    names
  * bsc#1265175, CVE-2026-6475: Prevent path traversal in
    pg_basebackup and pg_rewind
  * bsc#1265176, CVE-2026-6476: Properly quote subscription names
    in pg_createsubscriber
  * bsc#1265177, CVE-2026-6477: Mark PQfn() as unsafe, and avoid
    using it within libpq
  * bsc#1265178, CVE-2026-6478: Use timing-safe string comparisons
    in authentication code
  * bsc#1265179, CVE-2026-6479: Prevent unbounded recursion while
    processing startup packets
  * bsc#1265180, CVE-2026-6575: Detect faulty input when restoring
    attribute MCV statistics
  * bsc#1265181, CVE-2026-6637: Prevent SQL injection and buffer
    overruns in contrib/spi
  * bsc#1265182, CVE-2026-6638: Properly quote object names in
    logical replication origin checks
  * https://www.postgresql.org/docs/release/18.4/</changelog>
</package>
<package pkgid="a1056931ef659912469ef94a1bdcf6c9887a378399299e7a80f76120cf0cce7866ec0a6478ab0bf5c980bf6b0ca26f085d34661fe493517cc379f03a4dd35d7e" name="postgresql18-devel-mini" arch="s390x">
  <version epoch="0" ver="18.3" rel="2.1"/>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="JS &lt;obs.coke518@passinbox.com&gt;" date="1738152000">- Apply postgresql-tzdata2025a.patch regardless of
  whether LLVM JIT is enabled</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 17.3:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/17.3/
  * https://www.postgresql.org/about/news/-3015/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 17.4:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/17.4/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 17.5:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/17.5/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to Fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1746792001">- Fork package for postgresql 18
  https://www.postgresql.org/about/news/p-3070/</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1753272000">- Update to 18~beta2
  https://www.postgresql.org/about/news/p-3103/</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Update to 18~beta3
  * https://www.postgresql.org/about/news/p-3118/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755518400">- enable liburing and libnuma support
- prepare oauth support. but it creates broken symlinks at the
  moment</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755518401">- In the symlinking loop for *.so files only handle symlinks and
  not also files.
  This allows us to enable oauth support</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755604800">- move libpq-oauth into the libpq5  package. it is a plugin that
  will be loaded via dlopen() if libpq encounters an oauth workflow
  during a connection.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1756987200">- Update to 18 RC1.
  * https://www.postgresql.org/about/news/p-3130/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1758628800">- Update to 18.0.
  * https://www.postgresql.org/about/news/p-3142/
  * https://www.postgresql.org/docs/18/release-18.html</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1758801600">- pg_config --libs returns -lnuma so we need to require it.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Update to 18.1:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/18.1/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 18.2:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/18.2/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * bsc#1258012, CVE-2026-2007: Harden contrib/pg_trgm against
    changes in string lowercasing behavior.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 18.3 to fix two regressions in 18.2:
  * https://www.postgresql.org/docs/release/18.3/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
</package>
<package pkgid="aa2bd04b164ca359ee610d66b135687b0d393b716e16cf48f3eea313bf4b92e7098ebf978de26f2a574bb797b63f16091dfbf209ab409f843a050796effc7be6" name="postgresql18-devel-mini" arch="aarch64">
  <version epoch="0" ver="18.3" rel="3.1"/>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="JS &lt;obs.coke518@passinbox.com&gt;" date="1738152000">- Apply postgresql-tzdata2025a.patch regardless of
  whether LLVM JIT is enabled</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 17.3:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/17.3/
  * https://www.postgresql.org/about/news/-3015/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 17.4:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/17.4/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 17.5:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/17.5/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to Fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1746792001">- Fork package for postgresql 18
  https://www.postgresql.org/about/news/p-3070/</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1753272000">- Update to 18~beta2
  https://www.postgresql.org/about/news/p-3103/</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Update to 18~beta3
  * https://www.postgresql.org/about/news/p-3118/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755518400">- enable liburing and libnuma support
- prepare oauth support. but it creates broken symlinks at the
  moment</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755518401">- In the symlinking loop for *.so files only handle symlinks and
  not also files.
  This allows us to enable oauth support</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755604800">- move libpq-oauth into the libpq5  package. it is a plugin that
  will be loaded via dlopen() if libpq encounters an oauth workflow
  during a connection.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1756987200">- Update to 18 RC1.
  * https://www.postgresql.org/about/news/p-3130/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1758628800">- Update to 18.0.
  * https://www.postgresql.org/about/news/p-3142/
  * https://www.postgresql.org/docs/18/release-18.html</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1758801600">- pg_config --libs returns -lnuma so we need to require it.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Update to 18.1:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/18.1/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 18.2:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/18.2/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * bsc#1258012, CVE-2026-2007: Harden contrib/pg_trgm against
    changes in string lowercasing behavior.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 18.3 to fix two regressions in 18.2:
  * https://www.postgresql.org/docs/release/18.3/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
</package>
<package pkgid="4dc156253cb70a19dba2ff2233e269ab34e3a26fc0c9ec79265438673d33037fe1c279a918b2700965f0a78d88cbecb1b94a0a85926423703364411a42a8fd65" name="postgresql18-devel-mini" arch="ppc64le">
  <version epoch="0" ver="18.3" rel="3.1"/>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="JS &lt;obs.coke518@passinbox.com&gt;" date="1738152000">- Apply postgresql-tzdata2025a.patch regardless of
  whether LLVM JIT is enabled</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 17.3:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/17.3/
  * https://www.postgresql.org/about/news/-3015/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 17.4:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/17.4/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 17.5:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/17.5/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to Fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1746792001">- Fork package for postgresql 18
  https://www.postgresql.org/about/news/p-3070/</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1753272000">- Update to 18~beta2
  https://www.postgresql.org/about/news/p-3103/</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Update to 18~beta3
  * https://www.postgresql.org/about/news/p-3118/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755518400">- enable liburing and libnuma support
- prepare oauth support. but it creates broken symlinks at the
  moment</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755518401">- In the symlinking loop for *.so files only handle symlinks and
  not also files.
  This allows us to enable oauth support</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755604800">- move libpq-oauth into the libpq5  package. it is a plugin that
  will be loaded via dlopen() if libpq encounters an oauth workflow
  during a connection.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1756987200">- Update to 18 RC1.
  * https://www.postgresql.org/about/news/p-3130/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1758628800">- Update to 18.0.
  * https://www.postgresql.org/about/news/p-3142/
  * https://www.postgresql.org/docs/18/release-18.html</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1758801600">- pg_config --libs returns -lnuma so we need to require it.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Update to 18.1:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/18.1/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 18.2:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/18.2/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * bsc#1258012, CVE-2026-2007: Harden contrib/pg_trgm against
    changes in string lowercasing behavior.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 18.3 to fix two regressions in 18.2:
  * https://www.postgresql.org/docs/release/18.3/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
</package>
<package pkgid="4ca58cdc0eace367c0491a4cb9780105f5915b41c22b127f21daebbd3bd7c65a584ace37af425fe7915ed72382875bcd5ebf6ebdfd0d4f6fc13f7c06ea7344c3" name="postgresql18-devel-mini" arch="x86_64">
  <version epoch="0" ver="18.4" rel="18.2"/>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 17.4:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/17.4/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 17.5:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/17.5/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to Fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1746792001">- Fork package for postgresql 18
  https://www.postgresql.org/about/news/p-3070/</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1753272000">- Update to 18~beta2
  https://www.postgresql.org/about/news/p-3103/</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Update to 18~beta3
  * https://www.postgresql.org/about/news/p-3118/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755518400">- enable liburing and libnuma support
- prepare oauth support. but it creates broken symlinks at the
  moment</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755518401">- In the symlinking loop for *.so files only handle symlinks and
  not also files.
  This allows us to enable oauth support</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755604800">- move libpq-oauth into the libpq5  package. it is a plugin that
  will be loaded via dlopen() if libpq encounters an oauth workflow
  during a connection.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1756987200">- Update to 18 RC1.
  * https://www.postgresql.org/about/news/p-3130/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1758628800">- Update to 18.0.
  * https://www.postgresql.org/about/news/p-3142/
  * https://www.postgresql.org/docs/18/release-18.html</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1758801600">- pg_config --libs returns -lnuma so we need to require it.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Update to 18.1:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/18.1/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 18.2:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/18.2/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * bsc#1258012, CVE-2026-2007: Harden contrib/pg_trgm against
    changes in string lowercasing behavior.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 18.3 to fix two regressions in 18.2:
  * https://www.postgresql.org/docs/release/18.3/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1774526400">- Get rid of update-alternatives for openSUSE/SLE 16.0 and newer
  to support immutable systems and transactional updates.
  (jsc#PED-14820)</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1777550400">- bsc#1263804: After dropping update-alternatives we have to
  package /usr/bin/pg_config as an actual symlink, not %ghost.
- Fix spelling of build conditionals.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1778673600">- Update to version 18.4:
  * bsc#1265172, CVE-2026-6472: ensure the user has CREATE
    privilege on the schema specified
  * bsc#1265173, CVE-2026-6473: integer overflows in
    memory-allocation calculations
  * bsc#1265174, CVE-2026-6474: Guard against malicious time zone
    names
  * bsc#1265175, CVE-2026-6475: Prevent path traversal in
    pg_basebackup and pg_rewind
  * bsc#1265176, CVE-2026-6476: Properly quote subscription names
    in pg_createsubscriber
  * bsc#1265177, CVE-2026-6477: Mark PQfn() as unsafe, and avoid
    using it within libpq
  * bsc#1265178, CVE-2026-6478: Use timing-safe string comparisons
    in authentication code
  * bsc#1265179, CVE-2026-6479: Prevent unbounded recursion while
    processing startup packets
  * bsc#1265180, CVE-2026-6575: Detect faulty input when restoring
    attribute MCV statistics
  * bsc#1265181, CVE-2026-6637: Prevent SQL injection and buffer
    overruns in contrib/spi
  * bsc#1265182, CVE-2026-6638: Properly quote object names in
    logical replication origin checks
  * https://www.postgresql.org/docs/release/18.4/</changelog>
</package>
<package pkgid="917eeb155eac62269e5fe41254db15036820310d0cd42d75102fa0f8fcabc11d7dd3c451a82842e7b5e47474c8f7c182dde3fb71ec213aeef9f7989d15daab06" name="postgresql18-docs" arch="noarch">
  <version epoch="0" ver="18.3" rel="2.3"/>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="JS &lt;obs.coke518@passinbox.com&gt;" date="1738152000">- Apply postgresql-tzdata2025a.patch regardless of
  whether LLVM JIT is enabled</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 17.3:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/17.3/
  * https://www.postgresql.org/about/news/-3015/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 17.4:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/17.4/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 17.5:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/17.5/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to Fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1746792001">- Fork package for postgresql 18
  https://www.postgresql.org/about/news/p-3070/</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1753272000">- Update to 18~beta2
  https://www.postgresql.org/about/news/p-3103/</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Update to 18~beta3
  * https://www.postgresql.org/about/news/p-3118/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755518400">- enable liburing and libnuma support
- prepare oauth support. but it creates broken symlinks at the
  moment</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755518401">- In the symlinking loop for *.so files only handle symlinks and
  not also files.
  This allows us to enable oauth support</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755604800">- move libpq-oauth into the libpq5  package. it is a plugin that
  will be loaded via dlopen() if libpq encounters an oauth workflow
  during a connection.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1756987200">- Update to 18 RC1.
  * https://www.postgresql.org/about/news/p-3130/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1758628800">- Update to 18.0.
  * https://www.postgresql.org/about/news/p-3142/
  * https://www.postgresql.org/docs/18/release-18.html</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1758801600">- pg_config --libs returns -lnuma so we need to require it.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Update to 18.1:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/18.1/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 18.2:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/18.2/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * bsc#1258012, CVE-2026-2007: Harden contrib/pg_trgm against
    changes in string lowercasing behavior.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 18.3 to fix two regressions in 18.2:
  * https://www.postgresql.org/docs/release/18.3/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
</package>
<package pkgid="a547dda1b24ed9b4fdd375818bceb8f5051c770e42bdb54c8bf050a4bd3110a929f5661129a9f460c079586543ecae43b444b649d979613e5416537bbfcfeb4f" name="postgresql18-docs" arch="noarch">
  <version epoch="0" ver="18.3" rel="3.1"/>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="JS &lt;obs.coke518@passinbox.com&gt;" date="1738152000">- Apply postgresql-tzdata2025a.patch regardless of
  whether LLVM JIT is enabled</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 17.3:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/17.3/
  * https://www.postgresql.org/about/news/-3015/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 17.4:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/17.4/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 17.5:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/17.5/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to Fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1746792001">- Fork package for postgresql 18
  https://www.postgresql.org/about/news/p-3070/</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1753272000">- Update to 18~beta2
  https://www.postgresql.org/about/news/p-3103/</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Update to 18~beta3
  * https://www.postgresql.org/about/news/p-3118/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755518400">- enable liburing and libnuma support
- prepare oauth support. but it creates broken symlinks at the
  moment</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755518401">- In the symlinking loop for *.so files only handle symlinks and
  not also files.
  This allows us to enable oauth support</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755604800">- move libpq-oauth into the libpq5  package. it is a plugin that
  will be loaded via dlopen() if libpq encounters an oauth workflow
  during a connection.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1756987200">- Update to 18 RC1.
  * https://www.postgresql.org/about/news/p-3130/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1758628800">- Update to 18.0.
  * https://www.postgresql.org/about/news/p-3142/
  * https://www.postgresql.org/docs/18/release-18.html</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1758801600">- pg_config --libs returns -lnuma so we need to require it.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Update to 18.1:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/18.1/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 18.2:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/18.2/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * bsc#1258012, CVE-2026-2007: Harden contrib/pg_trgm against
    changes in string lowercasing behavior.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 18.3 to fix two regressions in 18.2:
  * https://www.postgresql.org/docs/release/18.3/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
</package>
<package pkgid="626285d5d7c38d5c03305a6e7ca0d93a5c8a07c60bc12d27e9ba0e7ffaf600f00ccf421351605347cab2300c618de3b48b399eac052dd51b9dd1f97ec07bc5d8" name="postgresql18-docs" arch="noarch">
  <version epoch="0" ver="18.4" rel="18.3"/>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 17.4:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/17.4/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 17.5:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/17.5/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to Fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1746792001">- Fork package for postgresql 18
  https://www.postgresql.org/about/news/p-3070/</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1753272000">- Update to 18~beta2
  https://www.postgresql.org/about/news/p-3103/</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Update to 18~beta3
  * https://www.postgresql.org/about/news/p-3118/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755518400">- enable liburing and libnuma support
- prepare oauth support. but it creates broken symlinks at the
  moment</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755518401">- In the symlinking loop for *.so files only handle symlinks and
  not also files.
  This allows us to enable oauth support</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755604800">- move libpq-oauth into the libpq5  package. it is a plugin that
  will be loaded via dlopen() if libpq encounters an oauth workflow
  during a connection.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1756987200">- Update to 18 RC1.
  * https://www.postgresql.org/about/news/p-3130/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1758628800">- Update to 18.0.
  * https://www.postgresql.org/about/news/p-3142/
  * https://www.postgresql.org/docs/18/release-18.html</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1758801600">- pg_config --libs returns -lnuma so we need to require it.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Update to 18.1:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/18.1/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 18.2:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/18.2/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * bsc#1258012, CVE-2026-2007: Harden contrib/pg_trgm against
    changes in string lowercasing behavior.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 18.3 to fix two regressions in 18.2:
  * https://www.postgresql.org/docs/release/18.3/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1774526400">- Get rid of update-alternatives for openSUSE/SLE 16.0 and newer
  to support immutable systems and transactional updates.
  (jsc#PED-14820)</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1777550400">- bsc#1263804: After dropping update-alternatives we have to
  package /usr/bin/pg_config as an actual symlink, not %ghost.
- Fix spelling of build conditionals.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1778673600">- Update to version 18.4:
  * bsc#1265172, CVE-2026-6472: ensure the user has CREATE
    privilege on the schema specified
  * bsc#1265173, CVE-2026-6473: integer overflows in
    memory-allocation calculations
  * bsc#1265174, CVE-2026-6474: Guard against malicious time zone
    names
  * bsc#1265175, CVE-2026-6475: Prevent path traversal in
    pg_basebackup and pg_rewind
  * bsc#1265176, CVE-2026-6476: Properly quote subscription names
    in pg_createsubscriber
  * bsc#1265177, CVE-2026-6477: Mark PQfn() as unsafe, and avoid
    using it within libpq
  * bsc#1265178, CVE-2026-6478: Use timing-safe string comparisons
    in authentication code
  * bsc#1265179, CVE-2026-6479: Prevent unbounded recursion while
    processing startup packets
  * bsc#1265180, CVE-2026-6575: Detect faulty input when restoring
    attribute MCV statistics
  * bsc#1265181, CVE-2026-6637: Prevent SQL injection and buffer
    overruns in contrib/spi
  * bsc#1265182, CVE-2026-6638: Properly quote object names in
    logical replication origin checks
  * https://www.postgresql.org/docs/release/18.4/</changelog>
</package>
<package pkgid="7da8bdf7436c4098238ee2d5b16d028abdf008a4ac20d8fd4955e07f356ac143157e7aa64e132c57122a351ff110279495eeed48deadc6b46a51802237eba45c" name="postgresql18-llvmjit" arch="s390x">
  <version epoch="0" ver="18.3" rel="2.3"/>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="JS &lt;obs.coke518@passinbox.com&gt;" date="1738152000">- Apply postgresql-tzdata2025a.patch regardless of
  whether LLVM JIT is enabled</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 17.3:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/17.3/
  * https://www.postgresql.org/about/news/-3015/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 17.4:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/17.4/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 17.5:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/17.5/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to Fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1746792001">- Fork package for postgresql 18
  https://www.postgresql.org/about/news/p-3070/</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1753272000">- Update to 18~beta2
  https://www.postgresql.org/about/news/p-3103/</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Update to 18~beta3
  * https://www.postgresql.org/about/news/p-3118/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755518400">- enable liburing and libnuma support
- prepare oauth support. but it creates broken symlinks at the
  moment</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755518401">- In the symlinking loop for *.so files only handle symlinks and
  not also files.
  This allows us to enable oauth support</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755604800">- move libpq-oauth into the libpq5  package. it is a plugin that
  will be loaded via dlopen() if libpq encounters an oauth workflow
  during a connection.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1756987200">- Update to 18 RC1.
  * https://www.postgresql.org/about/news/p-3130/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1758628800">- Update to 18.0.
  * https://www.postgresql.org/about/news/p-3142/
  * https://www.postgresql.org/docs/18/release-18.html</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1758801600">- pg_config --libs returns -lnuma so we need to require it.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Update to 18.1:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/18.1/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 18.2:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/18.2/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * bsc#1258012, CVE-2026-2007: Harden contrib/pg_trgm against
    changes in string lowercasing behavior.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 18.3 to fix two regressions in 18.2:
  * https://www.postgresql.org/docs/release/18.3/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
</package>
<package pkgid="3abaf4ce7f175ce2875d94ded0502324edcd97c92b78b670941ef0bdc5ea6921ad246f56ee5bc42169f5f60a52a6d73c2aedb034b1e54b588a940dbf1641e782" name="postgresql18-llvmjit" arch="aarch64">
  <version epoch="0" ver="18.3" rel="3.1"/>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="JS &lt;obs.coke518@passinbox.com&gt;" date="1738152000">- Apply postgresql-tzdata2025a.patch regardless of
  whether LLVM JIT is enabled</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 17.3:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/17.3/
  * https://www.postgresql.org/about/news/-3015/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 17.4:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/17.4/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 17.5:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/17.5/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to Fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1746792001">- Fork package for postgresql 18
  https://www.postgresql.org/about/news/p-3070/</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1753272000">- Update to 18~beta2
  https://www.postgresql.org/about/news/p-3103/</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Update to 18~beta3
  * https://www.postgresql.org/about/news/p-3118/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755518400">- enable liburing and libnuma support
- prepare oauth support. but it creates broken symlinks at the
  moment</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755518401">- In the symlinking loop for *.so files only handle symlinks and
  not also files.
  This allows us to enable oauth support</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755604800">- move libpq-oauth into the libpq5  package. it is a plugin that
  will be loaded via dlopen() if libpq encounters an oauth workflow
  during a connection.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1756987200">- Update to 18 RC1.
  * https://www.postgresql.org/about/news/p-3130/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1758628800">- Update to 18.0.
  * https://www.postgresql.org/about/news/p-3142/
  * https://www.postgresql.org/docs/18/release-18.html</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1758801600">- pg_config --libs returns -lnuma so we need to require it.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Update to 18.1:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/18.1/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 18.2:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/18.2/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * bsc#1258012, CVE-2026-2007: Harden contrib/pg_trgm against
    changes in string lowercasing behavior.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 18.3 to fix two regressions in 18.2:
  * https://www.postgresql.org/docs/release/18.3/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
</package>
<package pkgid="fffac70451e2d8572bd389b6e1c64fceb3fd39d94fdaf8a70dd2e278240e47245b5b66229ff870d5c8f5ef52c91c94d1862c75762a4b6470ddf396008f3ba4bf" name="postgresql18-llvmjit" arch="ppc64le">
  <version epoch="0" ver="18.3" rel="3.1"/>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="JS &lt;obs.coke518@passinbox.com&gt;" date="1738152000">- Apply postgresql-tzdata2025a.patch regardless of
  whether LLVM JIT is enabled</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 17.3:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/17.3/
  * https://www.postgresql.org/about/news/-3015/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 17.4:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/17.4/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 17.5:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/17.5/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to Fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1746792001">- Fork package for postgresql 18
  https://www.postgresql.org/about/news/p-3070/</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1753272000">- Update to 18~beta2
  https://www.postgresql.org/about/news/p-3103/</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Update to 18~beta3
  * https://www.postgresql.org/about/news/p-3118/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755518400">- enable liburing and libnuma support
- prepare oauth support. but it creates broken symlinks at the
  moment</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755518401">- In the symlinking loop for *.so files only handle symlinks and
  not also files.
  This allows us to enable oauth support</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755604800">- move libpq-oauth into the libpq5  package. it is a plugin that
  will be loaded via dlopen() if libpq encounters an oauth workflow
  during a connection.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1756987200">- Update to 18 RC1.
  * https://www.postgresql.org/about/news/p-3130/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1758628800">- Update to 18.0.
  * https://www.postgresql.org/about/news/p-3142/
  * https://www.postgresql.org/docs/18/release-18.html</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1758801600">- pg_config --libs returns -lnuma so we need to require it.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Update to 18.1:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/18.1/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 18.2:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/18.2/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * bsc#1258012, CVE-2026-2007: Harden contrib/pg_trgm against
    changes in string lowercasing behavior.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 18.3 to fix two regressions in 18.2:
  * https://www.postgresql.org/docs/release/18.3/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
</package>
<package pkgid="d9418988121ae23e15b4d8e1ebc39cc5bc95fcac10085cac579f27550c7c3c4de64be6401ebfdc1ebb040b79c23a981220934391cc112e19f935718d6f38be5d" name="postgresql18-llvmjit" arch="x86_64">
  <version epoch="0" ver="18.4" rel="18.3"/>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 17.4:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/17.4/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 17.5:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/17.5/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to Fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1746792001">- Fork package for postgresql 18
  https://www.postgresql.org/about/news/p-3070/</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1753272000">- Update to 18~beta2
  https://www.postgresql.org/about/news/p-3103/</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Update to 18~beta3
  * https://www.postgresql.org/about/news/p-3118/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755518400">- enable liburing and libnuma support
- prepare oauth support. but it creates broken symlinks at the
  moment</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755518401">- In the symlinking loop for *.so files only handle symlinks and
  not also files.
  This allows us to enable oauth support</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755604800">- move libpq-oauth into the libpq5  package. it is a plugin that
  will be loaded via dlopen() if libpq encounters an oauth workflow
  during a connection.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1756987200">- Update to 18 RC1.
  * https://www.postgresql.org/about/news/p-3130/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1758628800">- Update to 18.0.
  * https://www.postgresql.org/about/news/p-3142/
  * https://www.postgresql.org/docs/18/release-18.html</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1758801600">- pg_config --libs returns -lnuma so we need to require it.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Update to 18.1:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/18.1/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 18.2:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/18.2/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * bsc#1258012, CVE-2026-2007: Harden contrib/pg_trgm against
    changes in string lowercasing behavior.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 18.3 to fix two regressions in 18.2:
  * https://www.postgresql.org/docs/release/18.3/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1774526400">- Get rid of update-alternatives for openSUSE/SLE 16.0 and newer
  to support immutable systems and transactional updates.
  (jsc#PED-14820)</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1777550400">- bsc#1263804: After dropping update-alternatives we have to
  package /usr/bin/pg_config as an actual symlink, not %ghost.
- Fix spelling of build conditionals.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1778673600">- Update to version 18.4:
  * bsc#1265172, CVE-2026-6472: ensure the user has CREATE
    privilege on the schema specified
  * bsc#1265173, CVE-2026-6473: integer overflows in
    memory-allocation calculations
  * bsc#1265174, CVE-2026-6474: Guard against malicious time zone
    names
  * bsc#1265175, CVE-2026-6475: Prevent path traversal in
    pg_basebackup and pg_rewind
  * bsc#1265176, CVE-2026-6476: Properly quote subscription names
    in pg_createsubscriber
  * bsc#1265177, CVE-2026-6477: Mark PQfn() as unsafe, and avoid
    using it within libpq
  * bsc#1265178, CVE-2026-6478: Use timing-safe string comparisons
    in authentication code
  * bsc#1265179, CVE-2026-6479: Prevent unbounded recursion while
    processing startup packets
  * bsc#1265180, CVE-2026-6575: Detect faulty input when restoring
    attribute MCV statistics
  * bsc#1265181, CVE-2026-6637: Prevent SQL injection and buffer
    overruns in contrib/spi
  * bsc#1265182, CVE-2026-6638: Properly quote object names in
    logical replication origin checks
  * https://www.postgresql.org/docs/release/18.4/</changelog>
</package>
<package pkgid="099af3c72affcc069e4d2ad6ec241594a94c2244645f9f6fcb23f1cd3c93a8f5ed3e8a060aee997e88a35545f9db3ecbe9e0769b2df70259435a291545721829" name="postgresql18-llvmjit-devel" arch="s390x">
  <version epoch="0" ver="18.3" rel="2.3"/>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="JS &lt;obs.coke518@passinbox.com&gt;" date="1738152000">- Apply postgresql-tzdata2025a.patch regardless of
  whether LLVM JIT is enabled</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 17.3:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/17.3/
  * https://www.postgresql.org/about/news/-3015/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 17.4:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/17.4/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 17.5:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/17.5/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to Fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1746792001">- Fork package for postgresql 18
  https://www.postgresql.org/about/news/p-3070/</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1753272000">- Update to 18~beta2
  https://www.postgresql.org/about/news/p-3103/</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Update to 18~beta3
  * https://www.postgresql.org/about/news/p-3118/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755518400">- enable liburing and libnuma support
- prepare oauth support. but it creates broken symlinks at the
  moment</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755518401">- In the symlinking loop for *.so files only handle symlinks and
  not also files.
  This allows us to enable oauth support</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755604800">- move libpq-oauth into the libpq5  package. it is a plugin that
  will be loaded via dlopen() if libpq encounters an oauth workflow
  during a connection.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1756987200">- Update to 18 RC1.
  * https://www.postgresql.org/about/news/p-3130/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1758628800">- Update to 18.0.
  * https://www.postgresql.org/about/news/p-3142/
  * https://www.postgresql.org/docs/18/release-18.html</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1758801600">- pg_config --libs returns -lnuma so we need to require it.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Update to 18.1:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/18.1/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 18.2:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/18.2/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * bsc#1258012, CVE-2026-2007: Harden contrib/pg_trgm against
    changes in string lowercasing behavior.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 18.3 to fix two regressions in 18.2:
  * https://www.postgresql.org/docs/release/18.3/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
</package>
<package pkgid="16425377a4be3dae54092d81205d496b69e9b9c913052db648b6c0e3de37fb7cf891c7ca52a203d4b83a1d870fa8e16b4acec18a92132cf965908c3147f9967c" name="postgresql18-llvmjit-devel" arch="aarch64">
  <version epoch="0" ver="18.3" rel="3.1"/>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="JS &lt;obs.coke518@passinbox.com&gt;" date="1738152000">- Apply postgresql-tzdata2025a.patch regardless of
  whether LLVM JIT is enabled</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 17.3:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/17.3/
  * https://www.postgresql.org/about/news/-3015/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 17.4:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/17.4/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 17.5:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/17.5/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to Fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1746792001">- Fork package for postgresql 18
  https://www.postgresql.org/about/news/p-3070/</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1753272000">- Update to 18~beta2
  https://www.postgresql.org/about/news/p-3103/</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Update to 18~beta3
  * https://www.postgresql.org/about/news/p-3118/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755518400">- enable liburing and libnuma support
- prepare oauth support. but it creates broken symlinks at the
  moment</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755518401">- In the symlinking loop for *.so files only handle symlinks and
  not also files.
  This allows us to enable oauth support</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755604800">- move libpq-oauth into the libpq5  package. it is a plugin that
  will be loaded via dlopen() if libpq encounters an oauth workflow
  during a connection.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1756987200">- Update to 18 RC1.
  * https://www.postgresql.org/about/news/p-3130/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1758628800">- Update to 18.0.
  * https://www.postgresql.org/about/news/p-3142/
  * https://www.postgresql.org/docs/18/release-18.html</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1758801600">- pg_config --libs returns -lnuma so we need to require it.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Update to 18.1:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/18.1/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 18.2:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/18.2/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * bsc#1258012, CVE-2026-2007: Harden contrib/pg_trgm against
    changes in string lowercasing behavior.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 18.3 to fix two regressions in 18.2:
  * https://www.postgresql.org/docs/release/18.3/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
</package>
<package pkgid="66b52ec643e7ae7d38074a4d9dddbb70d44341314a2f5e60aa1903c0740cca83ed7780ba560a25b1c45de4fea62f2c041c5afbf312acde11dc3f4b9a7b13a8d5" name="postgresql18-llvmjit-devel" arch="ppc64le">
  <version epoch="0" ver="18.3" rel="3.1"/>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="JS &lt;obs.coke518@passinbox.com&gt;" date="1738152000">- Apply postgresql-tzdata2025a.patch regardless of
  whether LLVM JIT is enabled</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 17.3:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/17.3/
  * https://www.postgresql.org/about/news/-3015/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 17.4:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/17.4/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 17.5:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/17.5/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to Fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1746792001">- Fork package for postgresql 18
  https://www.postgresql.org/about/news/p-3070/</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1753272000">- Update to 18~beta2
  https://www.postgresql.org/about/news/p-3103/</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Update to 18~beta3
  * https://www.postgresql.org/about/news/p-3118/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755518400">- enable liburing and libnuma support
- prepare oauth support. but it creates broken symlinks at the
  moment</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755518401">- In the symlinking loop for *.so files only handle symlinks and
  not also files.
  This allows us to enable oauth support</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755604800">- move libpq-oauth into the libpq5  package. it is a plugin that
  will be loaded via dlopen() if libpq encounters an oauth workflow
  during a connection.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1756987200">- Update to 18 RC1.
  * https://www.postgresql.org/about/news/p-3130/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1758628800">- Update to 18.0.
  * https://www.postgresql.org/about/news/p-3142/
  * https://www.postgresql.org/docs/18/release-18.html</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1758801600">- pg_config --libs returns -lnuma so we need to require it.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Update to 18.1:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/18.1/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 18.2:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/18.2/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * bsc#1258012, CVE-2026-2007: Harden contrib/pg_trgm against
    changes in string lowercasing behavior.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 18.3 to fix two regressions in 18.2:
  * https://www.postgresql.org/docs/release/18.3/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
</package>
<package pkgid="1a88d0bfc90d9b0e296b4d24be008ee1d9981798d3c50b55d78951f776bbcfea78ce1cc530b11c45724f5335c1b26fd6f3d739793f4117f45234cb534cfc3453" name="postgresql18-llvmjit-devel" arch="x86_64">
  <version epoch="0" ver="18.4" rel="18.3"/>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 17.4:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/17.4/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 17.5:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/17.5/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to Fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1746792001">- Fork package for postgresql 18
  https://www.postgresql.org/about/news/p-3070/</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1753272000">- Update to 18~beta2
  https://www.postgresql.org/about/news/p-3103/</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Update to 18~beta3
  * https://www.postgresql.org/about/news/p-3118/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755518400">- enable liburing and libnuma support
- prepare oauth support. but it creates broken symlinks at the
  moment</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755518401">- In the symlinking loop for *.so files only handle symlinks and
  not also files.
  This allows us to enable oauth support</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755604800">- move libpq-oauth into the libpq5  package. it is a plugin that
  will be loaded via dlopen() if libpq encounters an oauth workflow
  during a connection.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1756987200">- Update to 18 RC1.
  * https://www.postgresql.org/about/news/p-3130/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1758628800">- Update to 18.0.
  * https://www.postgresql.org/about/news/p-3142/
  * https://www.postgresql.org/docs/18/release-18.html</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1758801600">- pg_config --libs returns -lnuma so we need to require it.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Update to 18.1:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/18.1/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 18.2:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/18.2/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * bsc#1258012, CVE-2026-2007: Harden contrib/pg_trgm against
    changes in string lowercasing behavior.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 18.3 to fix two regressions in 18.2:
  * https://www.postgresql.org/docs/release/18.3/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1774526400">- Get rid of update-alternatives for openSUSE/SLE 16.0 and newer
  to support immutable systems and transactional updates.
  (jsc#PED-14820)</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1777550400">- bsc#1263804: After dropping update-alternatives we have to
  package /usr/bin/pg_config as an actual symlink, not %ghost.
- Fix spelling of build conditionals.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1778673600">- Update to version 18.4:
  * bsc#1265172, CVE-2026-6472: ensure the user has CREATE
    privilege on the schema specified
  * bsc#1265173, CVE-2026-6473: integer overflows in
    memory-allocation calculations
  * bsc#1265174, CVE-2026-6474: Guard against malicious time zone
    names
  * bsc#1265175, CVE-2026-6475: Prevent path traversal in
    pg_basebackup and pg_rewind
  * bsc#1265176, CVE-2026-6476: Properly quote subscription names
    in pg_createsubscriber
  * bsc#1265177, CVE-2026-6477: Mark PQfn() as unsafe, and avoid
    using it within libpq
  * bsc#1265178, CVE-2026-6478: Use timing-safe string comparisons
    in authentication code
  * bsc#1265179, CVE-2026-6479: Prevent unbounded recursion while
    processing startup packets
  * bsc#1265180, CVE-2026-6575: Detect faulty input when restoring
    attribute MCV statistics
  * bsc#1265181, CVE-2026-6637: Prevent SQL injection and buffer
    overruns in contrib/spi
  * bsc#1265182, CVE-2026-6638: Properly quote object names in
    logical replication origin checks
  * https://www.postgresql.org/docs/release/18.4/</changelog>
</package>
<package pkgid="ba5f730b2647dab737cb67ac2975d4b68dcced1c2e5d9736e68e358a107065b8dbd4ee728e03053c3d266e59c2c110296bb717acb78595a4269b22f9290418f1" name="postgresql18-mini" arch="src">
  <version epoch="0" ver="18.3" rel="2.1"/>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="JS &lt;obs.coke518@passinbox.com&gt;" date="1738152000">- Apply postgresql-tzdata2025a.patch regardless of
  whether LLVM JIT is enabled</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 17.3:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/17.3/
  * https://www.postgresql.org/about/news/-3015/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 17.4:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/17.4/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 17.5:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/17.5/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to Fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1746792001">- Fork package for postgresql 18
  https://www.postgresql.org/about/news/p-3070/</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1753272000">- Update to 18~beta2
  https://www.postgresql.org/about/news/p-3103/</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Update to 18~beta3
  * https://www.postgresql.org/about/news/p-3118/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755518400">- enable liburing and libnuma support
- prepare oauth support. but it creates broken symlinks at the
  moment</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755518401">- In the symlinking loop for *.so files only handle symlinks and
  not also files.
  This allows us to enable oauth support</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755604800">- move libpq-oauth into the libpq5  package. it is a plugin that
  will be loaded via dlopen() if libpq encounters an oauth workflow
  during a connection.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1756987200">- Update to 18 RC1.
  * https://www.postgresql.org/about/news/p-3130/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1758628800">- Update to 18.0.
  * https://www.postgresql.org/about/news/p-3142/
  * https://www.postgresql.org/docs/18/release-18.html</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1758801600">- pg_config --libs returns -lnuma so we need to require it.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Update to 18.1:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/18.1/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 18.2:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/18.2/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * bsc#1258012, CVE-2026-2007: Harden contrib/pg_trgm against
    changes in string lowercasing behavior.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 18.3 to fix two regressions in 18.2:
  * https://www.postgresql.org/docs/release/18.3/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
</package>
<package pkgid="72e19c1ee5b81d130ff718404957155180fa8b84df3d492acfaeb3881681cf81cf9cd6f0c497f15606220bdfe343a0de5aa51cf467df75f771dc159bab9fc07f" name="postgresql18-mini" arch="src">
  <version epoch="0" ver="18.3" rel="3.1"/>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="JS &lt;obs.coke518@passinbox.com&gt;" date="1738152000">- Apply postgresql-tzdata2025a.patch regardless of
  whether LLVM JIT is enabled</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 17.3:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/17.3/
  * https://www.postgresql.org/about/news/-3015/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 17.4:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/17.4/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 17.5:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/17.5/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to Fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1746792001">- Fork package for postgresql 18
  https://www.postgresql.org/about/news/p-3070/</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1753272000">- Update to 18~beta2
  https://www.postgresql.org/about/news/p-3103/</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Update to 18~beta3
  * https://www.postgresql.org/about/news/p-3118/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755518400">- enable liburing and libnuma support
- prepare oauth support. but it creates broken symlinks at the
  moment</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755518401">- In the symlinking loop for *.so files only handle symlinks and
  not also files.
  This allows us to enable oauth support</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755604800">- move libpq-oauth into the libpq5  package. it is a plugin that
  will be loaded via dlopen() if libpq encounters an oauth workflow
  during a connection.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1756987200">- Update to 18 RC1.
  * https://www.postgresql.org/about/news/p-3130/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1758628800">- Update to 18.0.
  * https://www.postgresql.org/about/news/p-3142/
  * https://www.postgresql.org/docs/18/release-18.html</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1758801600">- pg_config --libs returns -lnuma so we need to require it.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Update to 18.1:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/18.1/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 18.2:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/18.2/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * bsc#1258012, CVE-2026-2007: Harden contrib/pg_trgm against
    changes in string lowercasing behavior.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 18.3 to fix two regressions in 18.2:
  * https://www.postgresql.org/docs/release/18.3/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
</package>
<package pkgid="cfd1bedb094520bd2a8c3fec63c7e0d5a005b5b8c53ae3431eed8eaad3c10afd0d6e05189520a77199e18e8a2cb0ccc704c5b832f822f1d1d2ffc323d1d8f2f6" name="postgresql18-mini" arch="src">
  <version epoch="0" ver="18.4" rel="18.2"/>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 17.4:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/17.4/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 17.5:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/17.5/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to Fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1746792001">- Fork package for postgresql 18
  https://www.postgresql.org/about/news/p-3070/</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1753272000">- Update to 18~beta2
  https://www.postgresql.org/about/news/p-3103/</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Update to 18~beta3
  * https://www.postgresql.org/about/news/p-3118/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755518400">- enable liburing and libnuma support
- prepare oauth support. but it creates broken symlinks at the
  moment</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755518401">- In the symlinking loop for *.so files only handle symlinks and
  not also files.
  This allows us to enable oauth support</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755604800">- move libpq-oauth into the libpq5  package. it is a plugin that
  will be loaded via dlopen() if libpq encounters an oauth workflow
  during a connection.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1756987200">- Update to 18 RC1.
  * https://www.postgresql.org/about/news/p-3130/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1758628800">- Update to 18.0.
  * https://www.postgresql.org/about/news/p-3142/
  * https://www.postgresql.org/docs/18/release-18.html</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1758801600">- pg_config --libs returns -lnuma so we need to require it.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Update to 18.1:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/18.1/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 18.2:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/18.2/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * bsc#1258012, CVE-2026-2007: Harden contrib/pg_trgm against
    changes in string lowercasing behavior.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 18.3 to fix two regressions in 18.2:
  * https://www.postgresql.org/docs/release/18.3/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1774526400">- Get rid of update-alternatives for openSUSE/SLE 16.0 and newer
  to support immutable systems and transactional updates.
  (jsc#PED-14820)</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1777550400">- bsc#1263804: After dropping update-alternatives we have to
  package /usr/bin/pg_config as an actual symlink, not %ghost.
- Fix spelling of build conditionals.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1778673600">- Update to version 18.4:
  * bsc#1265172, CVE-2026-6472: ensure the user has CREATE
    privilege on the schema specified
  * bsc#1265173, CVE-2026-6473: integer overflows in
    memory-allocation calculations
  * bsc#1265174, CVE-2026-6474: Guard against malicious time zone
    names
  * bsc#1265175, CVE-2026-6475: Prevent path traversal in
    pg_basebackup and pg_rewind
  * bsc#1265176, CVE-2026-6476: Properly quote subscription names
    in pg_createsubscriber
  * bsc#1265177, CVE-2026-6477: Mark PQfn() as unsafe, and avoid
    using it within libpq
  * bsc#1265178, CVE-2026-6478: Use timing-safe string comparisons
    in authentication code
  * bsc#1265179, CVE-2026-6479: Prevent unbounded recursion while
    processing startup packets
  * bsc#1265180, CVE-2026-6575: Detect faulty input when restoring
    attribute MCV statistics
  * bsc#1265181, CVE-2026-6637: Prevent SQL injection and buffer
    overruns in contrib/spi
  * bsc#1265182, CVE-2026-6638: Properly quote object names in
    logical replication origin checks
  * https://www.postgresql.org/docs/release/18.4/</changelog>
</package>
<package pkgid="3b5c0508d35a3cd1bf5444a7ca4e79fded92fa57842b9285f2e0f9ec8176379b8fd1a18fadf66ba55f974da786b823eac12d40079c9b665bf747c613c1a71d55" name="postgresql18-pglogical" arch="aarch64">
  <version epoch="0" ver="2.4.6" rel="5.26"/>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1639569600">- update to 2.4.1
  - Fix "snapshot still active" warnings and snapshot handling with
    domains. Problems introduced in version 2.4.0.
  - Flush error state when having failed to drop remote replication
    slot</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1666440000">- update to 2.4.2
  - Add PG 15 support</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1683806400">- Stop supporting postgresql10</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1685534400">- update to 2.4.3
  - Apply data filtering on the correct tuple during initial
    synchronization.
  - Restore the correct memory context while decoding a change.
  - Drop database never completes in PostgreSQL 15.
  - Don't replicate TRUNCATE as global message.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1696420800">- update to 2.4.4
  - add support for pg16</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1725883200">- disable pg11 builds as we will remove the EOL package soon</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1727179200">- update to 2.4.5
  - add support for pg17
  - Fix index usage for conflict resolution.
  - Maintain indexes when updating pglogical.sequence_state.
  - Fix build on PostgreSQL 9.4.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1754654400">- remove pg12 support</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755950400">- update to 2.4.6
  - Add support for PostgreSQL 18.
  - Fix additional deadlock during DROP DATABASE.
  - Fix incorrect row_filter processing after cache invalidation.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755950401">- enable pg18</changelog>
</package>
<package pkgid="94e85385a8d2cd47a00f3ef32f4dbe60077b49749b09c05ca2cc279c0e75df55a68c14432327570d38c0888cb9f87256890df0142129593b415b564bc5bffe52" name="postgresql18-pglogical" arch="ppc64le">
  <version epoch="0" ver="2.4.6" rel="5.26"/>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1639569600">- update to 2.4.1
  - Fix "snapshot still active" warnings and snapshot handling with
    domains. Problems introduced in version 2.4.0.
  - Flush error state when having failed to drop remote replication
    slot</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1666440000">- update to 2.4.2
  - Add PG 15 support</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1683806400">- Stop supporting postgresql10</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1685534400">- update to 2.4.3
  - Apply data filtering on the correct tuple during initial
    synchronization.
  - Restore the correct memory context while decoding a change.
  - Drop database never completes in PostgreSQL 15.
  - Don't replicate TRUNCATE as global message.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1696420800">- update to 2.4.4
  - add support for pg16</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1725883200">- disable pg11 builds as we will remove the EOL package soon</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1727179200">- update to 2.4.5
  - add support for pg17
  - Fix index usage for conflict resolution.
  - Maintain indexes when updating pglogical.sequence_state.
  - Fix build on PostgreSQL 9.4.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1754654400">- remove pg12 support</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755950400">- update to 2.4.6
  - Add support for PostgreSQL 18.
  - Fix additional deadlock during DROP DATABASE.
  - Fix incorrect row_filter processing after cache invalidation.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755950401">- enable pg18</changelog>
</package>
<package pkgid="d8342e5a04fd6ce95dd0e7fe85d1993ee4548a8b1385e760f0b0bb02fd5a4fd3400a6d0b1d249e457135a16b7a66fe89bbd45921bcff1f6763f61c27e0d2d3a7" name="postgresql18-pglogical" arch="s390x">
  <version epoch="0" ver="2.4.6" rel="5.26"/>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1639569600">- update to 2.4.1
  - Fix "snapshot still active" warnings and snapshot handling with
    domains. Problems introduced in version 2.4.0.
  - Flush error state when having failed to drop remote replication
    slot</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1666440000">- update to 2.4.2
  - Add PG 15 support</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1683806400">- Stop supporting postgresql10</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1685534400">- update to 2.4.3
  - Apply data filtering on the correct tuple during initial
    synchronization.
  - Restore the correct memory context while decoding a change.
  - Drop database never completes in PostgreSQL 15.
  - Don't replicate TRUNCATE as global message.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1696420800">- update to 2.4.4
  - add support for pg16</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1725883200">- disable pg11 builds as we will remove the EOL package soon</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1727179200">- update to 2.4.5
  - add support for pg17
  - Fix index usage for conflict resolution.
  - Maintain indexes when updating pglogical.sequence_state.
  - Fix build on PostgreSQL 9.4.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1754654400">- remove pg12 support</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755950400">- update to 2.4.6
  - Add support for PostgreSQL 18.
  - Fix additional deadlock during DROP DATABASE.
  - Fix incorrect row_filter processing after cache invalidation.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755950401">- enable pg18</changelog>
</package>
<package pkgid="c135d61d32ef61653dfe01d346ebbe7d9935f2a46553df51aa78860957aaa749e9141a81da6c5dcee7a2d46c24dc57ffa27814ba238209b18a2aeb13eca886ef" name="postgresql18-pglogical" arch="src">
  <version epoch="0" ver="2.4.6" rel="5.26"/>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1540641600">- limit to 9.6 and higher</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1571745600">- update to 2.2.2
  - Support for replication of tables which have covering unique
    indexes.
  - Improve failover slot detection.
  - Improve tests of column filtering and row filtering
  - Fix error messages to conform better to PostgreSQL standard.
  - Fix crash in DDL replication when parallelization is used when
    executing the DDL on subscriber.
- split out the llvmjit files into a subpackage</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1588680000">- update to 2.3.0
  The pglogical 2.3.0 is a minor update to the pglogical 2 which
  includes support for PostgreSQL 12 and several new minor features
  and bug fixes.
  - Support for PostgreSQL 12
  - Allow replicating tables and sequences to different names on
    the target
  - Add option to only synchronize the structure of replicated
    relations
  - Add a new option to force a text transfer format for a
    subscription
  - Allow tables to be resynchronized in state SYNC_STATUS_SYNCDONE
  - Fix pglogical_wait_for_sync_complete with unknown table
  - Use write lsn rather than insert lsn by default in
    wait_slot_confirm_lsn</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1604232000">- update to 2.3.3
  - This release adds support for PostgreSQL 13.
  - fixes the build against the latest PostgreSQL minor releases
  - pglogical 2.3.1 contains several fixes that prevented users
    from upgrading to version 2.3.0.  The features "Allow
    replicating tables and sequences to different names on the
    target" and "Add option to only synchronize the structure of
    replicated relations" from pglogical 2.3.0 have been removed in
    this release for the time being and will be added again in a
    later release.
- enable pg13</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1622116800">- CVE-2021-3515, bsc#1186121, pglogical-CVE-2021-3515.patch:
  Shell injection by pglogical users with CREATEDB access</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1622548800">- update to 2.3.4: (bsc#1186121)
  - Fix pg_dump/pg_restore execution (CVE-2021-3515)
    Correctly escape the connection string for both pg_dump and
    pg_restore so that exotic database and user names are handled
    correctly.  Reported by Pedro Gallegos
  - Assign collation to the index scan key
    When doing lookups for INSERT/UPDATE/DELETE, either to find
    conflicts or key for the operation to be applied, we should use
    correct collation.
    This fixes issues with PostgreSQL 12+ primary key lookups when
    primary key is on column using one of the textual types.
  - Execute pg_ctl with appropriate verbosity in
    pglogical_create_subscriber
    When -v is passed to pglogical_create_subscriber, it will now
    call pg_ctl without silent mode. This is useful for
    troubleshooting.
  - Clarify documentation regarding REPLICA IDENTITY requirements
    and support
- drop pglogical-CVE-2021-3515.patch: included in update
- drop do-not-link-unneeded-libs.patch: no longer applicable</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1629115200">- update to 2.4.0
  - Add preliminary support for PostgreSQL 14 (beta)
  - Fix pglogical_show_subscription_table to return row rather than
    set of rows
  - Fix snapshot handling in output plugin and apply worker
  - Fix command quoting on Windows so that it actually works
  - Seems like the API used before has 1024 limit on command line
    length
  - Make sure that the schema syncing process can be interrupted on
    Windows
  - Fix compilation issues with pglogical_create_subscriber on
    Windows
  - Fix double closing of relation when a BEFORE ROW DELETE trigger
    returns NULL in the apply worker
  - Fix multi-insert crash in the SPI apply worker
  - Fix multi-insert doing insert of last tuple multiple times in
    apply worker
  - Make sure debug_query_string is always set Newer versions of
    PostgreSQL require that debug_query_string is always set.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1636891200">- port to postgresql macros</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1638273600">- switch to %{pg_name}-llvmjit-devel</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1638446400">- fix postgresql_has_llvm usage</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1639569600">- update to 2.4.1
  - Fix "snapshot still active" warnings and snapshot handling with
    domains. Problems introduced in version 2.4.0.
  - Flush error state when having failed to drop remote replication
    slot</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1666440000">- update to 2.4.2
  - Add PG 15 support</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1683806400">- Stop supporting postgresql10</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1685534400">- update to 2.4.3
  - Apply data filtering on the correct tuple during initial
    synchronization.
  - Restore the correct memory context while decoding a change.
  - Drop database never completes in PostgreSQL 15.
  - Don't replicate TRUNCATE as global message.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1696420800">- update to 2.4.4
  - add support for pg16</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1725883200">- disable pg11 builds as we will remove the EOL package soon</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1727179200">- update to 2.4.5
  - add support for pg17
  - Fix index usage for conflict resolution.
  - Maintain indexes when updating pglogical.sequence_state.
  - Fix build on PostgreSQL 9.4.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1754654400">- remove pg12 support</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755950400">- update to 2.4.6
  - Add support for PostgreSQL 18.
  - Fix additional deadlock during DROP DATABASE.
  - Fix incorrect row_filter processing after cache invalidation.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755950401">- enable pg18</changelog>
</package>
<package pkgid="daedcb13701a9572e495bf28bd5287386c6b36cdf6b59573d70ad7f85953e2866c715c2bf17e9620b9e321c917017d7c851818ce58cd87a7873f170188006b6f" name="postgresql18-pglogical" arch="src">
  <version epoch="0" ver="2.4.7" rel="4.2"/>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1588680000">- update to 2.3.0
  The pglogical 2.3.0 is a minor update to the pglogical 2 which
  includes support for PostgreSQL 12 and several new minor features
  and bug fixes.
  - Support for PostgreSQL 12
  - Allow replicating tables and sequences to different names on
    the target
  - Add option to only synchronize the structure of replicated
    relations
  - Add a new option to force a text transfer format for a
    subscription
  - Allow tables to be resynchronized in state SYNC_STATUS_SYNCDONE
  - Fix pglogical_wait_for_sync_complete with unknown table
  - Use write lsn rather than insert lsn by default in
    wait_slot_confirm_lsn</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1604232000">- update to 2.3.3
  - This release adds support for PostgreSQL 13.
  - fixes the build against the latest PostgreSQL minor releases
  - pglogical 2.3.1 contains several fixes that prevented users
    from upgrading to version 2.3.0.  The features "Allow
    replicating tables and sequences to different names on the
    target" and "Add option to only synchronize the structure of
    replicated relations" from pglogical 2.3.0 have been removed in
    this release for the time being and will be added again in a
    later release.
- enable pg13</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1622116800">- CVE-2021-3515, bsc#1186121, pglogical-CVE-2021-3515.patch:
  Shell injection by pglogical users with CREATEDB access</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1622548800">- update to 2.3.4: (bsc#1186121)
  - Fix pg_dump/pg_restore execution (CVE-2021-3515)
    Correctly escape the connection string for both pg_dump and
    pg_restore so that exotic database and user names are handled
    correctly.  Reported by Pedro Gallegos
  - Assign collation to the index scan key
    When doing lookups for INSERT/UPDATE/DELETE, either to find
    conflicts or key for the operation to be applied, we should use
    correct collation.
    This fixes issues with PostgreSQL 12+ primary key lookups when
    primary key is on column using one of the textual types.
  - Execute pg_ctl with appropriate verbosity in
    pglogical_create_subscriber
    When -v is passed to pglogical_create_subscriber, it will now
    call pg_ctl without silent mode. This is useful for
    troubleshooting.
  - Clarify documentation regarding REPLICA IDENTITY requirements
    and support
- drop pglogical-CVE-2021-3515.patch: included in update
- drop do-not-link-unneeded-libs.patch: no longer applicable</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1629115200">- update to 2.4.0
  - Add preliminary support for PostgreSQL 14 (beta)
  - Fix pglogical_show_subscription_table to return row rather than
    set of rows
  - Fix snapshot handling in output plugin and apply worker
  - Fix command quoting on Windows so that it actually works
  - Seems like the API used before has 1024 limit on command line
    length
  - Make sure that the schema syncing process can be interrupted on
    Windows
  - Fix compilation issues with pglogical_create_subscriber on
    Windows
  - Fix double closing of relation when a BEFORE ROW DELETE trigger
    returns NULL in the apply worker
  - Fix multi-insert crash in the SPI apply worker
  - Fix multi-insert doing insert of last tuple multiple times in
    apply worker
  - Make sure debug_query_string is always set Newer versions of
    PostgreSQL require that debug_query_string is always set.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1636891200">- port to postgresql macros</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1638273600">- switch to %{pg_name}-llvmjit-devel</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1638446400">- fix postgresql_has_llvm usage</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1639569600">- update to 2.4.1
  - Fix "snapshot still active" warnings and snapshot handling with
    domains. Problems introduced in version 2.4.0.
  - Flush error state when having failed to drop remote replication
    slot</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1666440000">- update to 2.4.2
  - Add PG 15 support</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1683806400">- Stop supporting postgresql10</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1685534400">- update to 2.4.3
  - Apply data filtering on the correct tuple during initial
    synchronization.
  - Restore the correct memory context while decoding a change.
  - Drop database never completes in PostgreSQL 15.
  - Don't replicate TRUNCATE as global message.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1696420800">- update to 2.4.4
  - add support for pg16</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1725883200">- disable pg11 builds as we will remove the EOL package soon</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1727179200">- update to 2.4.5
  - add support for pg17
  - Fix index usage for conflict resolution.
  - Maintain indexes when updating pglogical.sequence_state.
  - Fix build on PostgreSQL 9.4.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1754654400">- remove pg12 support</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755950400">- update to 2.4.6
  - Add support for PostgreSQL 18.
  - Fix additional deadlock during DROP DATABASE.
  - Fix incorrect row_filter processing after cache invalidation.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755950401">- enable pg18</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1778068800">- Disable pg13</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1780315200">- update to 2.4.7
  - Add support for PostgreSQL 19.
  - Fix sync worker hang with idle source database.
  - Fix some memory leaks.</changelog>
</package>
<package pkgid="38b6f7f39bb3d3423b4245172908f8d0347632388bdb44175bb9ccda95fa4dd0a2af0a657e4891f6a8d588c8b66357adb2724c04b41b35fbb2d0818f232c2180" name="postgresql18-pglogical" arch="x86_64">
  <version epoch="0" ver="2.4.7" rel="4.2"/>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1683806400">- Stop supporting postgresql10</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1685534400">- update to 2.4.3
  - Apply data filtering on the correct tuple during initial
    synchronization.
  - Restore the correct memory context while decoding a change.
  - Drop database never completes in PostgreSQL 15.
  - Don't replicate TRUNCATE as global message.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1696420800">- update to 2.4.4
  - add support for pg16</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1725883200">- disable pg11 builds as we will remove the EOL package soon</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1727179200">- update to 2.4.5
  - add support for pg17
  - Fix index usage for conflict resolution.
  - Maintain indexes when updating pglogical.sequence_state.
  - Fix build on PostgreSQL 9.4.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1754654400">- remove pg12 support</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755950400">- update to 2.4.6
  - Add support for PostgreSQL 18.
  - Fix additional deadlock during DROP DATABASE.
  - Fix incorrect row_filter processing after cache invalidation.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755950401">- enable pg18</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1778068800">- Disable pg13</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1780315200">- update to 2.4.7
  - Add support for PostgreSQL 19.
  - Fix sync worker hang with idle source database.
  - Fix some memory leaks.</changelog>
</package>
<package pkgid="395c65256783a3cca07b35d58d8218225259f7071f1d93e24573a54a3b8a4a82979d16c34e4b82f868ee9a15242d5410ee7c605ba1a7fd0367f526776335ce92" name="postgresql18-plperl" arch="s390x">
  <version epoch="0" ver="18.3" rel="2.3"/>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="JS &lt;obs.coke518@passinbox.com&gt;" date="1738152000">- Apply postgresql-tzdata2025a.patch regardless of
  whether LLVM JIT is enabled</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 17.3:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/17.3/
  * https://www.postgresql.org/about/news/-3015/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 17.4:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/17.4/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 17.5:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/17.5/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to Fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1746792001">- Fork package for postgresql 18
  https://www.postgresql.org/about/news/p-3070/</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1753272000">- Update to 18~beta2
  https://www.postgresql.org/about/news/p-3103/</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Update to 18~beta3
  * https://www.postgresql.org/about/news/p-3118/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755518400">- enable liburing and libnuma support
- prepare oauth support. but it creates broken symlinks at the
  moment</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755518401">- In the symlinking loop for *.so files only handle symlinks and
  not also files.
  This allows us to enable oauth support</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755604800">- move libpq-oauth into the libpq5  package. it is a plugin that
  will be loaded via dlopen() if libpq encounters an oauth workflow
  during a connection.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1756987200">- Update to 18 RC1.
  * https://www.postgresql.org/about/news/p-3130/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1758628800">- Update to 18.0.
  * https://www.postgresql.org/about/news/p-3142/
  * https://www.postgresql.org/docs/18/release-18.html</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1758801600">- pg_config --libs returns -lnuma so we need to require it.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Update to 18.1:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/18.1/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 18.2:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/18.2/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * bsc#1258012, CVE-2026-2007: Harden contrib/pg_trgm against
    changes in string lowercasing behavior.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 18.3 to fix two regressions in 18.2:
  * https://www.postgresql.org/docs/release/18.3/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
</package>
<package pkgid="95ceee9b42d180dc2d029bdcef2982f4b3eac97f350530348b581cecd12cb2a144b8b006799b68c7e77ed0cfef3eb3fba837e2cd2fe5a865cee18af4d86c002b" name="postgresql18-plperl" arch="aarch64">
  <version epoch="0" ver="18.3" rel="3.1"/>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="JS &lt;obs.coke518@passinbox.com&gt;" date="1738152000">- Apply postgresql-tzdata2025a.patch regardless of
  whether LLVM JIT is enabled</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 17.3:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/17.3/
  * https://www.postgresql.org/about/news/-3015/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 17.4:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/17.4/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 17.5:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/17.5/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to Fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1746792001">- Fork package for postgresql 18
  https://www.postgresql.org/about/news/p-3070/</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1753272000">- Update to 18~beta2
  https://www.postgresql.org/about/news/p-3103/</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Update to 18~beta3
  * https://www.postgresql.org/about/news/p-3118/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755518400">- enable liburing and libnuma support
- prepare oauth support. but it creates broken symlinks at the
  moment</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755518401">- In the symlinking loop for *.so files only handle symlinks and
  not also files.
  This allows us to enable oauth support</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755604800">- move libpq-oauth into the libpq5  package. it is a plugin that
  will be loaded via dlopen() if libpq encounters an oauth workflow
  during a connection.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1756987200">- Update to 18 RC1.
  * https://www.postgresql.org/about/news/p-3130/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1758628800">- Update to 18.0.
  * https://www.postgresql.org/about/news/p-3142/
  * https://www.postgresql.org/docs/18/release-18.html</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1758801600">- pg_config --libs returns -lnuma so we need to require it.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Update to 18.1:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/18.1/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 18.2:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/18.2/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * bsc#1258012, CVE-2026-2007: Harden contrib/pg_trgm against
    changes in string lowercasing behavior.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 18.3 to fix two regressions in 18.2:
  * https://www.postgresql.org/docs/release/18.3/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
</package>
<package pkgid="3a3b0c5732d35fa6ab2bde69011250221db1e8823be3ace2fc42c1e0d508edb2f483dec100e409d0168e1bc8625ee18f3989f0b6f4cc9fa642df4275c8134151" name="postgresql18-plperl" arch="ppc64le">
  <version epoch="0" ver="18.3" rel="3.1"/>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="JS &lt;obs.coke518@passinbox.com&gt;" date="1738152000">- Apply postgresql-tzdata2025a.patch regardless of
  whether LLVM JIT is enabled</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 17.3:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/17.3/
  * https://www.postgresql.org/about/news/-3015/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 17.4:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/17.4/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 17.5:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/17.5/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to Fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1746792001">- Fork package for postgresql 18
  https://www.postgresql.org/about/news/p-3070/</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1753272000">- Update to 18~beta2
  https://www.postgresql.org/about/news/p-3103/</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Update to 18~beta3
  * https://www.postgresql.org/about/news/p-3118/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755518400">- enable liburing and libnuma support
- prepare oauth support. but it creates broken symlinks at the
  moment</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755518401">- In the symlinking loop for *.so files only handle symlinks and
  not also files.
  This allows us to enable oauth support</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755604800">- move libpq-oauth into the libpq5  package. it is a plugin that
  will be loaded via dlopen() if libpq encounters an oauth workflow
  during a connection.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1756987200">- Update to 18 RC1.
  * https://www.postgresql.org/about/news/p-3130/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1758628800">- Update to 18.0.
  * https://www.postgresql.org/about/news/p-3142/
  * https://www.postgresql.org/docs/18/release-18.html</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1758801600">- pg_config --libs returns -lnuma so we need to require it.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Update to 18.1:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/18.1/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 18.2:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/18.2/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * bsc#1258012, CVE-2026-2007: Harden contrib/pg_trgm against
    changes in string lowercasing behavior.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 18.3 to fix two regressions in 18.2:
  * https://www.postgresql.org/docs/release/18.3/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
</package>
<package pkgid="c01a97cfcc096632aadbf28752a3735053918ad3f085586a06bfb69f63b83a78a5280d0b4f8aaf7af9f8f39fa45b0af4c39f428e45d0f39f9add711d2a5eee58" name="postgresql18-plperl" arch="x86_64">
  <version epoch="0" ver="18.4" rel="18.3"/>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 17.4:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/17.4/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 17.5:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/17.5/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to Fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1746792001">- Fork package for postgresql 18
  https://www.postgresql.org/about/news/p-3070/</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1753272000">- Update to 18~beta2
  https://www.postgresql.org/about/news/p-3103/</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Update to 18~beta3
  * https://www.postgresql.org/about/news/p-3118/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755518400">- enable liburing and libnuma support
- prepare oauth support. but it creates broken symlinks at the
  moment</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755518401">- In the symlinking loop for *.so files only handle symlinks and
  not also files.
  This allows us to enable oauth support</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755604800">- move libpq-oauth into the libpq5  package. it is a plugin that
  will be loaded via dlopen() if libpq encounters an oauth workflow
  during a connection.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1756987200">- Update to 18 RC1.
  * https://www.postgresql.org/about/news/p-3130/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1758628800">- Update to 18.0.
  * https://www.postgresql.org/about/news/p-3142/
  * https://www.postgresql.org/docs/18/release-18.html</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1758801600">- pg_config --libs returns -lnuma so we need to require it.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Update to 18.1:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/18.1/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 18.2:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/18.2/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * bsc#1258012, CVE-2026-2007: Harden contrib/pg_trgm against
    changes in string lowercasing behavior.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 18.3 to fix two regressions in 18.2:
  * https://www.postgresql.org/docs/release/18.3/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1774526400">- Get rid of update-alternatives for openSUSE/SLE 16.0 and newer
  to support immutable systems and transactional updates.
  (jsc#PED-14820)</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1777550400">- bsc#1263804: After dropping update-alternatives we have to
  package /usr/bin/pg_config as an actual symlink, not %ghost.
- Fix spelling of build conditionals.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1778673600">- Update to version 18.4:
  * bsc#1265172, CVE-2026-6472: ensure the user has CREATE
    privilege on the schema specified
  * bsc#1265173, CVE-2026-6473: integer overflows in
    memory-allocation calculations
  * bsc#1265174, CVE-2026-6474: Guard against malicious time zone
    names
  * bsc#1265175, CVE-2026-6475: Prevent path traversal in
    pg_basebackup and pg_rewind
  * bsc#1265176, CVE-2026-6476: Properly quote subscription names
    in pg_createsubscriber
  * bsc#1265177, CVE-2026-6477: Mark PQfn() as unsafe, and avoid
    using it within libpq
  * bsc#1265178, CVE-2026-6478: Use timing-safe string comparisons
    in authentication code
  * bsc#1265179, CVE-2026-6479: Prevent unbounded recursion while
    processing startup packets
  * bsc#1265180, CVE-2026-6575: Detect faulty input when restoring
    attribute MCV statistics
  * bsc#1265181, CVE-2026-6637: Prevent SQL injection and buffer
    overruns in contrib/spi
  * bsc#1265182, CVE-2026-6638: Properly quote object names in
    logical replication origin checks
  * https://www.postgresql.org/docs/release/18.4/</changelog>
</package>
<package pkgid="8889b690e7526a5cad2c957af1009d1e3dd4647bbe53667d311ff08ba4bc89ad9c57c758be38350f5b0352f625d91ef91dd78a37132132e338e6a59085946e4a" name="postgresql18-plpython" arch="s390x">
  <version epoch="0" ver="18.3" rel="2.3"/>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="JS &lt;obs.coke518@passinbox.com&gt;" date="1738152000">- Apply postgresql-tzdata2025a.patch regardless of
  whether LLVM JIT is enabled</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 17.3:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/17.3/
  * https://www.postgresql.org/about/news/-3015/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 17.4:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/17.4/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 17.5:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/17.5/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to Fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1746792001">- Fork package for postgresql 18
  https://www.postgresql.org/about/news/p-3070/</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1753272000">- Update to 18~beta2
  https://www.postgresql.org/about/news/p-3103/</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Update to 18~beta3
  * https://www.postgresql.org/about/news/p-3118/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755518400">- enable liburing and libnuma support
- prepare oauth support. but it creates broken symlinks at the
  moment</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755518401">- In the symlinking loop for *.so files only handle symlinks and
  not also files.
  This allows us to enable oauth support</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755604800">- move libpq-oauth into the libpq5  package. it is a plugin that
  will be loaded via dlopen() if libpq encounters an oauth workflow
  during a connection.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1756987200">- Update to 18 RC1.
  * https://www.postgresql.org/about/news/p-3130/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1758628800">- Update to 18.0.
  * https://www.postgresql.org/about/news/p-3142/
  * https://www.postgresql.org/docs/18/release-18.html</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1758801600">- pg_config --libs returns -lnuma so we need to require it.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Update to 18.1:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/18.1/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 18.2:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/18.2/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * bsc#1258012, CVE-2026-2007: Harden contrib/pg_trgm against
    changes in string lowercasing behavior.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 18.3 to fix two regressions in 18.2:
  * https://www.postgresql.org/docs/release/18.3/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
</package>
<package pkgid="2fbf1e15bfc09d4b874242fd5168c31c297dbebc0190251a406adc2ce8bb8422244f2b93abd5a6f9970623d369f11f08d2fc681c2764435db7c40d1781422129" name="postgresql18-plpython" arch="aarch64">
  <version epoch="0" ver="18.3" rel="3.1"/>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="JS &lt;obs.coke518@passinbox.com&gt;" date="1738152000">- Apply postgresql-tzdata2025a.patch regardless of
  whether LLVM JIT is enabled</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 17.3:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/17.3/
  * https://www.postgresql.org/about/news/-3015/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 17.4:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/17.4/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 17.5:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/17.5/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to Fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1746792001">- Fork package for postgresql 18
  https://www.postgresql.org/about/news/p-3070/</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1753272000">- Update to 18~beta2
  https://www.postgresql.org/about/news/p-3103/</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Update to 18~beta3
  * https://www.postgresql.org/about/news/p-3118/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755518400">- enable liburing and libnuma support
- prepare oauth support. but it creates broken symlinks at the
  moment</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755518401">- In the symlinking loop for *.so files only handle symlinks and
  not also files.
  This allows us to enable oauth support</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755604800">- move libpq-oauth into the libpq5  package. it is a plugin that
  will be loaded via dlopen() if libpq encounters an oauth workflow
  during a connection.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1756987200">- Update to 18 RC1.
  * https://www.postgresql.org/about/news/p-3130/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1758628800">- Update to 18.0.
  * https://www.postgresql.org/about/news/p-3142/
  * https://www.postgresql.org/docs/18/release-18.html</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1758801600">- pg_config --libs returns -lnuma so we need to require it.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Update to 18.1:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/18.1/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 18.2:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/18.2/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * bsc#1258012, CVE-2026-2007: Harden contrib/pg_trgm against
    changes in string lowercasing behavior.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 18.3 to fix two regressions in 18.2:
  * https://www.postgresql.org/docs/release/18.3/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
</package>
<package pkgid="28ad5760007df463ff14070f5d8c7326f82c687f10714495fb1e509c511c0ee87fd9ea8770a872a2bb823fca8542757d7eb8bf511fd887d1eda56eb0a4c9800e" name="postgresql18-plpython" arch="ppc64le">
  <version epoch="0" ver="18.3" rel="3.1"/>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="JS &lt;obs.coke518@passinbox.com&gt;" date="1738152000">- Apply postgresql-tzdata2025a.patch regardless of
  whether LLVM JIT is enabled</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 17.3:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/17.3/
  * https://www.postgresql.org/about/news/-3015/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 17.4:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/17.4/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 17.5:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/17.5/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to Fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1746792001">- Fork package for postgresql 18
  https://www.postgresql.org/about/news/p-3070/</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1753272000">- Update to 18~beta2
  https://www.postgresql.org/about/news/p-3103/</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Update to 18~beta3
  * https://www.postgresql.org/about/news/p-3118/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755518400">- enable liburing and libnuma support
- prepare oauth support. but it creates broken symlinks at the
  moment</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755518401">- In the symlinking loop for *.so files only handle symlinks and
  not also files.
  This allows us to enable oauth support</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755604800">- move libpq-oauth into the libpq5  package. it is a plugin that
  will be loaded via dlopen() if libpq encounters an oauth workflow
  during a connection.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1756987200">- Update to 18 RC1.
  * https://www.postgresql.org/about/news/p-3130/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1758628800">- Update to 18.0.
  * https://www.postgresql.org/about/news/p-3142/
  * https://www.postgresql.org/docs/18/release-18.html</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1758801600">- pg_config --libs returns -lnuma so we need to require it.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Update to 18.1:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/18.1/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 18.2:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/18.2/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * bsc#1258012, CVE-2026-2007: Harden contrib/pg_trgm against
    changes in string lowercasing behavior.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 18.3 to fix two regressions in 18.2:
  * https://www.postgresql.org/docs/release/18.3/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
</package>
<package pkgid="461fd6cc9b51484417625ce01109b696cc828fefae779ff7a0a57da0ccc796942e2b47fee1d08f69bb471dcdd9c2d4963ac5603ffbd5a629d9e0a27f96c2a82c" name="postgresql18-plpython" arch="x86_64">
  <version epoch="0" ver="18.4" rel="18.3"/>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 17.4:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/17.4/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 17.5:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/17.5/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to Fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1746792001">- Fork package for postgresql 18
  https://www.postgresql.org/about/news/p-3070/</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1753272000">- Update to 18~beta2
  https://www.postgresql.org/about/news/p-3103/</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Update to 18~beta3
  * https://www.postgresql.org/about/news/p-3118/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755518400">- enable liburing and libnuma support
- prepare oauth support. but it creates broken symlinks at the
  moment</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755518401">- In the symlinking loop for *.so files only handle symlinks and
  not also files.
  This allows us to enable oauth support</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755604800">- move libpq-oauth into the libpq5  package. it is a plugin that
  will be loaded via dlopen() if libpq encounters an oauth workflow
  during a connection.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1756987200">- Update to 18 RC1.
  * https://www.postgresql.org/about/news/p-3130/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1758628800">- Update to 18.0.
  * https://www.postgresql.org/about/news/p-3142/
  * https://www.postgresql.org/docs/18/release-18.html</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1758801600">- pg_config --libs returns -lnuma so we need to require it.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Update to 18.1:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/18.1/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 18.2:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/18.2/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * bsc#1258012, CVE-2026-2007: Harden contrib/pg_trgm against
    changes in string lowercasing behavior.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 18.3 to fix two regressions in 18.2:
  * https://www.postgresql.org/docs/release/18.3/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1774526400">- Get rid of update-alternatives for openSUSE/SLE 16.0 and newer
  to support immutable systems and transactional updates.
  (jsc#PED-14820)</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1777550400">- bsc#1263804: After dropping update-alternatives we have to
  package /usr/bin/pg_config as an actual symlink, not %ghost.
- Fix spelling of build conditionals.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1778673600">- Update to version 18.4:
  * bsc#1265172, CVE-2026-6472: ensure the user has CREATE
    privilege on the schema specified
  * bsc#1265173, CVE-2026-6473: integer overflows in
    memory-allocation calculations
  * bsc#1265174, CVE-2026-6474: Guard against malicious time zone
    names
  * bsc#1265175, CVE-2026-6475: Prevent path traversal in
    pg_basebackup and pg_rewind
  * bsc#1265176, CVE-2026-6476: Properly quote subscription names
    in pg_createsubscriber
  * bsc#1265177, CVE-2026-6477: Mark PQfn() as unsafe, and avoid
    using it within libpq
  * bsc#1265178, CVE-2026-6478: Use timing-safe string comparisons
    in authentication code
  * bsc#1265179, CVE-2026-6479: Prevent unbounded recursion while
    processing startup packets
  * bsc#1265180, CVE-2026-6575: Detect faulty input when restoring
    attribute MCV statistics
  * bsc#1265181, CVE-2026-6637: Prevent SQL injection and buffer
    overruns in contrib/spi
  * bsc#1265182, CVE-2026-6638: Properly quote object names in
    logical replication origin checks
  * https://www.postgresql.org/docs/release/18.4/</changelog>
</package>
<package pkgid="ef1763eced89a6b1fe7169e016f03a4e2001dba0c8c97e947bc8e19726934da2ca00cefdbf0b483886177b88ef447b6def64c59d812f686528eab5d74347387c" name="postgresql18-pltcl" arch="s390x">
  <version epoch="0" ver="18.3" rel="2.3"/>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="JS &lt;obs.coke518@passinbox.com&gt;" date="1738152000">- Apply postgresql-tzdata2025a.patch regardless of
  whether LLVM JIT is enabled</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 17.3:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/17.3/
  * https://www.postgresql.org/about/news/-3015/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 17.4:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/17.4/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 17.5:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/17.5/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to Fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1746792001">- Fork package for postgresql 18
  https://www.postgresql.org/about/news/p-3070/</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1753272000">- Update to 18~beta2
  https://www.postgresql.org/about/news/p-3103/</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Update to 18~beta3
  * https://www.postgresql.org/about/news/p-3118/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755518400">- enable liburing and libnuma support
- prepare oauth support. but it creates broken symlinks at the
  moment</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755518401">- In the symlinking loop for *.so files only handle symlinks and
  not also files.
  This allows us to enable oauth support</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755604800">- move libpq-oauth into the libpq5  package. it is a plugin that
  will be loaded via dlopen() if libpq encounters an oauth workflow
  during a connection.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1756987200">- Update to 18 RC1.
  * https://www.postgresql.org/about/news/p-3130/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1758628800">- Update to 18.0.
  * https://www.postgresql.org/about/news/p-3142/
  * https://www.postgresql.org/docs/18/release-18.html</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1758801600">- pg_config --libs returns -lnuma so we need to require it.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Update to 18.1:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/18.1/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 18.2:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/18.2/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * bsc#1258012, CVE-2026-2007: Harden contrib/pg_trgm against
    changes in string lowercasing behavior.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 18.3 to fix two regressions in 18.2:
  * https://www.postgresql.org/docs/release/18.3/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
</package>
<package pkgid="5a7e7a72fa786bd008a6bddb0f5cafa83b0aa962e3878c4be4a40376258a037a8a365981768e1a969f90174c47b5434313d2df4be8d1aa66ea5598430912f5f3" name="postgresql18-pltcl" arch="aarch64">
  <version epoch="0" ver="18.3" rel="3.1"/>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="JS &lt;obs.coke518@passinbox.com&gt;" date="1738152000">- Apply postgresql-tzdata2025a.patch regardless of
  whether LLVM JIT is enabled</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 17.3:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/17.3/
  * https://www.postgresql.org/about/news/-3015/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 17.4:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/17.4/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 17.5:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/17.5/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to Fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1746792001">- Fork package for postgresql 18
  https://www.postgresql.org/about/news/p-3070/</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1753272000">- Update to 18~beta2
  https://www.postgresql.org/about/news/p-3103/</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Update to 18~beta3
  * https://www.postgresql.org/about/news/p-3118/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755518400">- enable liburing and libnuma support
- prepare oauth support. but it creates broken symlinks at the
  moment</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755518401">- In the symlinking loop for *.so files only handle symlinks and
  not also files.
  This allows us to enable oauth support</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755604800">- move libpq-oauth into the libpq5  package. it is a plugin that
  will be loaded via dlopen() if libpq encounters an oauth workflow
  during a connection.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1756987200">- Update to 18 RC1.
  * https://www.postgresql.org/about/news/p-3130/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1758628800">- Update to 18.0.
  * https://www.postgresql.org/about/news/p-3142/
  * https://www.postgresql.org/docs/18/release-18.html</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1758801600">- pg_config --libs returns -lnuma so we need to require it.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Update to 18.1:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/18.1/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 18.2:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/18.2/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * bsc#1258012, CVE-2026-2007: Harden contrib/pg_trgm against
    changes in string lowercasing behavior.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 18.3 to fix two regressions in 18.2:
  * https://www.postgresql.org/docs/release/18.3/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
</package>
<package pkgid="ee52c6946a26cc67694487d6af7a185f520a70eab683ea4e8d146ea208437dfa7b64e42142f582933b5b208d3a0620cf93d8ab65d3e3093c2b141b8982687a85" name="postgresql18-pltcl" arch="ppc64le">
  <version epoch="0" ver="18.3" rel="3.1"/>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="JS &lt;obs.coke518@passinbox.com&gt;" date="1738152000">- Apply postgresql-tzdata2025a.patch regardless of
  whether LLVM JIT is enabled</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 17.3:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/17.3/
  * https://www.postgresql.org/about/news/-3015/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 17.4:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/17.4/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 17.5:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/17.5/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to Fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1746792001">- Fork package for postgresql 18
  https://www.postgresql.org/about/news/p-3070/</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1753272000">- Update to 18~beta2
  https://www.postgresql.org/about/news/p-3103/</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Update to 18~beta3
  * https://www.postgresql.org/about/news/p-3118/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755518400">- enable liburing and libnuma support
- prepare oauth support. but it creates broken symlinks at the
  moment</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755518401">- In the symlinking loop for *.so files only handle symlinks and
  not also files.
  This allows us to enable oauth support</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755604800">- move libpq-oauth into the libpq5  package. it is a plugin that
  will be loaded via dlopen() if libpq encounters an oauth workflow
  during a connection.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1756987200">- Update to 18 RC1.
  * https://www.postgresql.org/about/news/p-3130/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1758628800">- Update to 18.0.
  * https://www.postgresql.org/about/news/p-3142/
  * https://www.postgresql.org/docs/18/release-18.html</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1758801600">- pg_config --libs returns -lnuma so we need to require it.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Update to 18.1:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/18.1/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 18.2:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/18.2/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * bsc#1258012, CVE-2026-2007: Harden contrib/pg_trgm against
    changes in string lowercasing behavior.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 18.3 to fix two regressions in 18.2:
  * https://www.postgresql.org/docs/release/18.3/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
</package>
<package pkgid="cfdc867827b1b7137caab390bb3da92950b5af8a0f30506c44294f4d986f2a1a05bd6db205ee4eca6b713845bc050744b0cea6d235b980ec43cc8077afc0e2e6" name="postgresql18-pltcl" arch="x86_64">
  <version epoch="0" ver="18.4" rel="18.3"/>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 17.4:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/17.4/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 17.5:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/17.5/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to Fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1746792001">- Fork package for postgresql 18
  https://www.postgresql.org/about/news/p-3070/</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1753272000">- Update to 18~beta2
  https://www.postgresql.org/about/news/p-3103/</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Update to 18~beta3
  * https://www.postgresql.org/about/news/p-3118/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755518400">- enable liburing and libnuma support
- prepare oauth support. but it creates broken symlinks at the
  moment</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755518401">- In the symlinking loop for *.so files only handle symlinks and
  not also files.
  This allows us to enable oauth support</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755604800">- move libpq-oauth into the libpq5  package. it is a plugin that
  will be loaded via dlopen() if libpq encounters an oauth workflow
  during a connection.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1756987200">- Update to 18 RC1.
  * https://www.postgresql.org/about/news/p-3130/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1758628800">- Update to 18.0.
  * https://www.postgresql.org/about/news/p-3142/
  * https://www.postgresql.org/docs/18/release-18.html</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1758801600">- pg_config --libs returns -lnuma so we need to require it.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Update to 18.1:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/18.1/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 18.2:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/18.2/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * bsc#1258012, CVE-2026-2007: Harden contrib/pg_trgm against
    changes in string lowercasing behavior.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 18.3 to fix two regressions in 18.2:
  * https://www.postgresql.org/docs/release/18.3/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1774526400">- Get rid of update-alternatives for openSUSE/SLE 16.0 and newer
  to support immutable systems and transactional updates.
  (jsc#PED-14820)</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1777550400">- bsc#1263804: After dropping update-alternatives we have to
  package /usr/bin/pg_config as an actual symlink, not %ghost.
- Fix spelling of build conditionals.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1778673600">- Update to version 18.4:
  * bsc#1265172, CVE-2026-6472: ensure the user has CREATE
    privilege on the schema specified
  * bsc#1265173, CVE-2026-6473: integer overflows in
    memory-allocation calculations
  * bsc#1265174, CVE-2026-6474: Guard against malicious time zone
    names
  * bsc#1265175, CVE-2026-6475: Prevent path traversal in
    pg_basebackup and pg_rewind
  * bsc#1265176, CVE-2026-6476: Properly quote subscription names
    in pg_createsubscriber
  * bsc#1265177, CVE-2026-6477: Mark PQfn() as unsafe, and avoid
    using it within libpq
  * bsc#1265178, CVE-2026-6478: Use timing-safe string comparisons
    in authentication code
  * bsc#1265179, CVE-2026-6479: Prevent unbounded recursion while
    processing startup packets
  * bsc#1265180, CVE-2026-6575: Detect faulty input when restoring
    attribute MCV statistics
  * bsc#1265181, CVE-2026-6637: Prevent SQL injection and buffer
    overruns in contrib/spi
  * bsc#1265182, CVE-2026-6638: Properly quote object names in
    logical replication origin checks
  * https://www.postgresql.org/docs/release/18.4/</changelog>
</package>
<package pkgid="188082873db6bf654731a3c07086dd9d517fc9c088ad78329d8d11ac62d4d11e1f2955f82346c11fe519e80c9cd9755df80916e684c8ed762f6424ca17d64af4" name="postgresql18-server" arch="s390x">
  <version epoch="0" ver="18.3" rel="2.3"/>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="JS &lt;obs.coke518@passinbox.com&gt;" date="1738152000">- Apply postgresql-tzdata2025a.patch regardless of
  whether LLVM JIT is enabled</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 17.3:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/17.3/
  * https://www.postgresql.org/about/news/-3015/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 17.4:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/17.4/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 17.5:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/17.5/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to Fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1746792001">- Fork package for postgresql 18
  https://www.postgresql.org/about/news/p-3070/</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1753272000">- Update to 18~beta2
  https://www.postgresql.org/about/news/p-3103/</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Update to 18~beta3
  * https://www.postgresql.org/about/news/p-3118/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755518400">- enable liburing and libnuma support
- prepare oauth support. but it creates broken symlinks at the
  moment</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755518401">- In the symlinking loop for *.so files only handle symlinks and
  not also files.
  This allows us to enable oauth support</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755604800">- move libpq-oauth into the libpq5  package. it is a plugin that
  will be loaded via dlopen() if libpq encounters an oauth workflow
  during a connection.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1756987200">- Update to 18 RC1.
  * https://www.postgresql.org/about/news/p-3130/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1758628800">- Update to 18.0.
  * https://www.postgresql.org/about/news/p-3142/
  * https://www.postgresql.org/docs/18/release-18.html</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1758801600">- pg_config --libs returns -lnuma so we need to require it.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Update to 18.1:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/18.1/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 18.2:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/18.2/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * bsc#1258012, CVE-2026-2007: Harden contrib/pg_trgm against
    changes in string lowercasing behavior.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 18.3 to fix two regressions in 18.2:
  * https://www.postgresql.org/docs/release/18.3/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
</package>
<package pkgid="0a1ccb9b016db895c312965910cf47b61bf911354cfeac3c6b881607aa1a55ab7b1406de76d3c39c05be4ffa3dc5815f4d766694e901e912735ffe755736cd34" name="postgresql18-server" arch="aarch64">
  <version epoch="0" ver="18.3" rel="3.1"/>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="JS &lt;obs.coke518@passinbox.com&gt;" date="1738152000">- Apply postgresql-tzdata2025a.patch regardless of
  whether LLVM JIT is enabled</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 17.3:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/17.3/
  * https://www.postgresql.org/about/news/-3015/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 17.4:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/17.4/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 17.5:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/17.5/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to Fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1746792001">- Fork package for postgresql 18
  https://www.postgresql.org/about/news/p-3070/</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1753272000">- Update to 18~beta2
  https://www.postgresql.org/about/news/p-3103/</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Update to 18~beta3
  * https://www.postgresql.org/about/news/p-3118/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755518400">- enable liburing and libnuma support
- prepare oauth support. but it creates broken symlinks at the
  moment</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755518401">- In the symlinking loop for *.so files only handle symlinks and
  not also files.
  This allows us to enable oauth support</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755604800">- move libpq-oauth into the libpq5  package. it is a plugin that
  will be loaded via dlopen() if libpq encounters an oauth workflow
  during a connection.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1756987200">- Update to 18 RC1.
  * https://www.postgresql.org/about/news/p-3130/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1758628800">- Update to 18.0.
  * https://www.postgresql.org/about/news/p-3142/
  * https://www.postgresql.org/docs/18/release-18.html</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1758801600">- pg_config --libs returns -lnuma so we need to require it.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Update to 18.1:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/18.1/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 18.2:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/18.2/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * bsc#1258012, CVE-2026-2007: Harden contrib/pg_trgm against
    changes in string lowercasing behavior.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 18.3 to fix two regressions in 18.2:
  * https://www.postgresql.org/docs/release/18.3/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
</package>
<package pkgid="5a6734c42b7275a5d51237d08b20ce9055496be715f909b39ac61d6605af4dba2fc289bb017baabe4e44f493eda307457028504e12bc91ad02959ecddc2f716b" name="postgresql18-server" arch="ppc64le">
  <version epoch="0" ver="18.3" rel="3.1"/>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="JS &lt;obs.coke518@passinbox.com&gt;" date="1738152000">- Apply postgresql-tzdata2025a.patch regardless of
  whether LLVM JIT is enabled</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 17.3:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/17.3/
  * https://www.postgresql.org/about/news/-3015/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 17.4:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/17.4/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 17.5:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/17.5/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to Fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1746792001">- Fork package for postgresql 18
  https://www.postgresql.org/about/news/p-3070/</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1753272000">- Update to 18~beta2
  https://www.postgresql.org/about/news/p-3103/</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Update to 18~beta3
  * https://www.postgresql.org/about/news/p-3118/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755518400">- enable liburing and libnuma support
- prepare oauth support. but it creates broken symlinks at the
  moment</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755518401">- In the symlinking loop for *.so files only handle symlinks and
  not also files.
  This allows us to enable oauth support</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755604800">- move libpq-oauth into the libpq5  package. it is a plugin that
  will be loaded via dlopen() if libpq encounters an oauth workflow
  during a connection.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1756987200">- Update to 18 RC1.
  * https://www.postgresql.org/about/news/p-3130/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1758628800">- Update to 18.0.
  * https://www.postgresql.org/about/news/p-3142/
  * https://www.postgresql.org/docs/18/release-18.html</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1758801600">- pg_config --libs returns -lnuma so we need to require it.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Update to 18.1:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/18.1/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 18.2:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/18.2/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * bsc#1258012, CVE-2026-2007: Harden contrib/pg_trgm against
    changes in string lowercasing behavior.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 18.3 to fix two regressions in 18.2:
  * https://www.postgresql.org/docs/release/18.3/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
</package>
<package pkgid="7ab374f3d8a4a5321f090ce557ee2eff6bf40ee783204c19c81b3b67d95b84a21afd9bb87892433a022a32a2f1b5b0871ef759a14eb6932818538cfe02edd165" name="postgresql18-server" arch="x86_64">
  <version epoch="0" ver="18.4" rel="18.3"/>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 17.4:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/17.4/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 17.5:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/17.5/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to Fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1746792001">- Fork package for postgresql 18
  https://www.postgresql.org/about/news/p-3070/</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1753272000">- Update to 18~beta2
  https://www.postgresql.org/about/news/p-3103/</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Update to 18~beta3
  * https://www.postgresql.org/about/news/p-3118/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755518400">- enable liburing and libnuma support
- prepare oauth support. but it creates broken symlinks at the
  moment</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755518401">- In the symlinking loop for *.so files only handle symlinks and
  not also files.
  This allows us to enable oauth support</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755604800">- move libpq-oauth into the libpq5  package. it is a plugin that
  will be loaded via dlopen() if libpq encounters an oauth workflow
  during a connection.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1756987200">- Update to 18 RC1.
  * https://www.postgresql.org/about/news/p-3130/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1758628800">- Update to 18.0.
  * https://www.postgresql.org/about/news/p-3142/
  * https://www.postgresql.org/docs/18/release-18.html</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1758801600">- pg_config --libs returns -lnuma so we need to require it.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Update to 18.1:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/18.1/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 18.2:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/18.2/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * bsc#1258012, CVE-2026-2007: Harden contrib/pg_trgm against
    changes in string lowercasing behavior.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 18.3 to fix two regressions in 18.2:
  * https://www.postgresql.org/docs/release/18.3/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1774526400">- Get rid of update-alternatives for openSUSE/SLE 16.0 and newer
  to support immutable systems and transactional updates.
  (jsc#PED-14820)</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1777550400">- bsc#1263804: After dropping update-alternatives we have to
  package /usr/bin/pg_config as an actual symlink, not %ghost.
- Fix spelling of build conditionals.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1778673600">- Update to version 18.4:
  * bsc#1265172, CVE-2026-6472: ensure the user has CREATE
    privilege on the schema specified
  * bsc#1265173, CVE-2026-6473: integer overflows in
    memory-allocation calculations
  * bsc#1265174, CVE-2026-6474: Guard against malicious time zone
    names
  * bsc#1265175, CVE-2026-6475: Prevent path traversal in
    pg_basebackup and pg_rewind
  * bsc#1265176, CVE-2026-6476: Properly quote subscription names
    in pg_createsubscriber
  * bsc#1265177, CVE-2026-6477: Mark PQfn() as unsafe, and avoid
    using it within libpq
  * bsc#1265178, CVE-2026-6478: Use timing-safe string comparisons
    in authentication code
  * bsc#1265179, CVE-2026-6479: Prevent unbounded recursion while
    processing startup packets
  * bsc#1265180, CVE-2026-6575: Detect faulty input when restoring
    attribute MCV statistics
  * bsc#1265181, CVE-2026-6637: Prevent SQL injection and buffer
    overruns in contrib/spi
  * bsc#1265182, CVE-2026-6638: Properly quote object names in
    logical replication origin checks
  * https://www.postgresql.org/docs/release/18.4/</changelog>
</package>
<package pkgid="3ae177843159d22fd1e221ed6aa2681176502def8a6dde7c44986807b4e0578b083b69734ea6d25b289358ac2064df6a6951362ab62fadb1f27621b9cc769ca7" name="postgresql18-server-devel" arch="s390x">
  <version epoch="0" ver="18.3" rel="2.3"/>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="JS &lt;obs.coke518@passinbox.com&gt;" date="1738152000">- Apply postgresql-tzdata2025a.patch regardless of
  whether LLVM JIT is enabled</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 17.3:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/17.3/
  * https://www.postgresql.org/about/news/-3015/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 17.4:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/17.4/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 17.5:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/17.5/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to Fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1746792001">- Fork package for postgresql 18
  https://www.postgresql.org/about/news/p-3070/</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1753272000">- Update to 18~beta2
  https://www.postgresql.org/about/news/p-3103/</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Update to 18~beta3
  * https://www.postgresql.org/about/news/p-3118/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755518400">- enable liburing and libnuma support
- prepare oauth support. but it creates broken symlinks at the
  moment</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755518401">- In the symlinking loop for *.so files only handle symlinks and
  not also files.
  This allows us to enable oauth support</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755604800">- move libpq-oauth into the libpq5  package. it is a plugin that
  will be loaded via dlopen() if libpq encounters an oauth workflow
  during a connection.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1756987200">- Update to 18 RC1.
  * https://www.postgresql.org/about/news/p-3130/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1758628800">- Update to 18.0.
  * https://www.postgresql.org/about/news/p-3142/
  * https://www.postgresql.org/docs/18/release-18.html</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1758801600">- pg_config --libs returns -lnuma so we need to require it.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Update to 18.1:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/18.1/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 18.2:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/18.2/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * bsc#1258012, CVE-2026-2007: Harden contrib/pg_trgm against
    changes in string lowercasing behavior.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 18.3 to fix two regressions in 18.2:
  * https://www.postgresql.org/docs/release/18.3/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
</package>
<package pkgid="7f133be597127b65a057de21db919f6cef86284b33fd38034a121b4b8d3a6fdcf6bcfed52681eaf9b5cccdd9018d77a891b3667b5ef9cff3933401b063033eb0" name="postgresql18-server-devel" arch="aarch64">
  <version epoch="0" ver="18.3" rel="3.1"/>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="JS &lt;obs.coke518@passinbox.com&gt;" date="1738152000">- Apply postgresql-tzdata2025a.patch regardless of
  whether LLVM JIT is enabled</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 17.3:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/17.3/
  * https://www.postgresql.org/about/news/-3015/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 17.4:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/17.4/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 17.5:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/17.5/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to Fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1746792001">- Fork package for postgresql 18
  https://www.postgresql.org/about/news/p-3070/</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1753272000">- Update to 18~beta2
  https://www.postgresql.org/about/news/p-3103/</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Update to 18~beta3
  * https://www.postgresql.org/about/news/p-3118/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755518400">- enable liburing and libnuma support
- prepare oauth support. but it creates broken symlinks at the
  moment</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755518401">- In the symlinking loop for *.so files only handle symlinks and
  not also files.
  This allows us to enable oauth support</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755604800">- move libpq-oauth into the libpq5  package. it is a plugin that
  will be loaded via dlopen() if libpq encounters an oauth workflow
  during a connection.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1756987200">- Update to 18 RC1.
  * https://www.postgresql.org/about/news/p-3130/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1758628800">- Update to 18.0.
  * https://www.postgresql.org/about/news/p-3142/
  * https://www.postgresql.org/docs/18/release-18.html</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1758801600">- pg_config --libs returns -lnuma so we need to require it.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Update to 18.1:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/18.1/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 18.2:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/18.2/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * bsc#1258012, CVE-2026-2007: Harden contrib/pg_trgm against
    changes in string lowercasing behavior.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 18.3 to fix two regressions in 18.2:
  * https://www.postgresql.org/docs/release/18.3/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
</package>
<package pkgid="37e54b2ea894b54157e6eb66d9cfc6904982b02cc45b9cb5c208aa87b0962204e5cc9a86b7814170510ed243ba4f7bf0d312fa3af3b2a6db2a87e326a3a5a784" name="postgresql18-server-devel" arch="ppc64le">
  <version epoch="0" ver="18.3" rel="3.1"/>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="JS &lt;obs.coke518@passinbox.com&gt;" date="1738152000">- Apply postgresql-tzdata2025a.patch regardless of
  whether LLVM JIT is enabled</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 17.3:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/17.3/
  * https://www.postgresql.org/about/news/-3015/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 17.4:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/17.4/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 17.5:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/17.5/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to Fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1746792001">- Fork package for postgresql 18
  https://www.postgresql.org/about/news/p-3070/</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1753272000">- Update to 18~beta2
  https://www.postgresql.org/about/news/p-3103/</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Update to 18~beta3
  * https://www.postgresql.org/about/news/p-3118/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755518400">- enable liburing and libnuma support
- prepare oauth support. but it creates broken symlinks at the
  moment</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755518401">- In the symlinking loop for *.so files only handle symlinks and
  not also files.
  This allows us to enable oauth support</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755604800">- move libpq-oauth into the libpq5  package. it is a plugin that
  will be loaded via dlopen() if libpq encounters an oauth workflow
  during a connection.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1756987200">- Update to 18 RC1.
  * https://www.postgresql.org/about/news/p-3130/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1758628800">- Update to 18.0.
  * https://www.postgresql.org/about/news/p-3142/
  * https://www.postgresql.org/docs/18/release-18.html</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1758801600">- pg_config --libs returns -lnuma so we need to require it.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Update to 18.1:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/18.1/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 18.2:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/18.2/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * bsc#1258012, CVE-2026-2007: Harden contrib/pg_trgm against
    changes in string lowercasing behavior.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 18.3 to fix two regressions in 18.2:
  * https://www.postgresql.org/docs/release/18.3/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
</package>
<package pkgid="6efdd3a25884e0fe0c8cbac5cebafa95291e8c33ebe3c0063b2435a4ec600feac6cd8a887734604092118e9b70d2af8b667e9f0a565a3cb795e95eb21773267e" name="postgresql18-server-devel" arch="x86_64">
  <version epoch="0" ver="18.4" rel="18.3"/>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 17.4:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/17.4/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 17.5:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/17.5/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to Fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1746792001">- Fork package for postgresql 18
  https://www.postgresql.org/about/news/p-3070/</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1753272000">- Update to 18~beta2
  https://www.postgresql.org/about/news/p-3103/</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Update to 18~beta3
  * https://www.postgresql.org/about/news/p-3118/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755518400">- enable liburing and libnuma support
- prepare oauth support. but it creates broken symlinks at the
  moment</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755518401">- In the symlinking loop for *.so files only handle symlinks and
  not also files.
  This allows us to enable oauth support</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755604800">- move libpq-oauth into the libpq5  package. it is a plugin that
  will be loaded via dlopen() if libpq encounters an oauth workflow
  during a connection.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1756987200">- Update to 18 RC1.
  * https://www.postgresql.org/about/news/p-3130/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1758628800">- Update to 18.0.
  * https://www.postgresql.org/about/news/p-3142/
  * https://www.postgresql.org/docs/18/release-18.html</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1758801600">- pg_config --libs returns -lnuma so we need to require it.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Update to 18.1:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/18.1/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 18.2:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/18.2/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * bsc#1258012, CVE-2026-2007: Harden contrib/pg_trgm against
    changes in string lowercasing behavior.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 18.3 to fix two regressions in 18.2:
  * https://www.postgresql.org/docs/release/18.3/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1774526400">- Get rid of update-alternatives for openSUSE/SLE 16.0 and newer
  to support immutable systems and transactional updates.
  (jsc#PED-14820)</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1777550400">- bsc#1263804: After dropping update-alternatives we have to
  package /usr/bin/pg_config as an actual symlink, not %ghost.
- Fix spelling of build conditionals.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1778673600">- Update to version 18.4:
  * bsc#1265172, CVE-2026-6472: ensure the user has CREATE
    privilege on the schema specified
  * bsc#1265173, CVE-2026-6473: integer overflows in
    memory-allocation calculations
  * bsc#1265174, CVE-2026-6474: Guard against malicious time zone
    names
  * bsc#1265175, CVE-2026-6475: Prevent path traversal in
    pg_basebackup and pg_rewind
  * bsc#1265176, CVE-2026-6476: Properly quote subscription names
    in pg_createsubscriber
  * bsc#1265177, CVE-2026-6477: Mark PQfn() as unsafe, and avoid
    using it within libpq
  * bsc#1265178, CVE-2026-6478: Use timing-safe string comparisons
    in authentication code
  * bsc#1265179, CVE-2026-6479: Prevent unbounded recursion while
    processing startup packets
  * bsc#1265180, CVE-2026-6575: Detect faulty input when restoring
    attribute MCV statistics
  * bsc#1265181, CVE-2026-6637: Prevent SQL injection and buffer
    overruns in contrib/spi
  * bsc#1265182, CVE-2026-6638: Properly quote object names in
    logical replication origin checks
  * https://www.postgresql.org/docs/release/18.4/</changelog>
</package>
<package pkgid="8828f494f87897aa5ba53343d5bb77e4a1027dca0b116d1c96436f311ad4a26c10c727e6695dadf1f885660077b4fec6f2dfe2572ca760e2db0298fd423a1cb0" name="postgresql18-test" arch="s390x">
  <version epoch="0" ver="18.3" rel="2.3"/>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="JS &lt;obs.coke518@passinbox.com&gt;" date="1738152000">- Apply postgresql-tzdata2025a.patch regardless of
  whether LLVM JIT is enabled</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 17.3:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/17.3/
  * https://www.postgresql.org/about/news/-3015/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 17.4:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/17.4/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 17.5:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/17.5/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to Fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1746792001">- Fork package for postgresql 18
  https://www.postgresql.org/about/news/p-3070/</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1753272000">- Update to 18~beta2
  https://www.postgresql.org/about/news/p-3103/</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Update to 18~beta3
  * https://www.postgresql.org/about/news/p-3118/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755518400">- enable liburing and libnuma support
- prepare oauth support. but it creates broken symlinks at the
  moment</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755518401">- In the symlinking loop for *.so files only handle symlinks and
  not also files.
  This allows us to enable oauth support</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755604800">- move libpq-oauth into the libpq5  package. it is a plugin that
  will be loaded via dlopen() if libpq encounters an oauth workflow
  during a connection.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1756987200">- Update to 18 RC1.
  * https://www.postgresql.org/about/news/p-3130/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1758628800">- Update to 18.0.
  * https://www.postgresql.org/about/news/p-3142/
  * https://www.postgresql.org/docs/18/release-18.html</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1758801600">- pg_config --libs returns -lnuma so we need to require it.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Update to 18.1:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/18.1/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 18.2:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/18.2/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * bsc#1258012, CVE-2026-2007: Harden contrib/pg_trgm against
    changes in string lowercasing behavior.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 18.3 to fix two regressions in 18.2:
  * https://www.postgresql.org/docs/release/18.3/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
</package>
<package pkgid="2a1bdd32353a6dda3d639805ad3c20e7c5c0b9d80630ff7b655ae7b76e11e8428d694dc271a4db10f09f7504c8f9e86b739695dc2efe4613a696618f4d17c6df" name="postgresql18-test" arch="aarch64">
  <version epoch="0" ver="18.3" rel="3.1"/>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="JS &lt;obs.coke518@passinbox.com&gt;" date="1738152000">- Apply postgresql-tzdata2025a.patch regardless of
  whether LLVM JIT is enabled</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 17.3:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/17.3/
  * https://www.postgresql.org/about/news/-3015/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 17.4:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/17.4/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 17.5:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/17.5/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to Fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1746792001">- Fork package for postgresql 18
  https://www.postgresql.org/about/news/p-3070/</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1753272000">- Update to 18~beta2
  https://www.postgresql.org/about/news/p-3103/</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Update to 18~beta3
  * https://www.postgresql.org/about/news/p-3118/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755518400">- enable liburing and libnuma support
- prepare oauth support. but it creates broken symlinks at the
  moment</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755518401">- In the symlinking loop for *.so files only handle symlinks and
  not also files.
  This allows us to enable oauth support</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755604800">- move libpq-oauth into the libpq5  package. it is a plugin that
  will be loaded via dlopen() if libpq encounters an oauth workflow
  during a connection.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1756987200">- Update to 18 RC1.
  * https://www.postgresql.org/about/news/p-3130/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1758628800">- Update to 18.0.
  * https://www.postgresql.org/about/news/p-3142/
  * https://www.postgresql.org/docs/18/release-18.html</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1758801600">- pg_config --libs returns -lnuma so we need to require it.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Update to 18.1:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/18.1/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 18.2:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/18.2/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * bsc#1258012, CVE-2026-2007: Harden contrib/pg_trgm against
    changes in string lowercasing behavior.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 18.3 to fix two regressions in 18.2:
  * https://www.postgresql.org/docs/release/18.3/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
</package>
<package pkgid="04d4135489a029bda9816c0634a6786e967a827145a6211e6a3ae9b049403001b0dbb4c5df9a14536d4d789cf3eb23097e31ccc6fc8fc044bfccda12464adf80" name="postgresql18-test" arch="ppc64le">
  <version epoch="0" ver="18.3" rel="3.1"/>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1738065600">- Fix build, add postgresql-tzdata2025a.patch</changelog>
  <changelog author="JS &lt;obs.coke518@passinbox.com&gt;" date="1738152000">- Apply postgresql-tzdata2025a.patch regardless of
  whether LLVM JIT is enabled</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739275200">- Upgrade to 17.3:
  * bsc#1237093, CVE-2025-1094: Harden PQescapeString and allied
    functions against invalidly-encoded input strings.
  * obsoletes postgresql-tzdata2025a.patch
  * https://www.postgresql.org/docs/release/17.3/
  * https://www.postgresql.org/about/news/-3015/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 17.4:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/17.4/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 17.5:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/17.5/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to Fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1746792001">- Fork package for postgresql 18
  https://www.postgresql.org/about/news/p-3070/</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1753272000">- Update to 18~beta2
  https://www.postgresql.org/about/news/p-3103/</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Update to 18~beta3
  * https://www.postgresql.org/about/news/p-3118/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755518400">- enable liburing and libnuma support
- prepare oauth support. but it creates broken symlinks at the
  moment</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755518401">- In the symlinking loop for *.so files only handle symlinks and
  not also files.
  This allows us to enable oauth support</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755604800">- move libpq-oauth into the libpq5  package. it is a plugin that
  will be loaded via dlopen() if libpq encounters an oauth workflow
  during a connection.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1756987200">- Update to 18 RC1.
  * https://www.postgresql.org/about/news/p-3130/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1758628800">- Update to 18.0.
  * https://www.postgresql.org/about/news/p-3142/
  * https://www.postgresql.org/docs/18/release-18.html</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1758801600">- pg_config --libs returns -lnuma so we need to require it.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Update to 18.1:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/18.1/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 18.2:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/18.2/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * bsc#1258012, CVE-2026-2007: Harden contrib/pg_trgm against
    changes in string lowercasing behavior.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 18.3 to fix two regressions in 18.2:
  * https://www.postgresql.org/docs/release/18.3/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
</package>
<package pkgid="c51b22d1afa05eccc1a1371a1037fcf519deb9fc50888f8f04c988e3c70be94164b8b579335868ec0a5a0ad966cc9021e55966defe5f6233af19971f42debc19" name="postgresql18-test" arch="x86_64">
  <version epoch="0" ver="18.4" rel="18.3"/>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1739880000">- Upgrade to 17.4:
  * Improve behavior of libpq's quoting functions:
    The changes made for CVE-2025-1094 had one serious oversight:
    PQescapeLiteral() and PQescapeIdentifier() failed to honor
    their string length parameter, instead always reading to the
    input string's trailing null. This resulted in including
    unwanted text in the output, if the caller intended to
    truncate the string via the length parameter. With very bad
    luck it could cause a crash due to reading off the end of
    memory.
    In addition, modify all these quoting functions so that when
    invalid encoding is detected, an invalid sequence is
    substituted for just the first byte of the presumed
    character, not all of it. This reduces the risk of problems
    if a calling application performs additional processing on
    the quoted string.
  * Fix small memory leak in pg_createsubscriber.
  * https://www.postgresql.org/docs/release/17.4/
  * https://www.postgresql.org/about/news/p-3018/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1746792000">- Upgrade to 17.5:
  * bsc#1242931, CVE-2025-4207: postgresql: PostgreSQL GB18030
    encoding validation can read one byte past end of allocation
    for text that fails validation.
  * https://www.postgresql.org/docs/release/17.5/
  * https://www.postgresql.org/about/news/p-3072/
- Add postresql-pg_config_paths.patch to Fix a race condition
  while generating pg_config_paths.h.</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1746792001">- Fork package for postgresql 18
  https://www.postgresql.org/about/news/p-3070/</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1753272000">- Update to 18~beta2
  https://www.postgresql.org/about/news/p-3103/</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755172800">- Update to 18~beta3
  * https://www.postgresql.org/about/news/p-3118/
  Security Issues
  * CVE-2025-8713: PostgreSQL optimizer statistics can expose
    sampled data within a view, partition, or child table
    (boo#1248120)
  * CVE-2025-8714: PostgreSQL pg_dump lets superuser of origin
    server execute arbitrary code in psql client (boo#1248122)
  * CVE-2025-8715: PostgreSQL pg_dump newline in object name
    executes arbitrary code in psql client and in restore target
    server (boo#1248119)</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755518400">- enable liburing and libnuma support
- prepare oauth support. but it creates broken symlinks at the
  moment</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755518401">- In the symlinking loop for *.so files only handle symlinks and
  not also files.
  This allows us to enable oauth support</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1755604800">- move libpq-oauth into the libpq5  package. it is a plugin that
  will be loaded via dlopen() if libpq encounters an oauth workflow
  during a connection.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1756987200">- Update to 18 RC1.
  * https://www.postgresql.org/about/news/p-3130/</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1758628800">- Update to 18.0.
  * https://www.postgresql.org/about/news/p-3142/
  * https://www.postgresql.org/docs/18/release-18.html</changelog>
  <changelog author="Marcus Rueckert &lt;mrueckert@suse.de&gt;" date="1758801600">- pg_config --libs returns -lnuma so we need to require it.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1762948800">- Update to 18.1:
  * https://www.postgresql.org/about/news/p-3171/
  * https://www.postgresql.org/docs/release/18.1/
  * bsc#1253332, CVE-2025-12817: Missing check for CREATE
    privileges on the schema in CREATE STATISTICS allowed table
    owners to create statistics in any schema, potentially leading
    to unexpected naming conflicts.
  * bsc#1253333, CVE-2025-12818: Several places in libpq were not
    sufficiently careful about computing the required size of a
    memory allocation. Sufficiently large inputs could cause
    integer overflow, resulting in an undersized buffer, which
    would then lead to writing past the end of the buffer.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763121600">- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1763985600">- Fix build with uring for post SLE15 code streams.</changelog>
  <changelog author="Guillaume GARDET &lt;guillaume.gardet@opensuse.org&gt;" date="1765281600">- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1770811200">- Update to 18.2:
  * https://www.postgresql.org/about/news/p-3235/
  * https://www.postgresql.org/docs/release/18.2/
  * bsc#1258008, CVE-2026-2003: Guard against unexpected
    dimensions of oidvector/int2vector
  * bsc#1258009, CVE-2026-2004: Harden selectivity estimators
    against being attached to operators that accept unexpected
    data types.
  * bsc#1258010, CVE-2026-2005: Fix buffer overrun in
    contrib/pgcrypto's PGP decryption functions.
  * bsc#1258011, CVE-2026-2006: Fix inadequate validation of
    multibyte character lengths.
  * bsc#1258012, CVE-2026-2007: Harden contrib/pg_trgm against
    changes in string lowercasing behavior.
  * obsoletes llvm-21-aarch64.patch
- Disown /var/lib/pgsql to support transactional updates.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1771934400">- bsc#1258754: Update to 18.3 to fix two regressions in 18.2:
  * https://www.postgresql.org/docs/release/18.3/
  * The substring() function raises an error "invalid byte sequence
    for encoding" on non-ASCII text values if the source of
    that value is a database column.
  * A standby may halt and return an error "could not access status
    of transaction".</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1774526400">- Get rid of update-alternatives for openSUSE/SLE 16.0 and newer
  to support immutable systems and transactional updates.
  (jsc#PED-14820)</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1777550400">- bsc#1263804: After dropping update-alternatives we have to
  package /usr/bin/pg_config as an actual symlink, not %ghost.
- Fix spelling of build conditionals.</changelog>
  <changelog author="Reinhard Max &lt;max@suse.com&gt;" date="1778673600">- Update to version 18.4:
  * bsc#1265172, CVE-2026-6472: ensure the user has CREATE
    privilege on the schema specified
  * bsc#1265173, CVE-2026-6473: integer overflows in
    memory-allocation calculations
  * bsc#1265174, CVE-2026-6474: Guard against malicious time zone
    names
  * bsc#1265175, CVE-2026-6475: Prevent path traversal in
    pg_basebackup and pg_rewind
  * bsc#1265176, CVE-2026-6476: Properly quote subscription names
    in pg_createsubscriber
  * bsc#1265177, CVE-2026-6477: Mark PQfn() as unsafe, and avoid
    using it within libpq
  * bsc#1265178, CVE-2026-6478: Use timing-safe string comparisons
    in authentication code
  * bsc#1265179, CVE-2026-6479: Prevent unbounded recursion while
    processing startup packets
  * bsc#1265180, CVE-2026-6575: Detect faulty input when restoring
    attribute MCV statistics
  * bsc#1265181, CVE-2026-6637: Prevent SQL injection and buffer
    overruns in contrib/spi
  * bsc#1265182, CVE-2026-6638: Properly quote object names in
    logical replication origin checks
  * https://www.postgresql.org/docs/release/18.4/</changelog>
</package>
</otherdata>