PG-2424 PostgreSQL 19 support - #806
Conversation
19a2402 to
fed60d2
Compare
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #806 +/- ##
==========================================
- Coverage 88.57% 88.08% -0.49%
==========================================
Files 3 3
Lines 1304 1318 +14
Branches 180 183 +3
==========================================
+ Hits 1155 1161 +6
- Misses 75 80 +5
- Partials 74 77 +3 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
fed60d2 to
481ccb5
Compare
0c199bc to
2a116fe
Compare
jeltz
left a comment
There was a problem hiding this comment.
I have not reviewed what actually changed in PGSS.
|
Do we need to support |
958ddb5 to
fed3a0b
Compare
Added |
|
what are the concerns regarding changes in PGSS that are being referenced here? |
|
@adeshthack The main thing was |
Make pg_stat_monitor compilable against PostgreSQL 19 PostgreSQL 19 optimized SELECT ... INTO statements execution(ce8d5fe), so some of them are no longer tracked by pg_stat_statements/pg_stat_monitor. So we update level tracking test to address this change. Build and test CI workflow required timeout increase as PG 19 requires slightly more time.
There are no PostgreSQL 19 packages yet, so add this version only to source based workflows.
pg_stat_statements introduces two new coutners in PostgreSQL 19: - generic_plan_calls - custom_plan_calls These counters track how many times a prepared statement was executed using a generic or custom plan. Backport them to pg_stat_monitor.
PostgreSQL 19 exposes ComputeConstantLengths function, so there is no more reasons to compute constant lenght with our own implemenation.
In PostgreSQL 19 some pg_stat_statements tests got updates. Backport them to pg_stat_monitor.
Backport the upstream pg_stat_statements fix (commit b1635c16669) from PostgreSQL 18. Mark same-location duplicates with length = -1 before the squashed check.
Mark property graphs with * the same way as we do for views.
Condition had and issue where it was keeping all subqueries, but it should keep only subqueries that are views or property graphs. Rewrite it with better condition: perminfoindex is non-zero for all types of RTEs that we need.
fed3a0b to
96a3336
Compare
yea sounds good |
PG-2424
Description
https://www.postgresql.org/docs/19/release-19.html#RELEASE-19-PGSTATSTATEMENTS
postgres/postgres@REL_18_4...REL_19_BETA2
Links
Fixes #773