Re: Resurrecting pg_upgrade - Mailing list pgsql-hackers

From Jon Jensen
Subject Re: Resurrecting pg_upgrade
Date
Msg-id Pine.LNX.4.58.0312162016140.1582@louche.swelter.net
Whole thread Raw
In response to Re: Resurrecting pg_upgrade  (Jan Wieck <JanWieck@Yahoo.com>)
Responses Re: Resurrecting pg_upgrade  ("scott.marlowe" <scott.marlowe@ihs.com>)
List pgsql-hackers
On Tue, 16 Dec 2003, Jan Wieck wrote:

> If you want to prevent "accidential" access, start postmaster on a 
> non-standard port.

That seems like an unfriendly thing to do. You'd have to check to see what 
port is "standard" for this particular installation, and pick something 
else. You may choose an unused port, but perhaps it needs to be used in a 
few minutes by some other process, but then will be occupied. The 
administrator may also not be happy to have an open port facing the world, 
or even just other possibly untrusted users on the same machine, assuming 
you bind to localhost.

Jon


pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: [PATCHES] Double Backslash example patch
Next
From: Jon Jensen
Date:
Subject: Re: [PATCHES] Double Backslash example patch