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 7E548D1EBD1 for ; Fri, 2 Apr 2004 01:50:49 +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 96171-04 for ; Thu, 1 Apr 2004 21:50:50 -0400 (AST) Received: from linuxworld.com.au (unknown [203.34.46.50]) by svr1.postgresql.org (Postfix) with ESMTP id 65211D1EBC9 for ; Thu, 1 Apr 2004 21:50:45 -0400 (AST) Received: from localhost (swm@localhost) by linuxworld.com.au (8.11.6/8.11.4) with ESMTP id i321oaf31436; Fri, 2 Apr 2004 11:50:36 +1000 Date: Fri, 2 Apr 2004 11:50:36 +1000 (EST) From: Gavin Sherry To: "J. Andrew Rogers" Cc: pgsql-hackers@postgresql.org Subject: Re: PITR for replication? In-Reply-To: <1080867508.29882.8.camel@localhost.localdomain> Message-ID: References: <5674.1080750914@sss.pgh.pa.us> <406B6EDB.5040406@familyhealth.com.au> <1080867508.29882.8.camel@localhost.localdomain> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200404/13 X-Sequence-Number: 51935 On Fri, 1 Apr 2004, J. Andrew Rogers wrote: > > 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. Logfile shipping is one replication option some commercial vendors offer. It doesn't solve all problems however. It is mostly used for hot backups in my experience. Gavin