Skip site navigation (1) Skip section navigation (2)

Re: Upgrading rant.

From: Oliver Elphick <olly(at)lfix(dot)co(dot)uk>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>,Hannu Krosing <hannu(at)tm(dot)ee>, mlw <pgsql(at)mohawksoft(dot)com>,Lamar Owen <lamar(dot)owen(at)wgcr(dot)org>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Upgrading rant.
Date: 2003-01-04 04:02:28
Message-ID: 1041652948.1198.15.camel@linda.lfix.co.uk (view raw or flat)
Thread:
Lists: pgsql-hackers
On Sat, 2003-01-04 at 02:17, Tom Lane wrote:

> There isn't any simple way to lock *everyone* out of the DB and still
> allow pg_upgrade to connect via the postmaster, and even if there were,
> the DBA could too easily forget to do it.

I tackled this issue in the Debian upgrade scripts.

I close the running postmaster and open a new postmaster using a
different port, so that normal connection attempts will fail because
there is no postmaster running on the normal port.

-- 
Oliver Elphick                                Oliver(dot)Elphick(at)lfix(dot)co(dot)uk
Isle of Wight, UK                             http://www.lfix.co.uk/oliver
GPG: 1024D/3E1D0C1C: CA12 09E0 E8D5 8870 5839  932A 614D 4C34 3E1D 0C1C
                 ========================================
     "But because of his great love for us, God, who is rich
      in mercy, made us alive with Christ even when we were
      dead in transgressions-it is by grace you have been
      saved."        Ephesians 2:4,5 


In response to

Responses

pgsql-hackers by date

Next:From: Dan LangilleDate: 2003-01-04 04:16:26
Subject: Re: Upgrading rant.
Previous:From: mlwDate: 2003-01-04 03:39:08
Subject: Re: Threads

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group