Re: pgsql: Keep pg_stat_statements' query texts in a file, not in shared me - Mailing list pgsql-committers

From Robert Haas
Subject Re: pgsql: Keep pg_stat_statements' query texts in a file, not in shared me
Date
Msg-id CA+TgmoY9U7K=yks0md6qQnL+55w3WsguNnPWAkadykdd93JKfQ@mail.gmail.com
Whole thread Raw
In response to Re: pgsql: Keep pg_stat_statements' query texts in a file, not in shared me  (KONDO Mitsumasa <kondo.mitsumasa@lab.ntt.co.jp>)
List pgsql-committers
On Mon, Jan 27, 2014 at 9:31 PM, KONDO Mitsumasa
<kondo.mitsumasa@lab.ntt.co.jp> wrote:
>> 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).
>
> I feel the sense of incongruity that is stored database data in text file.
> I'd like to hear from other people...

OK, I'll bite: I have no idea why you think that's a problem.  The
entire database is stored in a bunch of files in the same directory
tree as that text file.  If somebody can read the text file, they can
probably also read the entire contents of the database.  Sure, the
actual relations are binary data rather than *text* files, but if you
can read them, you can *most definitely* extract the whole database
contents, which is several orders of magnitude worse than anything you
can do with pg_stat_statements.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company


pgsql-committers by date:

Previous
From: Peter Geoghegan
Date:
Subject: Re: pgsql: Keep pg_stat_statements' query texts in a file, not in shared me
Next
From: Peter Geoghegan
Date:
Subject: Re: pgsql: Keep pg_stat_statements' query texts in a file, not in shared me