Closed pallavisontakke closed 1 month ago
All modified and coverable lines are covered by tests :white_check_mark:
Please upload report for BASE (
2.15.x@2525b81
). Learn more about missing BASE report.:exclamation: Current head 5751771 differs from pull request most recent head c7025cd
Please upload reports for the commit c7025cd to get more accurate results.
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
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 ...
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 ...
If you upgraded to 2.15.0 and have run the script after that upgrade you dont need to rerun. But if you are coming from a version before 2.15.0 you still need to execute the script.
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 ...
If you upgraded to 2.15.0 and have run the script after that upgrade you dont need to rerun. But if you are coming from a version before 2.15.0 you still need to execute the script.
Still, it would be nice to add this fact to the release notes for people coming from < 2.15.0, since not everybody might read the previous notes and IMHO it does not hurt much to include this line for 2.15.x minor releases:
**For on-premise users and upgrades from < 2.15.0 only**, you will need to run [this SQL script](https://github.com/timescale/timescaledb-extras/blob/master/utils/2.15.X-fix_hypertable_foreign_keys.sql) after running `ALTER EXTENSION`. More details can be found in the pull request [#6797](https://github.com/timescale/timescaledb/pull/6797).
BTW the displayed number for PR in the SQL Script line is wrong, it should say 6797 instead of 6786 as in the link, which is correct. Maybe this can corrected for the 2.15.0 info as part of this commit.
Can we keep the same format for this release note as the 2.15.0 for the script please:
After you run ALTER EXTENSION
, you must run this SQL script. For more details, see the
following pull requests #6797.
If you are migrating from TimescaleDB v2.15.0, no changes are required.
Have added a few suggestions. Happy follow up.
Edited so.
Release 2.15.1
This release contains performance improvements and bug fixes since the 2.15.0 release. We recommend that you upgrade at the next available opportunity.
Bugfixes
6540 Segmentation fault when backfilling data with COPY into a compressed chunk
6858 Before update trigger not working correctly
6908 Fix gapfill with timezone behaviour around dst switches
6911 Fix dropped chunk metadata removal in update script
6940 Fix
pg_upgrade
failure by removingregprocedure
from catalog table6957 Fix segfault in UNION queries with ordering on compressed chunks
Thanks