chore(deps): update dependency postgresql-18-timescaledb - #335
Merged
Conversation
Signed-off-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
renovate
Bot
force-pushed
the
renovate/postgresql-18-timescaledb-2.x
branch
from
September 11, 2026 03:12
303efd9 to
2f3a1ae
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.29.2→2.30.02.29.2+dfsg-1.pgdg12+1→2.30.0+dfsg-1.pgdg12+12.29.2+dfsg-1.pgdg13+1→2.30.0+dfsg-1.pgdg13+1Release Notes
timescale/timescaledb (postgresql-18-timescaledb)
v2.30.0Compare Source
This release contains performance improvements and bug fixes since the 2.29.2 release. We recommend that you upgrade at the next available opportunity.
Highlighted features in TimescaleDB v2.30.0
Blazing fast
LIMITqueries with the newly introducedDeferredChunkAppend. This custom node reduces planning significantly by delaying chunk expansion. During planning the hypertable stays unexpanded and only during execution are chunks enumerated on demand. Combined with the optimizations toFIRSTandLASTsparse indexes, this addition executes last-point queries far more efficiently and quickly. This changes the scaling of the "What is the last reading from this sensor" query from linear with number of chunks to constant if it can be found in the most recent chunk. The true power of the custom node starts to show with increasing amount of chunks, see more elaborate benchmarks.Features
DeferredChunkAppendcustom scanBugfixes
FOR TABLES IN SCHEMAcreate_compressed_chunktime_bucketWHEREclause and the columnar aggregation pipelineuser_catalog_tableoption from catalog tablesNULLtuples to compressed batches withNULLboundaries during recompressionGUCs
enable_deferred_chunk_append: Custom scan node for hypertables that iterates chunks at execution instead of expanding every chunk at plan time. Default: true.use_custom_toaster: Use a custom TOAST writer for compressed row inserts. Default: false.Thanks
Configuration
📅 Schedule: (UTC)
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR was generated by Mend Renovate. View the repository job log.