Skip site navigation (1) Skip section navigation (2)

Re: Proposed doc-patch: Identifying the Current WAL file

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Simon Riggs <simon(at)2ndquadrant(dot)com>
Cc: pgsql-patches(at)postgresql(dot)org, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Richard Huxton <dev(at)archonet(dot)com>, pgsql-docs(at)postgresql(dot)org
Subject: Re: Proposed doc-patch: Identifying the Current WAL file
Date: 2006-05-30 14:08:18
Message-ID: 200605301408.k4UE8Ib17555@candle.pha.pa.us (view raw or flat)
Thread:
Lists: pgsql-docspgsql-patches
Simon, I understand this is only for the 8.1.X and 8.0.X branches.  I am
hesitant to put something in back branches when the main branch does not
have this functionality.  I will hold the patch until we are sure where
the head branch is going.

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

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. +

In response to

pgsql-docs by date

Next:From: Bruce MomjianDate: 2006-06-07 12:58:02
Subject: Re: vacuum and routine maintenance docs
Previous:From: Bruce MomjianDate: 2006-05-30 11:55:01
Subject: Re: small doc patch for regexp_replace

pgsql-patches by date

Next:From: Bruce MomjianDate: 2006-05-30 14:09:31
Subject: Re: [PATCH] Round 2: Magic block for modules
Previous:From: Bruce MomjianDate: 2006-05-30 14:01:49
Subject: Re: [PATCH] Improve EXPLAIN ANALYZE overhead by sampling

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group