Re: pgsql: Adjust user-facing documentation to explain why we don't check

From: Magnus Hagander <magnus(at)hagander(dot)net>
To: Dave Page <dpage(at)postgresql(dot)org>
Cc: Bruce Momjian <bruce(at)momjian(dot)us>, Andrew Dunstan <andrew(at)dunslane(dot)net>, Tom Lane <tgl(at)postgresql(dot)org>, pgsql-committers(at)postgresql(dot)org
Subject: Re: pgsql: Adjust user-facing documentation to explain why we don't check
Date: 2007-02-20 20:04:00
Message-ID: 45DB5430.5060004@hagander.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

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.

//Magnus

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Dave Page 2007-02-20 20:06:34 Re: pgsql: Adjust user-facing documentation to explain why we don't check
Previous Message Bruce Momjian 2007-02-20 19:59:18 pgsql: Update "encode" documentation to mention that 'escape' only