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:50:34 |
Message-ID: | CAM3SWZSjgDpTK9ZKOV9-15CO4uP+=N90HZjiqqWUB_oaQX4AfA@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:31 PM, KONDO Mitsumasa
<kondo(dot)mitsumasa(at)lab(dot)ntt(dot)co(dot)jp> wrote:
> No. I don't say root user is superuser. Executing initdb user will be
> postgres superuser. But it can change non-superuser after creating database.
Okay. I still don't understand what your point is, or how this patch
makes any worse what you'd consider to be a general problem. It
doesn't even differ from a security standpoint to the original
pg_stat_statements from 2009.
> I feel the sense of incongruity that is stored database data in text file.
> I'd like to hear from other people...
I think it's incongruous that you chose to make your opinion known at
this time and in this way. You knew about this patch several months
ago; are your surprised that it does what it was prominently
advertised to do?
--
Peter Geoghegan
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Geoghegan | 2014-01-28 06:33:54 | Re: [COMMITTERS] pgsql: Keep pg_stat_statements' query texts in a file, not in shared me |
Previous Message | Robert Haas | 2014-01-28 02:40:38 | Re: pgsql: Keep pg_stat_statements' query texts in a file, not in shared me |
From | Date | Subject | |
---|---|---|---|
Next Message | Sawada Masahiko | 2014-01-28 03:17:29 | Re: Add force option to dropdb |
Previous Message | Robert Haas | 2014-01-28 02:41:23 | Re: Freezing without write I/O |