Received: from sss2.sss.pgh.pa.us (sss.pgh.pa.us [209.114.166.2])
	by hub.org (8.10.1/8.10.1) with ESMTP id e55Fd1O45986;
	Mon, 5 Jun 2000 11:39:01 -0400 (EDT)
Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1])
	by sss2.sss.pgh.pa.us (8.9.3/8.9.3) with ESMTP id LAA12136;
	Mon, 5 Jun 2000 11:37:43 -0400 (EDT)
To: Bruce Momjian <pgman@candle.pha.pa.us>
cc: PostgreSQL-development <pgsql-hackers@postgresql.org>,
	PostgreSQL-documentation <docs@postgresql.org>
Subject: Re: [HACKERS] INSTALL/install.sgml file 
In-reply-to: <200006051058.GAA20872@candle.pha.pa.us> 
References: <200006051058.GAA20872@candle.pha.pa.us>
Comments: In-reply-to Bruce Momjian <pgman@candle.pha.pa.us>
	message dated "Mon, 05 Jun 2000 06:58:27 -0400"
Date: Mon, 05 Jun 2000 11:37:43 -0400
Message-ID: <12133.960219463@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
X-Archive-Number: 200006/7

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.

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 ;-).)

			regards, tom lane