-
Notifications
You must be signed in to change notification settings - Fork 56
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
Bulk Operations for Postgres does not respect the PermanentTable setting #565
Comments
Hello @rabberbock , Thank you for reporting. This option is not yet supported for We will try to add the support to it if possible. Best Regards, Jon |
@JonathanMagnan Thanks for the update! I am actually seeing something else creating the session pinning, so will open up another issue for that. But yep, it would be nice to be able to customize that for Postgres as well. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
I would like Bulk operations to use a non temporary table for all Bulk Operations (to avoid connection pinning). However enabling this option either globally or per operation does not seem to have an effect.
Logs
CREATE TEMP TABLE ZZZProjects_468d3c9c_c5c1_4e54_badc_9aee50110677 AS SELECT etc....
Code
or
Is this expected for Postgres? Is there any alternative.
Thanks!
Further technical details
The text was updated successfully, but these errors were encountered: