chore(deps): update dependency gburd/pg_fts to v1.1.4 #26

Merged

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

2026-07-28 01:08:22 +02:00

AzSiAz commented

2026-07-28 01:02:20 +02:00

Owner

This PR contains the following updates:

Package	Update	Change
gburd/pg_fts	patch	`1.1.3` → `1.1.4`

Release Notes

gburd/pg_fts (gburd/pg_fts)

`v1.1.4`

Compare Source

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

Fixed segment merges that could fail to converge, or crash, on a large,
high-vocabulary index. Two issues in the merge path, both exposed only at
scale (validated on a ~1.9M-doc / 40GB+ index):
- A merge discarded its finished output and retried if the segment directory
  changed at all while it ran (for example a concurrent flush appending a
  segment). On a big index each merge takes minutes, so it could read a great
  deal and never commit -- the reported "reads hundreds of GB, segment count
  never drops" non-convergence. A merge now re-locates its inputs by content
  and commits alongside concurrent flushes.
- A committed merge freed its input pages, which the next merge could recycle
  for its output while still reading the previous chain -- leading to a rare
  crash (SIGBUS) on very large merges. Merges now write to freshly extended
  pages during the merge loop and reclaim the freed space afterward.
  These are memory/scale-path fixes only; the on-disk format is unchanged.

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.1.3` → `1.1.4` | --- ### Release Notes <details> <summary>gburd/pg_fts (gburd/pg_fts)</summary> ### [`v1.1.4`](https://github.com/gburd/pg_fts/blob/HEAD/CHANGELOG.md#114) [Compare Source](https://github.com/gburd/pg_fts/compare/v1.1.3...v1.1.4) Bug-fix release. **No on-disk format change** from 1.1.3; no **REINDEX** required (`ALTER EXTENSION pg_fts UPDATE TO '1.1.4'`). - **Fixed segment merges that could fail to converge, or crash, on a large, high-vocabulary index.** Two issues in the merge path, both exposed only at scale (validated on a \~1.9M-doc / 40GB+ index): - A merge discarded its finished output and retried if the segment directory changed at all while it ran (for example a concurrent flush appending a segment). On a big index each merge takes minutes, so it could read a great deal and never commit -- the reported "reads hundreds of GB, segment count never drops" non-convergence. A merge now re-locates its inputs by content and commits alongside concurrent flushes. - A committed merge freed its input pages, which the next merge could recycle for its output while still reading the previous chain -- leading to a rare crash (SIGBUS) on very large merges. Merges now write to freshly extended pages during the merge loop and reclaim the freed space afterward. These are memory/scale-path fixes only; the on-disk format is unchanged. </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-28 01:02:20 +02:00

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

ci/woodpecker/pr/pr Pipeline was successful

Details

60c38369e5

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

2026-07-28 01:02:21 +02:00

AzSiAz merged commit ffdb66fc50 into main

2026-07-28 01:08:22 +02:00

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

2026-07-28 01:08:22 +02:00