chore(deps): update dependency gburd/pg_fts to v1.0.6 #19

Merged
AzSiAz merged 1 commit from renovate/gburd-pg_fts-1.x into main 2026-07-23 12:06:46 +02:00
Owner

This PR contains the following updates:

Package Update Change
gburd/pg_fts patch 1.0.51.0.6

Release Notes

gburd/pg_fts (gburd/pg_fts)

v1.0.6

Compare 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').

  • Fixed runaway memory during a long index build over a large corpus
    (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_mem regardless
    of corpus size. (Peak build memory scales with the worker count -- size
    maintenance_work_mem with that multiplier in mind.)
  • A freshly built or REINDEXed index now reclaims the free tail its final
    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)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 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.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate.

This PR contains the following updates: | Package | Update | Change | |---|---|---| | [gburd/pg_fts](https://github.com/gburd/pg_fts) | patch | `1.0.5` → `1.0.6` | --- ### Release Notes <details> <summary>gburd/pg_fts (gburd/pg_fts)</summary> ### [`v1.0.6`](https://github.com/gburd/pg_fts/blob/HEAD/CHANGELOG.md#106) [Compare Source](https://github.com/gburd/pg_fts/compare/v1.0.5...v1.0.6) Bug-fix release. **No on-disk format change** from 1.0.5; no **REINDEX** required (`ALTER EXTENSION pg_fts UPDATE TO '1.0.6'`). - **Fixed runaway memory during a long index build over a large corpus** (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_mem` regardless of corpus size. (Peak build memory scales with the worker count -- size `maintenance_work_mem` with that multiplier in mind.) - **A freshly built or REINDEXed index now reclaims the free tail its final 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.) </details> --- ### Configuration 📅 **Schedule**: (in timezone Europe/Paris) - Branch creation - At any time (no schedule defined) - Automerge - At any time (no schedule defined) 🚦 **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. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR has been generated by [Mend Renovate](https://github.com/renovatebot/renovate). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0My4yNzMuMCIsInVwZGF0ZWRJblZlciI6IjQzLjI3My4wIiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6W119-->
chore(deps): update dependency gburd/pg_fts to v1.0.6
All checks were successful
ci/woodpecker/pr/pr Pipeline was successful
9cf1b84054
AzSiAz scheduled this pull request to auto merge when all checks succeed 2026-07-23 12:00:26 +02:00
AzSiAz merged commit 1a46ccb349 into main 2026-07-23 12:06:46 +02:00
AzSiAz deleted branch renovate/gburd-pg_fts-1.x 2026-07-23 12:06:47 +02:00
Sign in to join this conversation.
No reviewers
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
AzSiAz/cnpg-extension-image!19
No description provided.