| From: | Peter Geoghegan <pg(at)heroku(dot)com> |
|---|---|
| To: | KONDO Mitsumasa <kondo(dot)mitsumasa(at)lab(dot)ntt(dot)co(dot)jp> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-committers(at)postgresql(dot)org |
| Subject: | Re: pgsql: Keep pg_stat_statements' query texts in a file, not in shared me |
| Date: | 2014-01-28 02:07:18 |
| Message-ID: | CAM3SWZT4w1UofAArzvHnMmFA3HLnYMok3gjESDQaUd=U_ZgpTg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
On Mon, Jan 27, 2014 at 6:04 PM, KONDO Mitsumasa
<kondo(dot)mitsumasa(at)lab(dot)ntt(dot)co(dot)jp> wrote:
> It is written in documents; "For security reasons, non-superusers are not
> allowed to see the text of queries executed by other users." Is root user
> superuser? And initdb user might change to non-superuser after creating
> database cluster. In japan, database operation user isn't always database
> admin. Because database admin's salary is expensive than system operator's.
initdb will not run as a superuser to begin with. It flatly refuses.
Why is your concern with pg_stat_statements after this patch in particular?
You'll need to serialize the file at least once before seeing it, but
then it's there for good (on old versions, before Magnus got annoyed
that that affected basebackups).
--
Peter Geoghegan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2014-01-28 02:08:00 | Re: pgsql: Keep pg_stat_statements' query texts in a file, not in shared me |
| Previous Message | KONDO Mitsumasa | 2014-01-28 02:04:36 | Re: pgsql: Keep pg_stat_statements' query texts in a file, not in shared me |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2014-01-28 02:08:00 | Re: pgsql: Keep pg_stat_statements' query texts in a file, not in shared me |
| Previous Message | KONDO Mitsumasa | 2014-01-28 02:04:36 | Re: pgsql: Keep pg_stat_statements' query texts in a file, not in shared me |