postgresql18-timescaledb-2.24.0-bp157.2.5.1

- Update to version 2.24.0
  This release contains performance improvements and bug fixes
  since the 2.23.1 release. We recommend that you upgrade at the
  next available opportunity.
  Highlighted features in TimescaleDB v2.24.0
  - Direct Compress just got smarter and faster: it now works
    seamlessly with hypertables generating continuous aggregates.
    Invalidation ranges are computed directly in-memory based on
    the ingested batches and written efficiently at transaction
    commit. This change reduces the IO footprint drastically by
    removing the write amplification of the invalidation logs.
  - Continuous aggregates now speak UUIDv7: hypertables partitioned
    by UUIDv7 are fully supported through an enhanced time_bucket
    that accepts UUIDv7 values and returns precise, timezone-aware
    timestamps — unlocking powerful time-series analytics on modern
    UUID-driven table schemas.
  - Lightning-fast recompression: the new recompress := true option
    on the compress_chunk API enables pure in-memory recompression,
    delivering a 4–5× speed boost over the previous disk-based
    process.
  ARM support for bloom filters
  The sparse bloom filter indexes will stop working after upgrade
  to 2.24. If you are affected by this problem, the warning "bloom
  filter sparse indexes require action to re-enable" will appear in
  the Postgres log during upgrade.
  In versions before 2.24, the hashing scheme of the bloom filter
  sparse indexes used to depend on the build options of the
  TimescaleDB executables. These options are set by the package
  publishers and might differ between different package sources or
  even versions. After upgrading to a version with different
  options, the queries that use the bloom filter lookups could
  erroneously stop returning the rows that should in fact match the
  query conditions. The 2.24 release fixes this by using distinct
  column names for each hashing scheme.
  The bloom filter sparse indexes will be disabled on the
  compressed chunks created before upgrading to 2.24. To re-enable
  them, you have to decompress and then compress the affected
  chunks.
  If you were running the official APT package on AMD64
  architecture, the hashing scheme did not change, and it is safe
  to use the existing bloom filter sparse indexes. To enable this,
  set the GUC timescaledb.read_legacy_bloom1_v1 = on in the server
  configuration.
  The chunks compressed after upgrade to 2.24 will use the new
  index format, and the bloom filter sparse indexes will continue
  working as usual for these chunks without any intervention.
  For more details, refer to the pull request #8761.
  - Deprecations
  - The next release of TimescaleDB will remove the deprecated
    partial continuous aggregates format. The new format was
    introduced in 2.7.0 and provides significant improvements in
    terms of performance and storage efficiency. Please use
    cagg_migrate(<CONTINUOUS_AGGREGATE_NAME>) to migrate to the
    new format. Tiger Cloud users are migrated automatically.
  - In future releases the deprecated view
    timescaledb_information.compression_settings will be removed.
    Please use
    timescaledb_information.hypertable_columnstore_settings as a
    replacement.
  - The experimental view timescaledb_experimental.policies and
    the adjacent experimental functions add_policies,
    alter_policies, show_policies, remove_policies, and
    remove_all_policies to manage continuous aggregates will be
    removed in an upcoming release. For replacements, please use
    the Jobs API.
  - Backward-Incompatible Changes
  - #8761 Fix matching rows in queries using the bloom filter
    sparse indexes potentially not returned after extension
    upgrade. The version of the bloom filter sparse indexes is
    changed. The existing indexes will stop working and will
    require action to re-enable. See the section above for
    details.
  - Features
  - #8465 Speed up the filters like x = any(array[...]) using
    bloom filter sparse indexes.
  - #8569 In-memory recompression
  - #8754 Add concurrent mode for merging chunks
  - #8786 Display chunks view range as timestamps for UUIDv7
  - #8819 Refactor chunk compression logic
  - #8840 Allow ALTER COLUMN TYPE when compression is enabled but
    no compressed chunks exist
  - #8908 Add time bucketing support for UUIDv7
  - #8909 Support direct compress on hypertables with continuous
    aggregates
  - #8939 Support continuous aggregates on UUIDv7-partitioned
    hypertables
  - #8959 Cap continuous aggregate invalidation interval range at
    chunk boundary
  - #8975 Exclude date/time columns from default segmentby
  - #8993 Add GUC for in-memory recompression
  - Bugfixes
  - #8839 Improve _timescaledb_functions.cagg_watermark error
    handling
  - #8853 Change log level of continuous aggregate refresh
    messages to DEBUG1
  - #8933 Potential crash or seemingly random errors when
    querying the compressed chunks created on releases before
    2.15 and using the minmax sparse indexes.
  - #8942 Fix lateral join handling for compressed chunks
  - #8958 Fix if_not_exists behaviour when adding refresh policy
  - #8969 Gracefully handle missing job stat in background worker
  - #8988 Don't ignore additional filters on same column when
    building scankeys
  - GUCs
  - direct_compress_copy_tuple_sort_limit: Number of tuples that
    can be sorted at once in a COPY operation.
  - direct_compress_insert_tuple_sort_limit: Number of tuples
    that can be sorted at once in an INSERT operation.
  - read_legacy_bloom1_v1: Enable reading the legacy bloom1
    version 1 sparse indexes for SELECT queries.
  - enable_in_memory_recompression: Enable in-memory
    recompression functionality.

