chore(deps): update dependency gburd/pg_fts to v1.1.3 #25
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.1.2→1.1.3Release Notes
gburd/pg_fts (gburd/pg_fts)
v1.1.3Compare Source
Bug-fix release. No on-disk format change from 1.1.2; no REINDEX
required (
ALTER EXTENSION pg_fts UPDATE TO '1.1.3').multi-tens-of-GB index with many similarly-sized segments (e.g. a ~1.9M-doc /
~45GB email-body corpus),
fts_mergeand the build's compaction could run forhours without finishing: the segment merge was size-tiered with unbounded
fan-in, so it tried to merge essentially all segments into one in a single
pass over the whole index. The merge is now leveled (LSM/HanoiDB-style) with
bounded fan-in: a segment's level is derived from its size and no single
merge combines more than a bounded number of segments, so compaction proceeds
in small, discrete, observable steps (each merge logs
merging N of M segmentsatDEBUG1) with bounded write amplification and always converges.Validated on a 1.9M-doc / 26GB corpus: build to a bounded tiered set in ~17
minutes;
fts_mergecollapse to a single segment in ~8 minutes; previously itdid not complete. The segment level is computed from size, not stored, so the
on-disk format is unchanged and no REINDEX is needed.
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.