chore(deps): update dependency gburd/pg_fts to v1.1.1 #23

Merged

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

2026-07-26 17:06:44 +02:00

AzSiAz commented

2026-07-26 17:00:31 +02:00

Owner

This PR contains the following updates:

Package	Update	Change
gburd/pg_fts	patch	`1.1.0` → `1.1.1`

Release Notes

gburd/pg_fts (gburd/pg_fts)

`v1.1.1`

Compare Source

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

Fixed quadratic (O(N^2)) time in VACUUM / bulk-delete on a large index.
1.1.0 fixed the same pattern in the build's trigram writer; three more
instances remained on the delete/vacuum path (building a segment's live-docid
set and the tombstone sets one member at a time re-walked the sparsemap from
the start on every insert). Harmless on a small index, but on a large index
a VACUUM or a large DELETE could spend a very long time in tombstone
construction — the same "time explodes at scale" behavior the build had.
All corpus-scale sparsemap builds now use the bulk O(N) path. Tombstone
results are unchanged (verified against a delete + VACUUM cycle).
Docs: added a build time model and serial/low-parallelism recommendation
(the final single-segment collapse is a single-backend pass over the whole
index, so budget it in a maintenance window or leave the index tiered), and
noted that fts_index_stats() (like fts_index_nsegments()) can be polled on
an in-progress index.

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.0` → `1.1.1` | --- ### Release Notes <details> <summary>gburd/pg_fts (gburd/pg_fts)</summary> ### [`v1.1.1`](https://github.com/gburd/pg_fts/blob/HEAD/CHANGELOG.md#111) [Compare Source](https://github.com/gburd/pg_fts/compare/v1.1.0...v1.1.1) Bug-fix release. **No on-disk format change** from 1.1.0; no **REINDEX** required (`ALTER EXTENSION pg_fts UPDATE TO '1.1.1'`). - **Fixed quadratic (O(N^2)) time in `VACUUM` / bulk-delete on a large index.** 1.1.0 fixed the same pattern in the build's trigram writer; three more instances remained on the delete/vacuum path (building a segment's live-docid set and the tombstone sets one member at a time re-walked the sparsemap from the start on every insert). Harmless on a small index, but on a large index a `VACUUM` or a large `DELETE` could spend a very long time in tombstone construction — the same "time explodes at scale" behavior the build had. All corpus-scale sparsemap builds now use the bulk O(N) path. Tombstone results are unchanged (verified against a delete + `VACUUM` cycle). - **Docs:** added a build time model and serial/low-parallelism recommendation (the final single-segment collapse is a single-backend pass over the whole index, so budget it in a maintenance window or leave the index tiered), and noted that `fts_index_stats()` (like `fts_index_nsegments()`) can be polled on an in-progress index. </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-26 17:00:31 +02:00

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

ci/woodpecker/pr/pr Pipeline was successful

Details

28b3168e47

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

2026-07-26 17:00:31 +02:00

AzSiAz merged commit f6e4bcbd5d into main

2026-07-26 17:06:44 +02:00

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

2026-07-26 17:06:44 +02:00