SET LOCAL doesn't become undefined after transaction is commited

2020-03-18 Thread Kostya
Hi We are using dynamic settings via SET LOCAL for row level security. I would like to clarify that I'm seeing the correct behaviour I create a new session to the database, I run the following query: SELECT current_setting("session.my_tenant_id"); I will get the following error: pq: unrecognized

Re: SET LOCAL doesn't become undefined after transaction is commited

2020-03-18 Thread Kostya
d following your post that this may not scale well or perhaps have some security issues I'm not aware of. What is your take on this? Thanks in advance. On Wed, Mar 18, 2020 at 4:16 PM Tom Lane wrote: > Kostya writes: > > However, once I run the following transaction > >