Re: pg_upgrade using appname to lock out other users

From: Christopher Browne <cbbrowne(at)gmail(dot)com>
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 17:47:56
Message-ID: BANLkTinQSeSQRMaPHfko6Pcki6m5dVhSjw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Jun 15, 2011 at 5:35 PM, Bruce Momjian <bruce(at)momjian(dot)us> wrote:
> This requires no new backend code.  We could even _require_ the port
> number to be specified in pg_upgrade.

+1... That seems to have lots of nice properties.
--
When confronted by a difficult problem, solve it by reducing it to the
question, "How would the Lone Ranger handle this?"

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Kevin Grittner 2011-06-15 18:14:28 Re: Small SSI issues
Previous Message Bruce Momjian 2011-06-15 17:35:53 Re: pg_upgrade using appname to lock out other users