Re: pg_upgrade using appname to lock out other users
Bruce Momjian <bruce@momjian.us>
From: Bruce Momjian <bruce@momjian.us>
To: Jesper Krogh <jesper@krogh.cc>
Cc: pgsql-hackers <pgsql-hackers@postgresql.org>
Date: 2011-06-15T12:02:59Z
Lists: pgsql-hackers
Jesper Krogh wrote: > On 2011-06-15 05:01, 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.) > Couldn't the -b flag also imply a very strict hba.conf configuration, that > essentially only lets pg_upgrade in..? Yes, it could. What rules would we use? We could prohibit non-local connections. -- Bruce Momjian <bruce@momjian.us> http://momjian.us EnterpriseDB http://enterprisedb.com + It's impossible for everything to be true. +