Received: from localhost (unknown [200.46.204.182]) by postgresql.org (Postfix) with ESMTP id 434B02E4557 for ; Fri, 21 Dec 2007 22:33:57 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.182]) (amavisd-maia, port 10024) with ESMTP id 98954-02 for ; Fri, 21 Dec 2007 22:33:46 -0400 (AST) Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id A2BF32E44E3 for ; Fri, 21 Dec 2007 22:33:52 -0400 (AST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.1/8.14.1) with ESMTP id lBM2Xo04015489; Fri, 21 Dec 2007 21:33:50 -0500 (EST) To: Tom Davies cc: pgsql-admin@postgresql.org Subject: Re: on-line backup questions In-reply-to: <0FBA939C-2ED1-4400-BD3B-5290193837D0@gmail.com> References: <0FBA939C-2ED1-4400-BD3B-5290193837D0@gmail.com> Comments: In-reply-to Tom Davies message dated "Sat, 22 Dec 2007 13:02:50 +1100" Date: Fri, 21 Dec 2007 21:33:50 -0500 Message-ID: <15488.1198290830@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200712/201 X-Sequence-Number: 27718 Tom Davies writes: > 1. Purely out of curiousity, what's the nnnnnnnn.history file which is > requested from the archive when you restore? Read the doc section about timelines --- if a history file exists, it's needed to allow proper tracing of the "timeline" through multiple recovery attempts. > 3. What's the best thing to do when I deliberately shut down > PostgreSQL (i.e. pg_ctl stop)? When I start again I will be restoring > from the most recent backup and rolling forward over the archived WAL > files. I believe that shutdown leaves me with unarchived WAL files in > pg_xlog. Yeah, you should archive the latest WAL file, but in 8.0 you'd have to do that manually. (IIRC there isn't even a forced-xlog-switch function in that version to help you.) > 4. I'm using PostgreSQL 8.0 -- are there any significant improvements > in on-line backups in later versions? Get thyself onto 8.2 ASAP, or maybe go to 8.3 shortly after the holidays. 8.0 is basically our stone age for PITR support; while the concepts haven't changed since then, we've filed off a whole lot of rough edges in operational details. In a situation where you're depending on archive recovery as much as this, you *need* those fixes. regards, tom lane