From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
---|---|
To: | Bruce Momjian <bruce(at)momjian(dot)us> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgreSQL(dot)org> |
Subject: | Re: pg_upgrade using appname to lock out other users |
Date: | 2011-06-15 14:05:37 |
Message-ID: | 4DF8BC31.6020105@dunslane.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | 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
From | Date | Subject | |
---|---|---|---|
Next Message | Christopher Browne | 2011-06-15 14:16:57 | Re: pg_upgrade using appname to lock out other users |
Previous Message | Merlin Moncure | 2011-06-15 14:01:50 | Re: psql describe.c cleanup |