chore(deps): update dependency gburd/pg_fts to v1.0.8 #21

Merged

AzSiAz merged 1 commit from renovate/gburd-pg_fts-1.x into main

2026-07-24 17:08:10 +02:00

AzSiAz commented

2026-07-24 17:01:52 +02:00

Owner

This PR contains the following updates:

Package	Update	Change
gburd/pg_fts	patch	`1.0.7` → `1.0.8`

Release Notes

gburd/pg_fts (gburd/pg_fts)

`v1.0.8`

Compare Source

Bug-fix release. No on-disk format change from 1.0.7; no REINDEX
required (ALTER EXTENSION pg_fts UPDATE TO '1.0.8').

Fixed out-of-memory / worker SIGKILL during a large index build's merge
phase. The 1.0.6 flush-budget ceiling bounds the scan phase, but the merge
phase held two vocabulary-proportional working sets that no setting bounded:
it loaded every input segment's entire dictionary into memory (and the final
reduction opens all segments at once), and it accumulated the whole merged
vocabulary before writing the dictionary. On a large, high-vocabulary corpus
(tens of millions of distinct terms) each could reach multiple gigabytes
regardless of maintenance_work_mem, so a big build could exhaust host memory
in the merge phase even at a configuration whose scan phase fit comfortably.
The merge now reads each input dictionary a page at a time and spills the
output dictionary metadata to a temporary file, so its memory no longer scales
with the corpus vocabulary. Measured peak build memory roughly halved on a
high-vocabulary corpus, with a much flatter growth curve; build time did not
regress. (Memory-only change: on-disk format is byte-identical, no REINDEX.)

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.7` → `1.0.8` | --- ### Release Notes <details> <summary>gburd/pg_fts (gburd/pg_fts)</summary> ### [`v1.0.8`](https://github.com/gburd/pg_fts/blob/HEAD/CHANGELOG.md#108) [Compare Source](https://github.com/gburd/pg_fts/compare/v1.0.7...v1.0.8) Bug-fix release. **No on-disk format change** from 1.0.7; no **REINDEX** required (`ALTER EXTENSION pg_fts UPDATE TO '1.0.8'`). - **Fixed out-of-memory / worker SIGKILL during a large index build's merge phase.** The 1.0.6 flush-budget ceiling bounds the scan phase, but the merge phase held two vocabulary-proportional working sets that no setting bounded: it loaded every input segment's entire dictionary into memory (and the final reduction opens all segments at once), and it accumulated the whole merged vocabulary before writing the dictionary. On a large, high-vocabulary corpus (tens of millions of distinct terms) each could reach multiple gigabytes regardless of `maintenance_work_mem`, so a big build could exhaust host memory in the merge phase even at a configuration whose scan phase fit comfortably. The merge now reads each input dictionary a page at a time and spills the output dictionary metadata to a temporary file, so its memory no longer scales with the corpus vocabulary. Measured peak build memory roughly halved on a high-vocabulary corpus, with a much flatter growth curve; build time did not regress. (Memory-only change: on-disk format is byte-identical, no REINDEX.) </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. --- - [ ] If you want to rebase/retry this PR, check this box --- This PR has been generated by [Mend Renovate](https://github.com/renovatebot/renovate).

AzSiAz added 1 commit

2026-07-24 17:01:52 +02:00

chore(deps): update dependency gburd/pg_fts to v1.0.8

ci/woodpecker/pr/pr Pipeline was successful

Details

5558742904

AzSiAz scheduled this pull request to auto merge when all checks succeed

2026-07-24 17:01:52 +02:00

AzSiAz merged commit 5d7b3c9929 into main

2026-07-24 17:08:10 +02:00

AzSiAz deleted branch renovate/gburd-pg_fts-1.x

2026-07-24 17:08:10 +02:00