Dave Page wrote:
> Magnus Hagander wrote:
>> It would break insofar that it wouldn't work. the pgpass file. It will
>> of course not break *windows*, but people will consider PostgreSQL broken.
> Please explain why it won't work. *Existing* pgpass files would need to
> be secured, but that could be handled with documentation and suitable
> checks and hints in pgAdmin/libpq. New pgpass files created by pgAdmin
> (or other apps) would simply need to be secured by those apps at
> creation time.
Files created using notepad (or whatever) will not work. Unless you
manually fiddle around with the permissions.
In response to
pgsql-committers by date
|Next:||From: Dave Page||Date: 2007-02-20 20:06:34|
|Subject: Re: pgsql: Adjust user-facing documentation to explain
why we don't check|
|Previous:||From: Bruce Momjian||Date: 2007-02-20 19:59:18|
|Subject: pgsql: Update "encode" documentation to mention that 'escape' only |