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

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.

/D