From: | ITAGAKI Takahiro <itagaki(dot)takahiro(at)oss(dot)ntt(dot)co(dot)jp> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: pg_stat_statements |
Date: | 2008-06-16 02:11:40 |
Message-ID: | 20080616105922.7514.52131E4D@oss.ntt.co.jp |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> ITAGAKI Takahiro <itagaki(dot)takahiro(at)oss(dot)ntt(dot)co(dot)jp> writes:
> > Postgres 8.4 has pg_stat_user_functions view to track number of calls
> > of stored functions and time spent in them. Then, I'm thinking a
> > "sql statement" version of similar view -- pg_stat_statements.
>
> We don't have any system-wide names for statements, so this seems
> pretty ill-defined and of questionable value. Showing the text of
> statements in a view also has security problems.
Thanks. I see I have to consider security problems in whatever way I can.
I'm thinking to use hash values as system-wide IDs. Users who don't have
permissions can only see those meaningless values. SQL strings will be
hidden just same as pg_stat_activity.
Regards,
---
ITAGAKI Takahiro
NTT Open Source Software Center
From | Date | Subject | |
---|---|---|---|
Next Message | ITAGAKI Takahiro | 2008-06-16 02:31:59 | Re: pg_stat_statements |
Previous Message | Abhijit Menon-Sen | 2008-06-16 02:01:21 | psql: \edit-function <function-name> |