Re: pg_upgrade using appname to lock out other users - Mailing list pgsql-hackers

From Tom Lane
Subject Re: pg_upgrade using appname to lock out other users
Date
Msg-id 28881.1308174615@sss.pgh.pa.us
Whole thread Raw
In response to Re: pg_upgrade using appname to lock out other users  (Bruce Momjian <bruce@momjian.us>)
Responses Re: pg_upgrade using appname to lock out other users
List pgsql-hackers
Bruce Momjian <bruce@momjian.us> writes:
> Peter Eisentraut wrote:
>> On non-Windows servers you could get this even safer by disabling the
>> TCP/IP socket altogether, and placing the Unix-domain socket in a
>> private temporary directory.  The "port" wouldn't actually matter then.

> Yes, it would be nice to just create the socket in the current
> directory.  The fact it doesn't work on Windows would cause our docs to
> have to differ for Windows, which seems unfortunate.

It still wouldn't be bulletproof against someone running as the postgres
user, so probably not worth the trouble.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Simon Riggs
Date:
Subject: Re: FK NOT VALID can't be deferrable?
Next
From: Simon Riggs
Date:
Subject: Re: FK NOT VALID can't be deferrable?