Re: pg_upgrade using appname to lock out other users

From: Stephen Frost <sfrost(at)snowman(dot)net>
To: Bruce Momjian <bruce(at)momjian(dot)us>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Christopher Browne <cbbrowne(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: pg_upgrade using appname to lock out other users
Date: 2011-06-16 12:20:20
Message-ID: 20110616122020.GC32313@tamriel.snowman.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

* Bruce Momjian (bruce(at)momjian(dot)us) wrote:
> Right, we will re-check at the time they do the actual upgrade. This
> was requested so people can prepare for the real upgrade without having
> to stop their live server.

Exactly. A very good thing to have, and something which I needed and
would have been very upset to not have. My case was PostGIS being in
the old cluster and not available in the new cluster. I had to fix that
before moving forward, but I'm glad that didn't require shutting down
the old cluster to find out.

Thanks,

Stephen

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Radosław Smogura 2011-06-16 12:30:27 Patch - Debug builds without optimization
Previous Message Heikki Linnakangas 2011-06-16 12:15:44 Re: Latch implementation that wakes on postmaster death on both win32 and Unix