postgresql16-16.15-150600.16.38.1

- llvmjit-devel: require the main clang and llvm packages again
  instead of their -devel packages.

- Let llvmjit-devel require the llc and clang binaries to fix
  build of extensions on SLE-16 and newer.
- Use LLVM 15 on SLE-15 up to SP5 and LLVM 17 on SP6 and SP7.

- Update to version 16.15:
  https://www.postgresql.org/docs/16/release-16-15.html
  https://www.postgresql.org/about/news/postgresql-186-1711-1615-1519-1424-and-19-beta-3-released-3365/
  Security Fixes:
  - bsc#1275046, CVE-2026-6464: psql COPY FROM STDIN early failure
    processes data lines as psql commands (CVSS v3.1: 8.1)
  - bsc#1275044, CVE-2026-6469: ALTER TABLE ALTER TYPE resets
    extended statistics ownership (CVSS v3.1: 3.8)
  - bsc#1275043, CVE-2026-6470: Fails to check type USAGE privilege
    (CVSS v3.1: 4.3)
  - bsc#1275042, CVE-2026-6471: Logical decoding can dlopen
    arbitrary file (CVSS v3.1: 7.2)
  - bsc#1275001, CVE-2026-14662: tsvector and tsquery undersize
    allocations, via integer wraparound (CVSS v3.1: 8.8)
  - bsc#1275002, CVE-2026-14663: pgcrypto, for OpenSSL-disabled
    ciphers, silently encrypts to and decrypts from cleartext (CVSS
    v3.1: 6.5)
  - bsc#1275068, CVE-2026-14664: Regexp heap buffer overflow
    executes arbitrary code (CVSS v3.1: 8.8)
  - bsc#1275067, CVE-2026-14666: Row security caching disregards
    role modifications (CVSS v3.1: 4.2)
  - bsc#1275066, CVE-2026-14668: ctid type confusion in selectivity
    estimator discloses derivative of arbitrary read (CVSS v3.1:
    8.1)
  - bsc#1275065, CVE-2026-14669: to_char heap buffer overflow
    executes arbitrary code (CVSS v3.1: 8.8)
  - bsc#1275064, CVE-2026-14670: plperl tied object heap buffer
    overflow executes arbitrary code (CVSS v3.1: 8.8)
  - bsc#1275063, CVE-2026-14671: refint plan cache type confusion
    executes arbitrary code (CVSS v3.1: 8.8)
  - bsc#1275062, CVE-2026-14672: Observable response discrepancy
    with non-default scram_iterations provides user existence
    oracle (CVSS v3.1: 5.3)
  - bsc#1275061, CVE-2026-14673: amcheck does not clear untrusted
    search path (CVSS v3.1: 3.8)
  - bsc#1275059, CVE-2026-14677: 32-bit pltcl and plperl undersize
    allocations, via integer wraparound (CVSS v3.1: 8.8)
  - bsc#1275058, CVE-2026-14678: pg_trgm picksplit reads past end
    of buffer (CVSS v3.1: 4.3)
  - bsc#1275057, CVE-2026-14679: Stack buffer overflow in argument
    match writes 0x0 and 0x1 to server memory (CVSS v3.1: 8.2)
  - bsc#1275056, CVE-2026-14680: Type confusion via "internal"
    arguments (CVSS v3.1: 8.8)
  - bsc#1275054, CVE-2026-15741: Expression deparse allows SQL
    injection via EXTRACT argument (CVSS v3.1: 8.8)
  - bsc#1275053, CVE-2026-15742: fuzzystrmatch writes
    effectively-arbitrary addresses, via integer wraparound (CVSS
    v3.1: 8.8)
  - bsc#1275051, CVE-2026-16239: Type confusion in cursor CLOSE +
    DECLARE executes arbitrary code (CVSS v3.1: 8.8)
  - bsc#1275050, CVE-2026-16241: ECPG integer underflow can crash
    the client (CVSS v3.1: 3.8)
  - bsc#1275049, CVE-2026-18024: ascii() function reads past end of
    buffer (CVSS v3.1: 4.3)
  - bsc#1275048, CVE-2026-18408: psql \unrestrict lets superuser of
    pg_dump origin server execute arbitrary code in psql client
    (CVSS v3.1: 8.8)
  - bsc#1275047, CVE-2026-19385: pg_dump heap buffer overflow
    executes arbitrary code (CVSS v3.1: 8.8)

- Require clang/llvm-devel metapackages instead of directly
  requiring the latest version. With clang migrating away from
  update-alternatives, the versioned packages no longer provide the
  /usr/bin/clang symlink, which will now be contained in the
  metapackage only. If older LLVM versions are required, the
  compiler binary has to be provided via CLANG=clang-<N>.

- 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/

- 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.

