X-Original-To: pgsql-hackers-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id F3C20D1B18C for ; Thu, 15 Jul 2004 06:46:35 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 86927-02 for ; Thu, 15 Jul 2004 09:46:35 +0000 (GMT) Received: from linda-1.paradise.net.nz (bm-1a.paradise.net.nz [202.0.58.20]) by svr1.postgresql.org (Postfix) with ESMTP id 1BC2FD1B18A for ; Thu, 15 Jul 2004 06:46:26 -0300 (ADT) Received: from smtp-3.paradise.net.nz (smtp-3b.paradise.net.nz [202.0.32.212]) by linda-1.paradise.net.nz (Paradise.net.nz) with ESMTP id <0I0W00A0R0HI3W@linda-1.paradise.net.nz> for pgsql-hackers@postgresql.org; Thu, 15 Jul 2004 21:46:33 +1200 (NZST) Received: from coretech.co.nz (218-101-13-64.paradise.net.nz [218.101.13.64]) by smtp-3.paradise.net.nz (Postfix) with ESMTP id 176FEAE52D; Thu, 15 Jul 2004 21:45:50 +1200 (NZST) Date: Thu, 15 Jul 2004 21:47:50 +1200 From: Mark Kirkwood Subject: Re: Point in Time Recovery In-reply-to: <1089875702.17493.5539.camel@stromboli> To: Simon Riggs Cc: pgsql-hackers@postgresql.org Message-id: <40F652C6.4070007@coretech.co.nz> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=ISO-8859-1 Content-transfer-encoding: 7bit X-Accept-Language: en-us, en User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.6) Gecko/20040429 References: <200407141555.i6EFtnk22984@mail.osdl.org> <1089833620.17493.4624.camel@stromboli> <40F5E14A.4090003@coretech.co.nz> <1089875702.17493.5539.camel@stromboli> X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.0 tagged_above=0.0 required=5.0 tests= X-Spam-Level: X-Archive-Number: 200407/797 X-Sequence-Number: 56358 I tried what I thought was a straightforward scenario, and seem to have broken it :-( Here is the little tale 1) initdb 2) set archive_mode and archive_dest in postgresql.conf 3) startup 4) create database called 'test' 5) connect to 'test' and type 'checkpoint' 6) backup PGDATA using 'tar -zcvf' 7) create tables in 'test' and add data using COPY (exactly 2 logs worth) 8) shutdown and remove PGDATA 9) recover using 'tar -zxvf' 10) copy recovery.conf into PGDATA 11) startup This is what I get : LOG: database system was interrupted at 2004-07-15 21:24:04 NZST LOG: recovery command file found... LOG: restore_program = cp %s/%s %s LOG: recovery_target_inclusive = true LOG: recovery_debug_log = true LOG: starting archive recovery LOG: restored log file "0000000000000000" from archive LOG: checkpoint record is at 0/A48054 LOG: redo record is at 0/A48054; undo record is at 0/0; shutdown FALSE LOG: next transaction ID: 496; next OID: 25419 LOG: database system was not properly shut down; automatic recovery in progress LOG: redo starts at 0/A48094 LOG: restored log file "0000000000000001" from archive LOG: record with zero length at 0/1FFFFE0 LOG: redo done at 0/1FFFF30 LOG: restored log file "0000000000000001" from archive LOG: restored log file "0000000000000001" from archive PANIC: concurrent transaction log activity while database system is shutting down LOG: startup process (PID 13492) was terminated by signal 6 LOG: aborting startup due to startup process failure The concurrent access is a bit of a puzzle, as this is my home machine (i.e. I am *sure* noone else is connected!) Mark P.s : CVS HEAD from about 1 hour ago, PITR 5.2, FreeBSD 4.10 on x86