Release 2.15.1

[fabriziomello]

This release contains bug fixes since the 2.15.0 release. Best practice is to upgrade at the next available opportunity.

Migrating from self-hosted TimescaleDB v2.14.x and earlier

After you run ALTER EXTENSION, you must run this SQL script. For more details, see the following pull request #6797.

If you are migrating from TimescaleDB v2.15.0, no changes are required.

Bugfixes

• 6540: Segmentation fault when you backfill data using COPY into a compressed chunk.

• 6858: BEFORE UPDATE trigger not working correctly.

• 6908: Fix time_bucket_gapfill() with timezone behaviour around daylight savings time (DST) switches.

• 6911: Fix dropped chunk metadata removal in the update script.

• 6940: Fix pg_upgrade failure by removing regprocedure from the catalog table.

• 6957: Fix then segfault in UNION queries that contain ordering on compressed chunks.

Thanks

• @DiAifU, @kiddhombre and @intermittentnrg for reporting the issues with gapfill and daylight saving time.
• @edgarzamora for reporting the issue with update triggers.
• @hongquan for reporting the issue with the update script.
• @iliastsa and @SystemParadox for reporting the issue with COPY into a compressed chunk.

Disable-check: force-changelog-file

[codecov[bot]]

Codecov Report

All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 81.70%. Comparing base (59f50f2) to head (289a9b2). Report is 184 commits behind head on main.

Additional details and impacted files

```diff @@ Coverage Diff @@ ## main #6966 +/- ## ========================================== + Coverage 80.06% 81.70% +1.63% ========================================== Files 190 198 +8 Lines 37181 36858 -323 Branches 9450 9631 +181 ========================================== + Hits 29770 30115 +345 + Misses 2997 2864 -133 + Partials 4414 3879 -535 ```

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

[adschmu]

Is the 2.15.X-fix_hypertable_foreign_keys.sql script still required? It is not entirely clear whether "For [...] this release only" refers to 2.15.0 or 2.15.X.

The file name hints at it, but it would be helpful to include the one sentence about the script into these release notes again, if it still applies. There might be people not reading all of the previous changelogs, and the script is more like a "Known issues" bullet point anyway ...

[intermittentnrg]

Duplicate of #6970 which is already merged?

[fabriziomello]

Duplicate of #6970 which is already merged?

Actually no... we need to have two release PRs, one for the main branch and another for the release branch, in this case 2.15.x (actually the release branch PR is usually made by cherry picking the one against the main branch, but this time we rushed a bit). Thanks for reviewing!