Skip to content

Merge back release 2.4.0 - #843

Merged
artemgavrilov merged 4 commits into
mainfrom
release-2.4.0
Sep 14, 2026
Merged

artemgavrilov merged 4 commits into
mainfrom
release-2.4.0

Conversation

@artemgavrilov

Copy link
Copy Markdown
Contributor

PG-0

Description

Links

jeltz added 3 commits August 26, 2026 14:22
PostgreSQL 18.6 included a fix for CVE-2026-14676 which also affected us
due us copying code from pg_stat_statements. Only our code for 18 and 19
was affected but let's apply the fix for 18+ in a way which handles all
versions so we can avoid ifdefs.

See https://git.postgresql.org/pg/commitdiff/1e2795ddeafc66cd78d2c90a69dd820488639c7c
@artemgavrilov
artemgavrilov marked this pull request as ready for review September 8, 2026 15:43
@codecov

codecov Bot commented Sep 8, 2026

Copy link
Copy Markdown

Codecov Report

❌ Patch coverage is 94.11765% with 1 line in your changes missing coverage. Please review.
✅ Project coverage is 88.46%. Comparing base (cd866ff) to head (af0cc0c).

Files with missing lines Patch % Lines
src/pg_stat_monitor.c 94.11% 0 Missing and 1 partial ⚠️
Additional details and impacted files
@@            Coverage Diff             @@
##             main     #843      +/-   ##
==========================================
- Coverage   88.50%   88.46%   -0.05%     
==========================================
  Files           3        3              
  Lines        1340     1335       -5     
  Branches      196      196              
==========================================
- Hits         1186     1181       -5     
  Misses         75       75              
  Partials       79       79              

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@jeltz jeltz left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approved but not sure we actually need to create Prs for stuff like this.

@artemgavrilov

Copy link
Copy Markdown
Contributor Author

Approved but not sure we actually need to create Prs for stuff like this.

Main branch is protected, we cannot push there (and I think it's good restriction)

@artemgavrilov
artemgavrilov merged commit 229cfb7 into main Sep 14, 2026
61 of 75 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants