-
Notifications
You must be signed in to change notification settings - Fork 21
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
flowmachine should own all cache tables #4714
Comments
Re-opening because the currently-implemented trigger doesn't actually affect flowmachine-created cache tables, because 'CREATE TABLE AS' (used to store a flowmachine query result) is a different command from 'CREATE TABLE' (for which the trigger is defined). |
Nope, still not working 🤦 Looks like it doesn't trigger if the 'CREATE TABLE AS' command is within an 'EXPLAIN' statement... |
So we can:
|
Can't do the first (pg_tables is a view, no triggers allowed on system tables). Issue with the third is that we currently allow different names for the flowmachine user, so you can't arbitrarily assign ownership to |
The flowmachine user in Flowdb needs to be the owner of all cache tables in cache schema, otherwise the flowmachine server will be unable to properly clean the cache and error out in trying to do so. Should either explicitly set the owner of the table to flowmachine user, or, there should be a trigger set in Flowdb to do this.
The text was updated successfully, but these errors were encountered: