chore(deps): update dependency gburd/pg_fts to v1.1.2 #24

Merged

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

2026-07-26 21:07:23 +02:00

AzSiAz commented

2026-07-26 21:00:26 +02:00

Owner

This PR contains the following updates:

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

Release Notes

gburd/pg_fts (gburd/pg_fts)

`v1.1.2`

Compare Source

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

Fixed a hang in the final phase of a large CREATE INDEX CONCURRENTLY.
On a large, high-vocabulary corpus, a build could get all the way through the
merge (the 1.1.1 fix) and then wedge in finalization -- the build leader
parked waiting on parallel workers while another backend blocked on the
relation-extension lock, with the index never becoming valid. The build
finalization started a second parallel worker set to merge the segments; on a
large index under CONCURRENTLY on a busy host, the participants could
contend on the relation-extension lock and stall indefinitely. Finalization is
now serial (the 1.1.1 O(N) merge made the parallel pass unnecessary for
convergence), so no relation-extension contention arises and the build
completes. fts_merge() still merges in parallel when run on its own.

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.1` → `1.1.2` | --- ### Release Notes <details> <summary>gburd/pg_fts (gburd/pg_fts)</summary> ### [`v1.1.2`](https://github.com/gburd/pg_fts/blob/HEAD/CHANGELOG.md#112) [Compare Source](https://github.com/gburd/pg_fts/compare/v1.1.1...v1.1.2) Bug-fix release. **No on-disk format change** from 1.1.1; no **REINDEX** required (`ALTER EXTENSION pg_fts UPDATE TO '1.1.2'`). - **Fixed a hang in the final phase of a large `CREATE INDEX CONCURRENTLY`.** On a large, high-vocabulary corpus, a build could get all the way through the merge (the 1.1.1 fix) and then wedge in finalization -- the build leader parked waiting on parallel workers while another backend blocked on the relation-extension lock, with the index never becoming valid. The build finalization started a second parallel worker set to merge the segments; on a large index under `CONCURRENTLY` on a busy host, the participants could contend on the relation-extension lock and stall indefinitely. Finalization is now serial (the 1.1.1 O(N) merge made the parallel pass unnecessary for convergence), so no relation-extension contention arises and the build completes. `fts_merge()` still merges in parallel when run on its own. </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 21:00:26 +02:00

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

ci/woodpecker/pr/pr Pipeline was successful

Details

a14accaea3

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

2026-07-26 21:00:26 +02:00

AzSiAz merged commit 7d67a2294a into main

2026-07-26 21:07:23 +02:00

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

2026-07-26 21:07:23 +02:00