Received: from postgresql.org.org (webmail.postgresql.org [216.126.85.28]) by postgresql.org (8.11.3/8.11.4) with SMTP id f77GGq695873 for ; Tue, 7 Aug 2001 12:16:52 -0400 (EDT) (envelope-from pgsql-general-owner@postgresql.org) Received: from myst.fourpalms.org (myst.jpl.nasa.gov [137.78.15.105]) by postgresql.org (8.11.3/8.11.4) with ESMTP id f7706Y692233; Mon, 6 Aug 2001 20:06:34 -0400 (EDT) (envelope-from lockhart@alumni.caltech.edu) Received: from alumni.caltech.edu (localhost.localdomain [127.0.0.1]) by myst.fourpalms.org (Postfix) with ESMTP id 550CBC584; Tue, 7 Aug 2001 00:07:40 +0000 (UTC) Message-ID: <3B6F314B.AC23AB5A@alumni.caltech.edu> Date: Tue, 07 Aug 2001 00:07:39 +0000 From: Thomas Lockhart Reply-To: thomas@pgsql.com Organization: PostgreSQL X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.2.19-4.1mdk i686) X-Accept-Language: en MIME-Version: 1.0 To: Peter Eisentraut , PostgreSQL Hackers Mailing List Cc: David Wheeler , postgres list Subject: Re: user guide References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Archive-Number: 200108/147 X-Sequence-Number: 13369 > > I have a suggestion, as well: I think the PostgreSQL documentatio could > > use a section that discusses all the maintenance issues in one place. > This is already on the TODO list. I've started expanding the Admin chapter on database recovery (expanding was easy; it has been "Any volunteers to write this?" for two or three years now). At the moment, I've split the info into two chapters on "Failure" (discussing various failure scenarios) and "Recovery". Comments and organizational suggestions are welcome. Will commit sometime soon so others can contribute if they would like. - Thomas