Repository navigation
chore: add notable PostgreSQL bug fixes - #57
github-actions[bot] wants to merge 1 commit into
Conversation
PR Summary by QodoRefresh PostgreSQL release-note bug proposals for versions 15–18
AI Description
Diagram
High-Level Assessment
Files changed (1)
|
Code Review by Qodo
1. Catalog entries would ship with footnote markers and author credits
|
| "doc_link": "https://www.postgresql.org/docs/release/15.19/", | ||
| "fixed_in_minor": 19 | ||
| "issue_id": "PG15-3efcadec9", | ||
| "summary": "Fix buffer overrun in tsvector_delete() (Anthropic OSS program) §", |
There was a problem hiding this comment.
2. Attributions to an unverified credit are proposed 🐞 Bug ≡ Correctness
The entries credit "Anthropic OSS program" as the author of two buffer-overrun fixes. The scraper keeps the parenthesised text in the summary because its author regex only trims names that begin with a capital letter.
Agent Prompt
Issue description: Two proposed entries credit "Anthropic OSS program", which the scraper did not validate against the upstream release notes.
Fix Focus Areas:
- proposed-bugs.json[22-22]
- proposed-bugs.json[52-52]
Recommended Fix: Open the PostgreSQL 17.12 and 18.7 release notes and confirm the credit for each entry. Correct or drop the entries if the credit does not appear upstream.
ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools
| "doc_link": "https://www.postgresql.org/docs/release/15.18/", | ||
| "fixed_in_minor": 18 | ||
| "issue_id": "PG15-274da088e", | ||
| "summary": "Fix small memory leak in pgoutput with streamed prepared transactions (Ayush Tiwari) §", |
There was a problem hiding this comment.
3. Trivial memory-leak fix flagged as high severity 🐞 Bug ≡ Correctness
The HIGH_KEYWORDS list includes "memory leak", so _classify puts "Fix small memory leak in pgoutput with streamed prepared transactions" in the high tier. The PR description asks curators to drop trivial entries, but this one ranks above medium-tier crash-adjacent items.
Agent Prompt
Issue description: A small memory-leak fix is classified as high severity by keyword matching and kept in the proposal set.
Fix Focus Areas:
- proposed-bugs.json[16-16]
- tools/scrape_release_notes.py[60-70]
Recommended Fix: Curators should drop this entry when reviewing. Consider removing the generic "memory leak" keyword from HIGH_KEYWORDS, or matching it only together with a crash or corruption keyword.
ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools
Automated PostgreSQL release-notes scout.
tools/scrape_release_notes.pyfetched the latest ~2 minorrelease notes per major in {15,16,17,18}, filtered the
<li class="listitem">entries by severity keywords, dedupedagainst
data/known_bugs.json, and surfaced the top 5 permajor for review. The candidates are in
proposed-bugs.json.Action items for a human:
is biased toward data-integrity / crash / replication
bugs; doc-only or trivial entries should be dropped.
PG17-a1b2c3d4e→
PG17-MERGE-RACE-CONDITION-01) before merging.data/known_bugs.json:bash uv run python tools/scrape_release_notes.py --write --yes uv run python tools/generate_cve_sql.py git add data/known_bugs.json pgFirstAid.sql view_pgFirstAid.sql view_pgFirstAid_managed.sql git commit -m "chore: refresh known-bugs catalog"proposed-bugs.jsonbefore merge.Notes on the keyword filter (
HIGH/MEDIUMlists live intools/scrape_release_notes.py): the curated list is small,intent is curated quality over recall, and silent false
negatives are preferred over noisy false positives. Tune the
keyword lists if the proposals get noisy or thin.