We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Hello,
I am currently experiencing a problem with the calculation of EXCLUSIVE times for BitmapHeapScan/BitmapIndexScan with workers.
With the following plan https://explain.dalibo.com/plan/7a74fb44bggc5b9g ( text )
It seems that PEV2 divides the BitmapIndexScan time as if it were using Workers. This is not normally the case.
We got the same behavior with this plan : https://explain.dalibo.com/plan/g75eg7d22dcbd66b ( json )
( I am relying on the following document : https://www.postgresql.org/docs/current/parallel-plans.html#PARALLEL-SCANS . )
Could you please address this issue ?
Best regards,
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Hello,
I am currently experiencing a problem with the calculation of EXCLUSIVE times for BitmapHeapScan/BitmapIndexScan with workers.
With the following plan https://explain.dalibo.com/plan/7a74fb44bggc5b9g ( text )
It seems that PEV2 divides the BitmapIndexScan time as if it were using Workers. This is not normally the case.
We got the same behavior with this plan : https://explain.dalibo.com/plan/g75eg7d22dcbd66b ( json )
( I am relying on the following document : https://www.postgresql.org/docs/current/parallel-plans.html#PARALLEL-SCANS . )
Could you please address this issue ?
Best regards,
The text was updated successfully, but these errors were encountered: