Received: from localhost (unknown [200.46.204.187]) by postgresql.org (Postfix) with ESMTP id 659AE2E331E for ; Thu, 10 Jan 2008 15:27:42 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.187]) (amavisd-maia, port 10024) with ESMTP id 75940-08 for ; Thu, 10 Jan 2008 15:27:23 -0400 (AST) Received: from mail2.yozons.com (mail2.yozons.com [63.251.168.97]) by postgresql.org (Postfix) with ESMTP id BD7422E31D1 for ; Thu, 10 Jan 2008 15:27:36 -0400 (AST) Received: from [192.168.1.2] (pool-71-164-18-27.sttlwa.fios.verizon.net [71.164.18.27]) (authenticated bits=0) by mail2.yozons.com (8.12.10/8.12.10) with ESMTP id m0AJRZlG022578 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for ; Thu, 10 Jan 2008 11:27:35 -0800 Message-ID: <478671A9.9070404@computer.org> Date: Thu, 10 Jan 2008 11:27:37 -0800 From: David Wall Reply-To: d.wall@computer.org User-Agent: Thunderbird 2.0.0.9 (Windows/20071031) MIME-Version: 1.0 To: pgsql-admin@postgresql.org Subject: PITR warm-standby with 8.2 setup questions Content-Type: multipart/alternative; boundary="------------070805000300020302020903" X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200801/111 X-Sequence-Number: 27885 This is a multi-part message in MIME format. --------------070805000300020302020903 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit I'm trying to get WAL file copying working across two systems. It seems pretty straightforward to handle this in the "archive_command" of the primary, in which I am able to copy the files easily to a staging area for the backup system. On the backup system, I have the recovery.conf pointing to my script, but I have a few questions on how that program should behave, and whether I'd be much wiser to just use pg_standby instead of my own script. 1) I do not want to give the backup PG a file unless it's a "complete" file. I don't want to give it one that is currently in the middle of being transferred from the primary to the backup system (or a backup copy that failed in the middle). Most of my files are 16777216 bytes, so I initially checked that size. But I found that there are files with a name like '0000000100000002000000DC.00000020.backup' that is only 272 bytes. Will that file also need to be given to PG recovery, and if so, how are most determining if a small file is complete or just a partial from the copy? 2) On the recovery side, the %p and %f values are giving me %p of 'pg_xlog/RECOVERYXLOG' and %f of '0000000100000003000000B1'. Can I confirm that this means my recover program should find a file named '0000000100000003000000B1' in my backup system's WAL archive and copy it to the file named 'pg_xlog/RECOVERYXLOG', or should I put it into 'pg_xlog/0000000100000003000000B1'? 3) On the backup PG, is it correct that I have to remove backup_label, postmaster.pid and pg_xlog if they are part of the or TAR backup from the primary's PGDATA area? Thanks, David --------------070805000300020302020903 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit
I'm trying to get WAL file copying working across two systems.  It seems pretty straightforward to handle this in the "archive_command" of the primary, in which I am able to copy the files easily to a staging area for the backup system.

On the backup system, I have the recovery.conf pointing to my script, but I have a few questions on how that program should behave, and whether I'd be much wiser to just use pg_standby instead of my own script.

1) I do not want to give the backup PG a file unless it's a "complete" file.  I don't want to give it one that is currently in the middle of being transferred from the primary to the backup system (or a backup copy that failed in the middle).  Most of my files are 16777216 bytes, so I initially checked that size.  But I found that there are files with a name like '0000000100000002000000DC.00000020.backup' that is only 272 bytes.  Will that file also need to be given to PG recovery, and if so, how are most determining if a small file is complete or just a partial from the copy?

2) On the recovery side, the %p and %f values are giving me %p of 'pg_xlog/RECOVERYXLOG' and %f of '0000000100000003000000B1'.  Can I confirm that this means my recover program should find a file named '0000000100000003000000B1' in my backup system's WAL archive and copy it to the file named 'pg_xlog/RECOVERYXLOG', or should I put it into 'pg_xlog/0000000100000003000000B1'?

3) On the backup PG, is it correct that I have to remove backup_label, postmaster.pid and pg_xlog if they are part of the or TAR backup from the primary's PGDATA area?

Thanks,
David

--------------070805000300020302020903--