chore(deps): update dependency gburd/pg_fts to v1.0.3 #16

Merged

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

2026-07-21 14:06:21 +02:00

AzSiAz commented

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

Owner

This PR contains the following updates:

Package	Update	Change
gburd/pg_fts	patch	`1.0.2` → `1.0.3`

Release Notes

gburd/pg_fts (gburd/pg_fts)

`v1.0.3`

Compare Source

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

Fixed an invalid memory alloc request size crash in a parallel index-build
worker (reported against a ~13-hour parallel CREATE INDEX CONCURRENTLY
over a large table with a very large vocabulary). This was a different site
from the 1.0.2 fix: the trigram inverted-index builder and the streaming
segment merge sized several allocations from the merged-group vocabulary,
which -- unlike the per-segment build path -- is not bounded by
maintenance_work_mem, so a hot trigram's term list (and the merge output
arrays) could exceed the 1 GB allocation limit on a large enough corpus. All
corpus/vocabulary-scale allocations in the build, merge, and analyze paths now
use a huge-safe allocation, closing this crash class off across the board.
A single document that would assemble into an ftsdoc larger than 1 GB now
reports a clear "document is too large" error instead of an opaque
allocation failure. An ftsdoc is a variable-length value limited to 1 GB.

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.2` → `1.0.3` | --- ### Release Notes <details> <summary>gburd/pg_fts (gburd/pg_fts)</summary> ### [`v1.0.3`](https://github.com/gburd/pg_fts/blob/HEAD/CHANGELOG.md#103) [Compare Source](https://github.com/gburd/pg_fts/compare/v1.0.2...v1.0.3) Bug-fix release. **No on-disk format change** from 1.0.2; no **REINDEX** required (`ALTER EXTENSION pg_fts UPDATE TO '1.0.3'`). - **Fixed an `invalid memory alloc request size` crash in a parallel index-build worker** (reported against a \~13-hour parallel `CREATE INDEX CONCURRENTLY` over a large table with a very large vocabulary). This was a different site from the 1.0.2 fix: the trigram inverted-index builder and the streaming segment merge sized several allocations from the *merged-group vocabulary*, which -- unlike the per-segment build path -- is not bounded by `maintenance_work_mem`, so a hot trigram's term list (and the merge output arrays) could exceed the 1 GB allocation limit on a large enough corpus. All corpus/vocabulary-scale allocations in the build, merge, and analyze paths now use a huge-safe allocation, closing this crash class off across the board. - **A single document that would assemble into an `ftsdoc` larger than 1 GB now reports a clear "document is too large" error** instead of an opaque allocation failure. An `ftsdoc` is a variable-length value limited to 1 GB. </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-21 14:00:26 +02:00

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

ci/woodpecker/pr/pr Pipeline was successful

Details

ab116cab97

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

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

AzSiAz merged commit 7b9f5e44d7 into main

2026-07-21 14:06:21 +02:00

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

2026-07-21 14:06:21 +02:00