| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
| Cc: | pgsql-hackers(at)postgreSQL(dot)org |
| Subject: | Re: WIP: getting rid of the pg_database flat file |
| Date: | 2009-08-12 01:10:06 |
| Message-ID: | 2132.1250039406@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
> Tom Lane wrote:
>> Really? And how would pgbouncer be depending on that?
> ==== auth_file ====
> The name of the file to load user names and passwords from. The file format
> is the same as the PostgreSQL pg_auth/pg_pwd file, so this setting can be
> pointed directly to one of those backend files.
Considering that we feel free to whack that file format around, and that
it's stored in a directory that non-postgres users shouldn't even be
able to read, I think this argument is just silly. The only alternative
fix that was proposed in this thread
http://archives.postgresql.org/pgsql-performance/2009-08/msg00094.php
involved changing the flat files into a format that would definitely not
be easily readable by other programs, anyway.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2009-08-12 01:11:37 | Re: Why is vacuum_freeze_min_age 100m? |
| Previous Message | Tom Lane | 2009-08-12 01:05:29 | Re: pgindent timing (was Re: [COMMITTERS] pgsql: Refactor NUM_cache_remove calls in error report path to a PG_TRY) |