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 A70EED1EB6C for ; Fri, 2 Apr 2004 18:56:47 +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 24354-06 for ; Fri, 2 Apr 2004 14:56:52 -0400 (AST) Received: from cmailm1.svr.pol.co.uk (cmailm1.svr.pol.co.uk [195.92.193.18]) by svr1.postgresql.org (Postfix) with ESMTP id B5CFCD1EB3C for ; Fri, 2 Apr 2004 14:56:44 -0400 (AST) Received: from modem-1869.orangutan.dialup.pol.co.uk ([217.135.231.77] helo=stromboli) by cmailm1.svr.pol.co.uk with esmtp (Exim 4.14) id 1B9TqT-0004B8-BK; Fri, 02 Apr 2004 19:56:49 +0100 From: "Simon Riggs" To: "Greg Stark" , , "J. Andrew Rogers" Subject: Re: PITR for replication? Date: Fri, 2 Apr 2004 19:57:41 +0100 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) In-Reply-To: <87isgjov70.fsf@stark.xeocode.com> X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 Importance: Normal X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200404/39 X-Sequence-Number: 51961 > Greg Stark > "J. Andrew Rogers" writes: > > > 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. You're right...it is the basis of a log shipping replication facility. I'm keen no to get too far ahead of ourselves. Let's eat the mammoth one bite at a time....or one patch at a time. > Well "replication" is one of those things that means > different things to > different people. IMHO, this is one of the simpler, more > reliable, mechanisms > and would be nice to have. And you're right that it shouldn't > require much > more work, in fact it's probably easier than a lot of other > cases that PITR > requires. I agree. PITR is intended initially as a recovery mechanism. Replication has other purposes as well, such as locating data close to where it is required (in master-multi-slave replication scenarios), which is certainly not an objective or even a likely end point of the PITR work. The PostgreSQL community is lucky enough to have some very competent people working on those other approaches and I would recommend everybody checks out that work. > For a long time Oracle has supported this mechanism for > running warm standby > databases. Basically you maintain a second database and every > time an archived > log is finished you ship it over and immediately "restore" it > on the standby > machine. Whenever you have a failure you can quickly fail > over to the standby > database which is all ready to go and up-to-date within > minutes of your > failure. This facility is one of the intended features, if all goes well. But it is an advanced feature, not the bread and butter. > Since 8i Oracle has also supported a more advanced version > where you can open > the standby database in read-only mode. This mode requires more thought, but is certainly possible, in time. Best Regards Simon Riggs