Skip site navigation (1) Skip section navigation (2)

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

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Bruce Momjian <bruce(at)momjian(dot)us>
Cc: Magnus Hagander <magnus(at)hagander(dot)net>, Andrew Dunstan <andrew(at)dunslane(dot)net>, pgsql-committers(at)postgresql(dot)org
Subject: Re: pgsql: Adjust user-facing documentation to explain why we don't check
Date: 2007-02-20 18:43:47
Message-ID: 13681.1171997027@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-committers
Bruce Momjian <bruce(at)momjian(dot)us> writes:
> Magnus Hagander wrote:
>> PGPASSFILE takes a full path name, so you can put the file anywhere you
>> want. Just like on Unix.

> OK, so we _do_ need to check the permissions on pgpass on Win32, but we
> just don't know how to do that?

We could ignore PGPASSFILE on Windows, or restrict it to be in the
secure directory ...

			regards, tom lane

In response to

pgsql-committers by date

Next:From: Andrew DunstanDate: 2007-02-20 18:44:10
Subject: Re: pgsql: Adjust user-facing documentation to explain why we don't check
Previous:From: Magnus HaganderDate: 2007-02-20 18:43:43
Subject: Re: pgsql: Adjust user-facing documentation to explain why we don't check

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group