From: Bruce Momjian <pgman@candle.pha.pa.us>
Message-Id: <200605300129.k4U1TSR22258@candle.pha.pa.us>
Subject: Re: Proposed doc-patch: Identifying the Current WAL file
In-Reply-To: <1148390067.2646.806.camel@localhost.localdomain>
To: Simon Riggs <simon@2ndquadrant.com>
Date: Mon, 29 May 2006 21:29:28 -0400 (EDT)
CC: pgsql-patches@postgresql.org, Tom Lane <tgl@sss.pgh.pa.us>,
	Richard Huxton <dev@archonet.com>, pgsql-docs@postgresql.org
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset=US-ASCII


Your patch has been added to the PostgreSQL unapplied patches list at:

	http://momjian.postgresql.org/cgi-bin/pgpatches

It will be applied as soon as one of the PostgreSQL committers reviews
and approves it.

---------------------------------------------------------------------------


Simon Riggs wrote:
> On Sun, 2006-04-16 at 15:22 +0100, Simon Riggs wrote:
> > On Sat, 2006-04-15 at 16:20 -0400, Bruce Momjian wrote:
> > > 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.
> 
> > For 8.0. and 8.1 users, I'd suggest we release an external function as a
> > contrib module, so that we don't compromise reliability and not force an
> > initdb for them. With docs, of course.
> > 
> > I suggest we have two functions:
> > 1. pg_xlog_file_from_offset(text)
> > This allows the output of pg_stop_backup to be formatted into a
> > filename, so it would be used like this:
> > 	select pg_xlog_file_from_offset(pg_stop_backup());
> 
> Patch to implement this as a contrib module enclosed.
> 
> No main manual doc patch yet, awaiting review.
> 
> -- 
>   Simon Riggs             
>   EnterpriseDB   http://www.enterprisedb.com

[ Attachment, skipping... ]

> 
> ---------------------------(end of broadcast)---------------------------
> TIP 3: Have you checked our extensive FAQ?
> 
>                http://www.postgresql.org/docs/faq

-- 
  Bruce Momjian   http://candle.pha.pa.us
  EnterpriseDB    http://www.enterprisedb.com

  + If your life is a hard drive, Christ can be your backup. +