X-Original-To: pgsql-hackers-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id A678FD1EADE for ; Fri, 2 Apr 2004 00:58:31 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 78668-06 for ; Thu, 1 Apr 2004 20:58:32 -0400 (AST) Received: from mx1.neopolitan.us (mx1.neopolitan.us [65.87.16.224]) by svr1.postgresql.org (Postfix) with ESMTP id 6B8D1D1EAAE for ; Thu, 1 Apr 2004 20:58:28 -0400 (AST) Received: from [65.87.16.98] (HELO [10.0.0.210]) by mx1.neopolitan.us (CommuniGate Pro SMTP 4.1.8) with ESMTP-TLS id 3813228 for pgsql-hackers@postgresql.org; Thu, 01 Apr 2004 16:58:28 -0800 Subject: PITR for replication? From: "J. Andrew Rogers" To: pgsql-hackers@postgresql.org In-Reply-To: <406B6EDB.5040406@familyhealth.com.au> References: <5674.1080750914@sss.pgh.pa.us> <406B6EDB.5040406@familyhealth.com.au> Content-Type: text/plain Organization: Message-Id: <1080867508.29882.8.camel@localhost.localdomain> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.2.2 (1.2.2-5) Date: 01 Apr 2004 16:58:28 -0800 Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200404/11 X-Sequence-Number: 51933 I may be completely missing the point here, but it looks to me as though the PITR archival mechanism is also most of a native replication facility. Is there anyone reason this couldn't be extended to replication, and if so, is anyone planning on using it as such? My memory is fuzzy on this point, but I seem to recall that this is (was?) how replication is more-or-less done for many of the big commercial RDBMS. jrogers@neopolitan.com