pg.ddx.io  pgsql-docs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Bruce Momjian <pgman@candle.pha.pa.us>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: PostgreSQL-development <pgsql-hackers@postgresql.org>
Cc: PostgreSQL-documentation <docs@postgresql.org>
Subject: Re: [HACKERS] INSTALL/install.sgml file
Date: Mon, 5 Jun 2000 13:05:02 -0400 (EDT)
Message-ID: <200006051705.NAA04033@candle.pha.pa.us> (raw)
In-Reply-To: <12133.960219463@sss.pgh.pa.us>

> Bruce Momjian <pgman@candle.pha.pa.us> writes:
> > In looking at the INSTALL/install.sgml files, I see that there are no
> > instructions for removing the /data directory after the backup, so 
> > initdb will succeed.  Should that be suggested after the backup is
> > performed?  If not, initdb will fail.  Also, I have to add something to
> > the initdb step to tell 7.* users they don't need initdb.
> 
> What?  It says "move the old directories out of the way" at the bottom
> of step 6.
> 

Oh, I see that now.  The trick was that people upgrading from 7.0 or
7.0.1 do not need to do pg_dumpall, nor move the old directory out of
the way, nor do an initdb, nor reload from pg_dumpall.

I put a note about who should run pg_dumpall (6.5.* or earlier), and
then later I mention that "If you did pg_dumpall..." move the old
directory out of the way, do initdb, and reload.  Seems it is OK now. 
Thanks.

> Possibly that should be promoted into a whole separate step, rather than
> being just an afterthought to killing the postmaster.
> 
> This step and step 11 should also mention pg_upgrade as a possible
> alternative to doing a full reload.  (But encourage people to make
> the backup anyway ;-).)

I got that into step 5:

      Rather than using pg_dumpall, pg_upgrade can often be used.



-- 
  Bruce Momjian                        |  http://www.op.net/~candle
  pgman@candle.pha.pa.us               |  (610) 853-3000
  +  If your life is a hard drive,     |  830 Blythe Avenue
  +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026



view thread (7+ messages)  latest in thread

Message-ID: <200006051705.NAA04033@candle.pha.pa.us>
Permalink:  ../200006051705.NAA04033@candle.pha.pa.us/
Also on:    postgresql.org/message-id/200006051705.NAA04033@candle.pha.pa.us

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-docs@postgresql.org
  Cc: pgman@candle.pha.pa.us, tgl@sss.pgh.pa.us, pgsql-hackers@postgresql.org, docs@postgresql.org
  Subject: Re: [HACKERS] INSTALL/install.sgml file
  In-Reply-To: <200006051705.NAA04033@candle.pha.pa.us>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox