chore(deps): update dependency gburd/pg_fts to v1.1.3 #25

Merged
AzSiAz merged 1 commit from renovate/gburd-pg_fts-1.x into main 2026-07-27 18:11:53 +02:00
Owner

This PR contains the following updates:

Package Update Change
gburd/pg_fts patch 1.1.21.1.3

Release Notes

gburd/pg_fts (gburd/pg_fts)

v1.1.3

Compare 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').

  • Fixed non-converging merges on a large, high-vocabulary index. On a
    multi-tens-of-GB index with many similarly-sized segments (e.g. a ~1.9M-doc /
    ~45GB email-body corpus), fts_merge and the build's compaction could run for
    hours 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 segments at DEBUG1) 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_merge collapse to a single segment in ~8 minutes; previously it
    did 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)

  • 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.2` → `1.1.3` | --- ### Release Notes <details> <summary>gburd/pg_fts (gburd/pg_fts)</summary> ### [`v1.1.3`](https://github.com/gburd/pg_fts/blob/HEAD/CHANGELOG.md#113) [Compare Source](https://github.com/gburd/pg_fts/compare/v1.1.2...v1.1.3) Bug-fix release. **No on-disk format change** from 1.1.2; no **REINDEX** required (`ALTER EXTENSION pg_fts UPDATE TO '1.1.3'`). - **Fixed non-converging merges on a large, high-vocabulary index.** On a multi-tens-of-GB index with many similarly-sized segments (e.g. a \~1.9M-doc / \~45GB email-body corpus), `fts_merge` and the build's compaction could run for hours 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 segments` at `DEBUG1`) 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_merge` collapse to a single segment in \~8 minutes; previously it did not complete. The segment level is computed from size, not stored, so the on-disk format is unchanged and no REINDEX is needed. </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. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR has been generated by [Mend Renovate](https://github.com/renovatebot/renovate). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0My4yODQuMCIsInVwZGF0ZWRJblZlciI6IjQzLjI4NC4wIiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6W119-->
chore(deps): update dependency gburd/pg_fts to v1.1.3
All checks were successful
ci/woodpecker/pr/pr Pipeline was successful
4d65a4e17e
AzSiAz scheduled this pull request to auto merge when all checks succeed 2026-07-27 18:00:31 +02:00
AzSiAz merged commit f5b6085992 into main 2026-07-27 18:11:52 +02:00
AzSiAz deleted branch renovate/gburd-pg_fts-1.x 2026-07-27 18:11:53 +02:00
Sign in to join this conversation.
No reviewers
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
AzSiAz/cnpg-extension-image!25
No description provided.