Re: Auto-explain patch - Mailing list pgsql-hackers

From Marko Kreen
Subject Re: Auto-explain patch
Date
Msg-id e51f66da0807090422i23ae7345h2b4ba807951532b4@mail.gmail.com
Whole thread Raw
In response to Re: Auto-explain patch  (ITAGAKI Takahiro <itagaki.takahiro@oss.ntt.co.jp>)
Responses Re: Auto-explain patch  (Dean Rasheed <dean_rasheed@hotmail.com>)
List pgsql-hackers
On 7/9/08, ITAGAKI Takahiro <itagaki.takahiro@oss.ntt.co.jp> wrote:
>  Dean Rasheed <dean_rasheed@hotmail.com> wrote:
> > * client_sql_trace = on | off - settable by a normal user to allow a
>  > client session to see the sql_trace output. If this parameter is on,
>  > the sql_trace will be logged as NOTICE output.
>
>
> In terms of security, is it ok to show normal users SQLs used in functions
>  that are owned by other users? Users can call not-owned functions only if
>  they have EXECUTE privilege on them. -- presently we can see function
>  bodies from pg_proc.prosrc freely, though.

Different owner is not a problem, but SECURITY DEFINER may be.

That can be solved by turning the setting off on entry to such function,
by non-superuser.  Like we handle search_path.

-- 
marko


pgsql-hackers by date:

Previous
From: Simon Riggs
Date:
Subject: Re: Auto-explain patch
Next
From: Gregory Stark
Date:
Subject: Re: Identifier case folding notes