chore(deps): update dependency timescale/timescaledb to v2.15.2 #3
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
2.15.0
->2.15.2
Release Notes
timescale/timescaledb (timescale/timescaledb)
v2.15.2
Compare Source
This release contains bug fixes since the 2.15.1 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 or v2.15.1, no changes are required.
Bugfixes
compress_chunk
with a primary space partition.Thanks
v2.15.1
Compare Source
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
BEFORE UPDATE
trigger not working correctly.time_bucket_gapfill()
with timezone behaviour around daylight savings time (DST) switches.pg_upgrade
failure by removingregprocedure
from the catalog table.segfault
in UNION queries that contain ordering on compressed chunks.Thanks
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate. View repository job log here.