New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Mark cagg_watermark parallel safe #5240
Mark cagg_watermark parallel safe #5240
Conversation
Codecov Report
@@ Coverage Diff @@
## main #5240 +/- ##
===========================================
+ Coverage 63.10% 89.00% +25.89%
===========================================
Files 225 225
Lines 45666 51821 +6155
===========================================
+ Hits 28818 46123 +17305
+ Misses 16848 5698 -11150
Continue to review full report at Codecov.
|
a9e56d7
to
fc8c12f
Compare
@lkshminarayanan, @akuzm: please review this pull request.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good idea to mark it parallel safe.
The `cagg_watermark` function perform just read-only operations so is safe to make it parallel safe to take advantage of the Postgres parallel query. Since 2.7 when we introduced the new Continuous Aggregate format we don't use partials anymore and those aggregate functions `partialize_agg` and `finalize_agg` are not parallel safe, so make no sense don't take advantage of Postgres parallel query for realtime Continuous Aggregates.
fc8c12f
to
6543fae
Compare
The
cagg_watermark
function perform just read-only operations so issafe to make it parallel safe to take advantage of the Postgres
parallel query.
Since 2.7 when we introduced the new Continuous Aggregate format we
don't use partials anymore and those aggregate functions
partialize_agg
andfinalize_agg
are not parallel safe, so make nosense don't take advantage of Postgres parallel query for realtime
Continuous Aggregates.
Disable-Check: force-changelog-changed
Related to #4699