Skip to content

Don't call into the Postgres planner anymore when we take over #846

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

Merged
merged 3 commits into from
Jun 19, 2025

Conversation

JelteF
Copy link
Collaborator

@JelteF JelteF commented Jun 17, 2025

In the past we needed to call into the Postgres planner for permission checking on Postgres tables. This has not been needed for a while now. We were still doing it out of caution for breaking other things, but it seems like calling standard_planner might be causing problems by itself too (see #845). Furthermore calling the regular planner is also quite a waste of CPU cycles.

In the past we needed to call into the Postgres planner for permission
checking on Postgres tables. This has not been needed for a while now.
We were still doing it out of caution for breaking other things, but it
seems like that might be causing problems by itself too. And also it's
quite a waste of CPU cycles.
@JelteF JelteF force-pushed the remove-additional-planner-call branch from 64ff71e to 59d5179 Compare June 17, 2025 22:34
@JelteF JelteF merged commit f42b4b0 into main Jun 19, 2025
6 checks passed
@JelteF JelteF deleted the remove-additional-planner-call branch June 19, 2025 08:54
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.

1 participant