Re: Resurrecting pg_upgrade - Mailing list pgsql-hackers

From Jan Wieck
Subject Re: Resurrecting pg_upgrade
Date
Msg-id 3FDF4E19.3050207@Yahoo.com
Whole thread Raw
In response to Re: Resurrecting pg_upgrade  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Resurrecting pg_upgrade
Re: Resurrecting pg_upgrade
List pgsql-hackers
Tom Lane wrote:

> "Marc G. Fournier" <scrappy@postgresql.org> writes:
>> Then again, in the case of pg_upgrade, wouldn't just disabling access from
>> anywhere except localhost prevent others from getting in?
> 
> Not if your normal operating mode includes connections from clients
> running locally.  I really don't see any clean way to ensure that
> pg_upgrade (and subsidiary pg_dump runs invoked by it) are the only
> ones allowed to connect to the database, if we keep the normal
> postmaster running.  But if we shut down the postmaster then it's
> trivial.

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


Jan

-- 
#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me.                                  #
#================================================== JanWieck@Yahoo.com #



pgsql-hackers by date:

Previous
From: "Dann Corbit"
Date:
Subject: Re: [pgsql-hackers-win32] [PATCHES] fork/exec patch
Next
From: Alvaro Herrera
Date:
Subject: Re: [PATCHES] Double Backslash example patch