Jeff Amiel <[EMAIL PROTECTED]> writes:
> 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?
That would work to the extent that you filter SQL commands so a
nefarious user can't issue his own 'SET SESSION AUTHORIZATION'
to become someone else ...
regards, tom lane
---------------------------(end of broadcast)---------------------------
TIP 4: Don't 'kill -9' the postmaster
