AzSiAz/cnpg-extension-image
1
0
Fork 0
Code Issues 1 Pull requests Projects Releases Packages 17 Wiki Activity

chore(deps): update dependency gburd/pg_fts to v1.0.2 #15

Merged
AzSiAz merged 1 commit from renovate/gburd-pg_fts-1.x into main 2026-07-20 14:11:25 +02:00
Conversation 0 Commits 1 Files changed 2 +7 -7
AzSiAz commented 2026-07-20 14:00:32 +02:00
Owner
Copy link

This PR contains the following updates:

Package Update Change
gburd/pg_fts patch 1.0.1 → 1.0.2

Release Notes

gburd/pg_fts (gburd/pg_fts)

v1.0.2

Compare Source

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

  • Fixed a read-path crash (invalid memory alloc request size) when decoding
    a posting block with a very large per-block position count.     The
    positions-decode path in bm25_decode_term sized its scratch buffers with an
    unguarded allocation; when a block's summed term frequency pushed the buffer
    past the 1 GB MaxAllocSize limit, the allocation threw and aborted whatever
    triggered the decode -- a CREATE INDEX CONCURRENTLY validation scan in the
    reported case, but the same path is reached by ordinary scans (count, ranked,
    phrase), merges, and vacuum. A legitimately large position count now uses a
    huge-safe allocation; a corrupt or inflated on-disk term-frequency (a class
    the existing block-header and column-length corruption checks did not catch)
    is now detected and rejected with a WARNING (a bounded miss, REINDEX to
    rebuild), rather than reading past the block. This was the read-side
    counterpart of the build-time huge-allocation fix; both sides are now guarded.
  • The corruption/fuzz harness gained a dedicated planted-bug ("teeth") build for
    this class, so a regression that removed the guard would fail CI.

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.1` → `1.0.2` | --- ### Release Notes <details> <summary>gburd/pg_fts (gburd/pg_fts)</summary> ### [`v1.0.2`](https://github.com/gburd/pg_fts/blob/HEAD/CHANGELOG.md#102) [Compare Source](https://github.com/gburd/pg_fts/compare/v1.0.1...v1.0.2) Bug-fix release. **No on-disk format change** from 1.0.1; no **REINDEX** required (`ALTER EXTENSION pg_fts UPDATE TO '1.0.2'`). - **Fixed a read-path crash (`invalid memory alloc request size`) when decoding a posting block with a very large per-block position count.** The positions-decode path in `bm25_decode_term` sized its scratch buffers with an unguarded allocation; when a block's summed term frequency pushed the buffer past the 1 GB `MaxAllocSize` limit, the allocation threw and aborted whatever triggered the decode -- a `CREATE INDEX CONCURRENTLY` validation scan in the reported case, but the same path is reached by ordinary scans (count, ranked, phrase), merges, and vacuum. A legitimately large position count now uses a huge-safe allocation; a corrupt or inflated on-disk term-frequency (a class the existing block-header and column-length corruption checks did not catch) is now detected and rejected with a `WARNING` (a bounded miss, `REINDEX` to rebuild), rather than reading past the block. This was the read-side counterpart of the build-time huge-allocation fix; both sides are now guarded. - The corruption/fuzz harness gained a dedicated planted-bug ("teeth") build for this class, so a regression that removed the guard would fail CI. </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:eyJjcmVhdGVkSW5WZXIiOiI0My4yNzIuMCIsInVwZGF0ZWRJblZlciI6IjQzLjI3Mi4wIiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6W119-->
chore(deps): update dependency gburd/pg_fts to v1.0.2
All checks were successful
ci/woodpecker/pr/pr Pipeline was successful
Details
2d23ce2351
AzSiAz scheduled this pull request to auto merge when all checks succeed 2026-07-20 14:00:32 +02:00
AzSiAz merged commit f12e91d33a into main 2026-07-20 14:11:25 +02:00
AzSiAz deleted branch renovate/gburd-pg_fts-1.x 2026-07-20 14:11:25 +02:00
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
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!15
No description provided.