Fix partition_prune testcase

[artemgavrilov]

Fixes #423

compute_query_id parameter has special value regress that allows pg_stat_monitor to have query identifier but hides it in EXPLAINs to let regression testing pass.

https://www.postgresql.org/docs/current/runtime-config-statistics.html#GUC-COMPUTE-QUERY-ID

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 90.56%. Comparing base (3d84610) to head (00bc98b).
Report is 4 commits behind head on main.

❗ Current head 00bc98b differs from pull request most recent head 05f5e2d. Consider uploading reports for the commit 05f5e2d to get more accurate results

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #440   +/-   ##
=======================================
  Coverage   90.55%   90.56%           
=======================================
  Files           3        3           
  Lines        1271     1272    +1     
  Branches       35       35           
=======================================
+ Hits         1151     1152    +1     
  Misses         98       98           
  Partials       22       22           

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

[Naeem-Akhter]

@artemgavrilov

Any reason that in this PR we have this setting only for postgresql-14-build & postgresql-15-build ('compute_query_id = regress). But not for postgresql-16-build where it is still (compute_query_id = off)? Am i missing something? :)

[artemgavrilov]

@artemgavrilov

Any reason that in this PR we have this setting only for postgresql-14-build & postgresql-15-build ('compute_query_id = regress). But not for postgresql-16-build where it is still (compute_query_id = off)? Am i missing something? :)

Mmm, all 3 (14/15/16) workflows were edited.

[Naeem-Akhter]

@artemgavrilov
Any reason that in this PR we have this setting only for postgresql-14-build & postgresql-15-build ('compute_query_id = regress). But not for postgresql-16-build where it is still (compute_query_id = off)? Am i missing something? :)

Mmm, all 3 (14/15/16) workflows were edited.

Then I guess, somehow GH was showing me wrong diff of changes. But change is reflected in your working branch. :)

Thanks!

[Naeem-Akhter]

Looks good to me!