- Update to version 2.23.1
  - #8873 Don't error on failure to update job stats
  - #8875 Fix decoding of UUID v7 timestamp microseconds
  - #8879 Fix blocker for multiple hierarchical continuous
    aggregate policies
  - #8882 Fix crash in policy creation

- Update to version 2.23.0
  This release contains performance improvements and bug fixes
  since the 2.22.1 release. We recommend that you upgrade at the
  next available opportunity.
  Highlighted features in TimescaleDB v2.23.0
  - This release introduces full PostgreSQL 18 support for all
    existing features. TimescaleDB v2.23 is available for
    PostgreSQL 15, 16, 17, and 18.
  - UUIDv7 compression is now enabled by default on the
    columnstore. This feature was shipped in v2.22.0. It saves you
    at least 30% of storage and delivers ~2× faster query
    performance with UUIDv7 columns in the filter conditions.
  - Added the ability to set hypertables to unlogged, addressing an
    open community request #836. This allows the tradeoff between
    durability and performance, with the latter being favourable
    for larger imports.
  - By allowing set-returning functions in continuous aggregates,
    this releases addresses a long standing blocker, raised by the
    community #1717.
  PostgreSQL 15 deprecation announcement
  - We will continue supporting PostgreSQL 15 until June 2026.
    Closer to that time, we will announce the specific TimescaleDB
    version in which PostgreSQL 15 support will not be included
    going forward.
  https://github.com/timescale/timescaledb/releases/tag/2.23.0
- enable building for pg18

- Update to version 2.22.1
  https://github.com/timescale/timescaledb/releases/tag/2.22.1

- Update to version 2.22.0
  https://github.com/timescale/timescaledb/releases/tag/2.22.0

- Update to version 2.21.3
  https://github.com/timescale/timescaledb/releases/tag/2.21.3

- Update to version 2.21.2
  https://github.com/timescale/timescaledb/releases/tag/2.21.2

- Update to version 2.21.1
  https://github.com/timescale/timescaledb/releases/tag/2.21.1

- Update to version 2.21.0
  https://github.com/timescale/timescaledb/releases/tag/2.21.0
  This release contains performance improvements and bug fixes
  since the 2.20.3 release. We recommend that you upgrade at the
  next available opportunity.
  Highlighted features in TimescaleDB v2.21.0
  - The attach & detach chunks feature allows manually adding or
    removing chunks from a hypertable with uncompressed chunks,
    similar to PostgreSQL’s partition management.
  - Continued improvement of backfilling into the columnstore,
    achieving up to 2.5x speedup for constrained tables, by
    introducing caching logic that boosts throughput for writes to
    compressed chunks, bringing INSERT performance close to that of
    uncompressed chunks.
  - Optimized DELETE operations on the columstore through
    batch-level deletions of non-segmentby keys in the filter
    condition, greatly improving performance to up to 42x faster in
    some cases, as well as reducing bloat, and lowering resource
    usage.
  - The heavy lock taken in Continuous Aggregate refresh was
    relaxed, enabling concurrent refreshes for non-overlapping
    ranges and eliminating the need for complex customer
    workarounds.
  - [tech preview] Direct Compress is an innovative TimescaleDB
    feature that improves high-volume data ingestion by compressing
    data in memory and writing it directly to disk, reducing I/O
    overhead, eliminating dependency on background compression
    jobs, and significantly boosting insert performance.
  Sunsetting of the hypercore access method
  We made the decision to deprecate hypercore access method (TAM)
  with the 2.21.0 release. It was an experiment, which did not show
  the signals we hoped for and will be sunsetted in TimescaleDB
  2.22.0, scheduled for September 2025. Upgrading to 2.22.0 and
  higher will be blocked if TAM is still in use. Since TAM’s
  inception in 2.18.0, we learned that btrees were not the right
  architecture. The recent advancements in the columnstore—such as
  more performant backfilling, SkipScan, adding check constraints,
  and faster point queries—put the columnstore close to or on par
  with TAM without the storage from the additional index. We
  apologize for the inconvenience this action potentially causes
  and are here to assist you during the migration process.

- Stop storing build machine kernel version (boo#1101107)

- Update to version 2.20.3
  https://github.com/timescale/timescaledb/releases/tag/2.20.3

- Update to version 2.20.2
  https://github.com/timescale/timescaledb/releases/tag/2.20.2

- drop pg 14

- Update to version 2.20.1
  https://github.com/timescale/timescaledb/releases/tag/2.20.1

- Update to version 2.20.0
  https://github.com/timescale/timescaledb/releases/tag/2.20.0

- Update to version 2.19.3
  https://github.com/timescale/timescaledb/releases/tag/2.19.3

- Update to version 2.19.2
  https://github.com/timescale/timescaledb/releases/tag/2.19.2

- Update to version 2.19.1
  https://github.com/timescale/timescaledb/releases/tag/2.19.1

- Update to version 2.19.0
  https://github.com/timescale/timescaledb/releases/tag/2.19.0

- Update to version 2.18.2
  https://github.com/timescale/timescaledb/releases/tag/2.18.2