X-Original-To: pgsql-docs-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by postgresql.org (Postfix) with ESMTP id 6030D11F6C58 for ; Sat, 15 Apr 2006 17:20:51 -0300 (ADT) X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Score: 0.113 X-Spam-Level: X-Spam-Status: No, score=0.113 required=5 tests=[AWL=0.113] Received: from postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id h3COMYHMaJC3 for ; Sat, 15 Apr 2006 17:20:46 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey- Received: from candle.pha.pa.us (candle.pha.pa.us [70.90.9.53]) by postgresql.org (Postfix) with ESMTP id 346E011F6D2C for ; Sat, 15 Apr 2006 17:20:48 -0300 (ADT) Received: (from pgman@localhost) by candle.pha.pa.us (8.11.6/8.11.6) id k3FKKjM20502; Sat, 15 Apr 2006 16:20:45 -0400 (EDT) From: Bruce Momjian Message-Id: <200604152020.k3FKKjM20502@candle.pha.pa.us> Subject: Re: Proposed doc-patch: Identifying the Current WAL file In-Reply-To: <1145127316.3273.12.camel@localhost.localdomain> To: Simon Riggs Date: Sat, 15 Apr 2006 16:20:45 -0400 (EDT) CC: Tom Lane , Richard Huxton , pgsql-docs@postgresql.org X-Mailer: ELM [version 2.4ME+ PL121 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII X-Archive-Number: 200604/22 X-Sequence-Number: 3521 Simon Riggs wrote: > On Sat, 2006-04-15 at 12:24 -0400, Bruce Momjian wrote: > > And if we can't provide one, should we supply an SQL function > > to return the current WAL name? > > I'll do this. Just give me a few days to get my feet under the new desk. > I know its well past time I sorted this and a few other things out. If we get some mechanism to write those partial WAL files, we might not need the ability to identify the current WAL file, and because a new function is going to require an initdb, I am thinking we can't get this done until 8.2 anyway, so Simon, please come up with a plan to finish the missing PITR pieces. I am getting tired of trying to explain workarounds to PITR users, especially when the workarounds are not easy. We added PITR in 8.0, and we have made little improvement to it since then, and its limitations are getting tiring. -- Bruce Momjian http://candle.pha.pa.us EnterpriseDB http://www.enterprisedb.com + If your life is a hard drive, Christ can be your backup. +