Re: Forcing current WAL file to be archived

Simon Riggs wrote:
> On Tue, 2006-07-25 at 11:57 -0400, Bruce Momjian wrote:
> > Tom Lane wrote:
> > > Simon Riggs <simon@2ndquadrant.com> writes:
> > > > I was planning to add a new GUC
> > > >     archive_timeout (integer) = max # secs between log file switches
> > > 
> > > That's fine, but feature freeze is in a week and we don't even have the
> > > basic function for manually doing a log file switch.  Let's get that
> > > done first and then think about automatic switches.
> > > 
> > > Also, forcing another 16M of WAL out every few seconds is a pretty crude
> > > and inefficient way of making sure your hot standby server is up to
> > > date.  As Hannu noted, an archiving script can do better than that if it
> > > can access the current WAL file name and offset.  So we really want to
> > > get the function to return that info done as well.
> > 
> > Agreed.  One concern I have is that we have waited for Simon to complete
> > this for 1.5 years, and now with a week left he is still working on it
> > (or starting on it).  
> 
> Since we cannot agree even now on what should be done, you'll forgive me
> for not having completed it sooner, especially since you know more about
> my schedule now than others.

It is not a blame issue.  The issue is I would like this completed for
8.2 and I want to minimize the possibility it will not be done.

I think we do know what we want done.  It is just that we are not
certain of the user interface.

--  Bruce Momjian   bruce@momjian.us EnterpriseDB    http://www.enterprisedb.com
 + If your life is a hard drive, Christ can be your backup. +