Re: Resurrecting pg_upgrade - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Resurrecting pg_upgrade
Date
Msg-id 21717.1071261104@sss.pgh.pa.us
Whole thread Raw
In response to Re: Resurrecting pg_upgrade  ("Marc G. Fournier" <scrappy@postgresql.org>)
Responses Re: Resurrecting pg_upgrade  (Jan Wieck <JanWieck@Yahoo.com>)
List pgsql-hackers
"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.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Resurrecting pg_upgrade
Next
From: Andrew Dunstan
Date:
Subject: Re: Resurrecting pg_upgrade