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

Re: [HACKERS] INSTALL/install.sgml file

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, PostgreSQL-documentation <docs(at)postgresql(dot)org>
Subject: Re: [HACKERS] INSTALL/install.sgml file
Date: 2000-06-06 21:58:45
Message-ID: Pine.LNX.4.21.0006062126070.17370-100000@localhost.localdomain (view raw, whole thread or download thread mbox)
Lists: pgsql-docspgsql-hackers
Bruce Momjian writes:

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

I think the installation instructions should say "If you are upgrading
from an existing installation, read the Administrator's Guide for backing
and restoring your data." The said guide contains a chapter discussing
these issues in detail (or at least it contains a chapter on it and we
should add some detail :). This sort of thing can't be replaced by three

Just the other day I griped about the fact that the installation
instructions are in fact a chapter of the administrator's guide, which
breaks the internal and external organization and the flow of information
of both the installation instructions and the administrator's guide.

Can anyone see that concern?

Peter Eisentraut                  Sernanders väg 10:115
peter_e(at)gmx(dot)net                   75262 Uppsala            Sweden

In response to


pgsql-docs by date

Next:From: Bruce MomjianDate: 2000-06-07 01:36:36
Subject: Re: [HACKERS] INSTALL/install.sgml file
Previous:From: GaganDate: 2000-06-06 20:13:09

pgsql-hackers by date

Next:From: Peter EisentrautDate: 2000-06-06 22:07:54
Subject: Advisory: configure script has moved
Previous:From: Tom LaneDate: 2000-06-06 21:40:47
Subject: Re: Odd release numbers for development versions?

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