Re: current_user inside SECURITY DEFINER function?

From: Stephen Frost <sfrost(at)snowman(dot)net>
To: Peter Eisentraut <peter_e(at)gmx(dot)net>
Cc: Richard Hayward <richard(at)tortoise(dot)demon(dot)co(dot)uk>, pgsql-general(at)postgresql(dot)org
Subject: Re: current_user inside SECURITY DEFINER function?
Date: 2005-07-06 20:27:44
Message-ID: 20050706202744.GD24207@ns.snowman.net
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-general

* Peter Eisentraut (peter_e(at)gmx(dot)net) wrote:
> Stephen Frost wrote:
> > * Richard Hayward (richard(at)tortoise(dot)demon(dot)co(dot)uk) wrote:
> > > Is there any way of getting the user?
> >
> > You might try session_user. 8.1 will hopefully clean this up some.
>
> Why would it? This is SQL standard behavior that should not be changed.

It'll match the SQL spec, I'm not sure it does now, that was more of my
point than anything else. :)

Stephen

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Clark Allan 2005-07-06 20:45:30 ms-sql OUTPUT equivalent
Previous Message Richard Hayward 2005-07-06 20:19:18 Re: current_user inside SECURITY DEFINER function?