"A.M." <agentm@themactionfaction.com> writes:
> It seems I am stuck so please allow me to propose an extension:
> SET SESSION AUTHORIZATION user [WITH PASSWORD 'password];
This idea is extremely unlikely to be accepted, as the password would be
at risk of exposure in places like the pg_stat_activity view.
I think the correct way to do what you want is via a SECURITY DEFINER
function.
regards, tom lane