- Get rid of update-alternatives for openSUSE/SLE 16.0 and newer
  to support immutable systems and transactional updates.
  (jsc#PED-14824)

- 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".

- 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.

- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch

- Fix build on aarch64 with upstream commit 0dceba2:
  * llvm-21-aarch64.patch

- Fix build with uring for post SLE15 code streams.

- Use %product_libs_llvm_ver to determine the LLVM version.
- Remove conditionals for obsolete PostgreSQL releases.

- 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.

- Sync spec file from version 18.

- 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)

- Upgrade to 16.1:
  * bsc#1216962, CVE-2023-5868: Fix handling of unknown-type
    arguments in DISTINCT "any" aggregate functions. This error led
    to a text-type value being interpreted as an unknown-type value
    (that is, a zero-terminated string) at runtime. This could
    result in disclosure of server memory following the text value.
  * bsc#1216961, CVE-2023-5869: Detect integer overflow while
    computing new array dimensions. When assigning new elements to
    array subscripts that are outside the current array bounds, an
    undetected integer overflow could occur in edge cases. Memory
    stomps that are potentially exploitable for arbitrary code
    execution are possible, and so is disclosure of server memory.
  * bsc#1216960, CVE-2023-5870: Prevent the pg_signal_backend role
    from signalling background workers and autovacuum processes.
    The documentation says that pg_signal_backend cannot issue
    signals to superuser-owned processes. It was able to signal
    these background  processes, though, because they advertise a
    role OID of zero. Treat that as indicating superuser ownership.
    The security implications of cancelling one of these process
    types are fairly small so far as the core code goes (we'll just
    start another one), but extensions might add background workers
    that are more vulnerable.
    Also ensure that the is_superuser parameter is set correctly in
    such processes. No specific security consequences are known for
    that oversight, but it might be significant for some extensions.
  * Add support for LLVM 16 and 17
  * https://www.postgresql.org/docs/16/release-16-1.html

- boo#1216734: Revert the last change and make the devel package
  independend of all other subpackages except for the libs.

- boo#1216022: Call install-alternatives from the devel subpackage
  as well, otherwise the symlink for ecpg might be missing.

- Also buildignore the postgresql*-implementation symbols: this is
  needed in order to bootstrap when no postgresql version currently
  has valid symbols provided. Once the packages are built, OBS
  could translate this to the pgname-* packages and accept the
  ignores; during bootstrap though, there is nothing providing the
  symbol and the existing buildignores do not suffice.

- Upgrade to 16.0:
  * https://www.postgresql.org/about/news/2715
  * https://www.postgresql.org/docs/16/release-16.html

- Upgrade to 16rc1:
  * https://www.postgresql.org/about/news/2702/

- Upgrade too v16beta3.

- Copy postgresql15 to postgresql16 and upgrade to v16beta2.
- Don't create a unix domain socket under /tmp anymore.

- Restore the independence of mini builds from the main build after
  the -mini name change from April 4, 2023.
- Adjust icu handling to prepare for PostgreSQL 16.

- Overhaul postgresql-README.SUSE and move it from the binary
  package to the noarch wrapper package.
- Change the unix domain socket location from /var/run to /run.

- Update to 15.3:
  * bsc#1211228, CVE-2023-2454:
    Prevent CREATE SCHEMA from defeating changes in search_path
  * bsc#1211229, CVE-2023-2455: Enforce row-level security
    policies correctly after inlining a set-returning function
  * https://www.postgresql.org/about/news/2637/
  * https://www.postgresql.org/docs/15/release-15-3.html

- bsc#1210303: Stop using the obsolete internal %_restart_on_update
  macro and drop support for sysv init to simplify the scriptlets.

- Include -mini in Name: to avoid conflicts in the source package
  name and OBS internal dependency tracking.

- Update to 15.2:
  * CVE-2022-41862, bsc#1208102: memory leak in libpq
  * https://www.postgresql.org/about/news/2592/
  * https://www.postgresql.org/docs/15/release-15-2.html
- Bump latest_supported_llvm_ver to 15.

- Update to 15.1:
  * https://www.postgresql.org/about/news/2543/
  * https://www.postgresql.org/docs/15/release-15-1.html

- Update to 15.0:
  * https://www.postgresql.org/about/news/p-2526/
  * https://www.postgresql.org/docs/15/release-15.html
- Move pg_upgrade from *-contrib to *-server.
- Drop support for the 9.x versioning scheme.

- Update to 15~rc2
  * https://www.postgresql.org/about/news/p-2521/
  * Reverting the "optimized order of GROUP BY keys" feature.

- Fix source URLs

- Update to 15~rc1
  https://www.postgresql.org/about/news/p-2516/

- Create mechanism to specify the latest supported LLVM version.
  Automatically pin to that version if the distribution has a newer
  unsupported default version.