Closed TheOtherBrian1 closed 2 weeks ago
Hm, wait. Is this config applicable now that we use the Nix build?
@samrose It doesn't look like the settings in supautils.conf are being applied (maybe only a local thing) but
postgres=# set pg_net.ttl = '1s'
ERROR: parameter "pg_net.ttl" cannot be changed now
@samrose It doesn't look like the settings in supautils.conf are being applied (maybe only a local thing) but
postgres=# set pg_net.ttl = '1s' ERROR: parameter "pg_net.ttl" cannot be changed now
- is that the correct location for supautils config?
- does it apply locally?
I think you are right that those settings have not been wired in yet on local testing
I’ll be back in front of computer in a few and will get it working in local testing context
We did recently merge in a pr to develop that correctly used all of our configurations and migrations
cc @supabase/backend for a +1
What kind of change does this PR introduce?
Modified supautils configs
What is the current behavior?
pg_net variables and the log_lock_waits variable cannot be configured by users.
What is the new behavior?
Allows users to configure pg_net variables (other than database):
Gives users permission to log locks that last for more than 1s
Additional context
Add any other context or screenshots.