chore(deps): update dependency gburd/pg_fts to v1.0.6 #19
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "renovate/gburd-pg_fts-1.x"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This PR contains the following updates:
1.0.5→1.0.6Release Notes
gburd/pg_fts (gburd/pg_fts)
v1.0.6Compare Source
Bug-fix release. No on-disk format change from 1.0.5; no REINDEX
required (
ALTER EXTENSION pg_fts UPDATE TO '1.0.6').(the phase after the 1.0.5 fix). The per-participant build memory budget grew
geometrically with no ceiling, so a large build's in-memory working set could
climb to tens of gigabytes before flushing; combined with one budget per build
participant (the leader plus each parallel worker), a big parallel build could
exhaust host memory and thrash into swap hours in. The budget is now capped at
2 x maintenance_work_mem, so peak build memory is bounded to(max_parallel_maintenance_workers + 1) x 2 x maintenance_work_memregardlessof corpus size. (Peak build memory scales with the worker count -- size
maintenance_work_memwith that multiplier in mind.)merge leaves on disk, so it ships closer to its compacted size instead of
carrying the merge's freed-input pages until the next VACUUM. (Full
compaction of interior free space still comes from
fts_vacuum/ VACUUM.)Configuration
📅 Schedule: (in timezone Europe/Paris)
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, 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.