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 0DA70D1E2AF for ; Fri, 2 Apr 2004 04:21:10 +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 36734-05 for ; Fri, 2 Apr 2004 00:21:08 -0400 (AST) Received: from news.hub.org (news.hub.org [200.46.204.72]) by svr1.postgresql.org (Postfix) with ESMTP id 73205D1DC1B for ; Fri, 2 Apr 2004 00:21:08 -0400 (AST) Received: from news.hub.org (news.hub.org [200.46.204.72]) by news.hub.org (8.12.9/8.12.9) with ESMTP id i324L7Yn090546 for ; Fri, 2 Apr 2004 04:21:08 GMT (envelope-from news@news.hub.org) Received: (from news@localhost) by news.hub.org (8.12.9/8.12.9/Submit) id i323wFbo084244 for pgsql-hackers@postgresql.org; Fri, 2 Apr 2004 03:58:15 GMT X-Newsgroups: comp.databases.postgresql.hackers Subject: Re: PITR for replication? References: <5674.1080750914@sss.pgh.pa.us> <406B6EDB.5040406@familyhealth.com.au> <1080867508.29882.8.camel@localhost.localdomain> From: Christopher Browne X-message-flag: Outlook is rather hackable, isn't it? X-Home-Page: http://www.cbbrowne.com/info/ X-Affero: http://svcs.affero.net/rm.php?r=cbbrowne Message-ID: User-Agent: Gnus/5.1006 (Gnus v5.10.6) XEmacs/21.4 (Security Through Obscurity, linux) Cancel-Lock: sha1:BMXK6RgEtWZRlGEcjyC7Kl4J5yI= MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Lines: 27 Date: Thu, 01 Apr 2004 22:04:41 -0500 X-Complaints-To: abuse@sympatico.ca Organization: Bell Sympatico To: pgsql-hackers@postgresql.org X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200404/135 X-Sequence-Number: 52057 Oops! jrogers@neopolitan.com ("J. Andrew Rogers") was seen spray-painting on a wall: > 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. What isn't clear to me at this point is whether PITR is set up to allow the database to remain "live and accessible" while updates are being loaded in. If that's NOT the case, then it is in no way a meaningful replacement for replication, vastly useful though it may be. At those times I have seen Oracle(tm) archive logs being applied to support PITR-related functionality, the DB hasn't been "up and running." I suspect that may have changed by now, which would certainly be handy for replication. -- (format nil "~S@~S" "cbbrowne" "ntlug.org") http://cbbrowne.com/info/multiplexor.html As of next Tuesday, all terminal input will be line-at-a-time. Please update your programs.