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

From Andrew Dunstan
Subject Re: pg_upgrade using appname to lock out other users
Date
Msg-id 4DF8BC31.6020105@dunslane.net
Whole thread Raw
In response to 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
Re: pg_upgrade using appname to lock out other users
List pgsql-hackers

On 06/14/2011 11:01 PM, Bruce Momjian wrote:
> You might remember we added a postmaster/postgres -b switch to indicate
> binary upgrade mode.  The attached patch prevents any client without an
> application_name of 'binary-upgrade' from connecting to the cluster
> while it is binary upgrade mode.  This helps prevent unauthorized users
> from connecting during the upgrade.  This will not help for clusters
> that do not have the -b flag, e.g. pre-9.1.
>
> Does this seem useful?  Something for 9.1 or 9.2?
>
> This idea came from Andrew Dunstan via IRC during a pg_upgrade run by
> Stephen Frost when some clients accidentally connected.  (Stephen reran
> pg_upgrade successfully.)
>

What I actually had in mind was rather different: an HBA mechanism based 
on appname. But on second thoughts maybe the protocol wouldn't support that.

cheers

andrew


pgsql-hackers by date:

Previous
From: Merlin Moncure
Date:
Subject: Re: psql describe.c cleanup
Next
From: Christopher Browne
Date:
Subject: Re: pg_upgrade using appname to lock out other users