From: | "Marko Kreen" <markokr(at)gmail(dot)com> |
---|---|
To: | "ITAGAKI Takahiro" <itagaki(dot)takahiro(at)oss(dot)ntt(dot)co(dot)jp> |
Cc: | "Dean Rasheed" <dean_rasheed(at)hotmail(dot)com>, "Simon Riggs" <simon(at)2ndquadrant(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Auto-explain patch |
Date: | 2008-07-09 11:22:45 |
Message-ID: | e51f66da0807090422i23ae7345h2b4ba807951532b4@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 7/9/08, ITAGAKI Takahiro <itagaki(dot)takahiro(at)oss(dot)ntt(dot)co(dot)jp> wrote:
> Dean Rasheed <dean_rasheed(at)hotmail(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Simon Riggs | 2008-07-09 11:22:56 | Re: Auto-explain patch |
Previous Message | Marko Kreen | 2008-07-09 11:05:03 | review: table function support |