Re: Forcing current WAL file to be archived - Mailing list pgsql-hackers

From Simon Riggs
Subject Re: Forcing current WAL file to be archived
Date
Msg-id 1154383483.3226.6.camel@localhost.localdomain
Whole thread Raw
In response to Re: Forcing current WAL file to be archived  (Hannu Krosing <hannu@skype.net>)
List pgsql-hackers
On Tue, 2006-08-01 at 00:40 +0300, Hannu Krosing wrote:
> Ühel kenal päeval, T, 2006-07-25 kell 17:05, kirjutas Simon Riggs:
> > On Tue, 2006-07-25 at 11:53 -0400, Tom Lane wrote:
> > > 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.
> >
> > Agreed.
>
> Simon, did you (or anybody else) manage to complete the patch for adding
> the (wal_filename, offset) returning function ?

Just wrapping now.

I tried to add archive_timeout also, though am still fiddling with that,
so I've taken that back out for now.

--  Simon Riggs EnterpriseDB          http://www.enterprisedb.com



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: DTrace enabled build fails
Next
From: Alvaro Herrera
Date:
Subject: trivial script for getting pgsql-committers patches