chore(deps): update dependency gburd/pg_fts to v1.0.5 #18
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "renovate/gburd-pg_fts-1.x"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This PR contains the following updates:
1.0.4→1.0.5Release Notes
gburd/pg_fts (gburd/pg_fts)
v1.0.5Compare Source
Bug-fix release. No on-disk format change from 1.0.4; no REINDEX
required (
ALTER EXTENSION pg_fts UPDATE TO '1.0.5').over a high-vocabulary text column (e.g. email/message bodies with quoted
chains, patches, and code -- millions of distinct terms). The build bounds its
memory by flushing a segment when the in-memory working set exceeds
maintenance_work_mem, but the size check did not count the term hash table,which lives in a child memory context -- so on a vocabulary-dominant corpus
the check undercounted the real working set and the flush fired far too late,
letting a multi-hour build grow well past
maintenance_work_mem(observed~19 GB resident+swap on an 83 GB / 1.8M-row build before it was killed). The
check now counts child contexts, so a build settles at roughly
maintenance_work_memregardless of vocabulary size. Affects both serial andparallel builds; no change to results or on-disk format.
Configuration
📅 Schedule: (in timezone Europe/Paris)
🚦 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.
This PR has been generated by Mend Renovate.