Could we continue to use our existing connection pool (via our app
server) and every time the application 'gets' a connection (as a
superuser) , we then 'SET SESSION AUTHORIZATION' to the appropriate user
who is performing the action?
>>Under the new scheme, we are limited by max_connections
>>(postgresql.conf)...and would return an error immediately when no
>>connections were available. Is there any way to mitigate this?
>>
>>
>
>This is doubtless the worst problem...
>
> regards, tom lane
>
>
