chore(deps): update dependency gburd/pg_fts to v1.0.4 #17

Merged

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

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

AzSiAz commented

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

Owner

This PR contains the following updates:

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

Release Notes

gburd/pg_fts (gburd/pg_fts)

`v1.0.4`

Compare Source

Scale-hardening release. No on-disk format change from 1.0.3; no REINDEX
required (ALTER EXTENSION pg_fts UPDATE TO '1.0.4').

CREATE INDEX on a large table with a modest maintenance_work_mem no
longer fails with "reached the maximum of 128 segments." The build flushed
one segment per maintenance_work_mem of accumulation with no intermediate
merge, so a large enough index overflowed the segment directory before the
end-of-build merge. Each build participant now grows its own flush budget
geometrically, so the flush count grows only logarithmically with corpus size
(and stays far under the cap) -- parallel-safe, with no on-disk or behavior
change to the finished index.
Corrected integer-width overflows that only surface at extreme scale (wrong
results, not crashes): document-frequency sums used in IDF/BM25 scoring and in
fts_index_df() are now 64-bit (a term in more than ~4 billion documents no
longer wraps); the anomaly-scan "skip common terms" filter no longer misfires
on a term whose df exceeds ~2.1 billion.
fts_index_stats's nterms output is now bigint (was int), so an
index with more than ~2.1 billion total distinct terms reports a correct
count. This widens the function's output column; the upgrade replaces the
function definition (a DROP/CREATE, applied automatically by
ALTER EXTENSION ... UPDATE).

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.3` → `1.0.4` | --- ### Release Notes <details> <summary>gburd/pg_fts (gburd/pg_fts)</summary> ### [`v1.0.4`](https://github.com/gburd/pg_fts/blob/HEAD/CHANGELOG.md#104) [Compare Source](https://github.com/gburd/pg_fts/compare/v1.0.3...v1.0.4) Scale-hardening release. **No on-disk format change** from 1.0.3; no **REINDEX** required (`ALTER EXTENSION pg_fts UPDATE TO '1.0.4'`). - **`CREATE INDEX` on a large table with a modest `maintenance_work_mem` no longer fails** with "reached the maximum of 128 segments." The build flushed one segment per `maintenance_work_mem` of accumulation with no intermediate merge, so a large enough index overflowed the segment directory before the end-of-build merge. Each build participant now grows its own flush budget geometrically, so the flush count grows only logarithmically with corpus size (and stays far under the cap) -- parallel-safe, with no on-disk or behavior change to the finished index. - **Corrected integer-width overflows that only surface at extreme scale** (wrong results, not crashes): document-frequency sums used in IDF/BM25 scoring and in `fts_index_df()` are now 64-bit (a term in more than \~4 billion documents no longer wraps); the anomaly-scan "skip common terms" filter no longer misfires on a term whose df exceeds \~2.1 billion. - **`fts_index_stats`'s `nterms` output is now `bigint`** (was `int`), so an index with more than \~2.1 billion total distinct terms reports a correct count. This widens the function's output column; the upgrade replaces the function definition (a `DROP`/`CREATE`, applied automatically by `ALTER EXTENSION ... UPDATE`). </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 21:00:30 +02:00

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

ci/woodpecker/pr/pr Pipeline was successful

Details

3e815b2111

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

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

AzSiAz merged commit f809d7f3c7 into main

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

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

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