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

Re: Forcing current WAL file to be archived

From: Simon Riggs <simon(at)2ndquadrant(dot)com>
To: Hannu Krosing <hannu(at)skype(dot)net>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Bruce Momjian <bruce(at)momjian(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Forcing current WAL file to be archived
Date: 2006-07-31 22:04:42
Message-ID: 1154383483.3226.6.camel@localhost.localdomain (view raw or flat)
Thread:
Lists: 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


In response to

pgsql-hackers by date

Next:From: Alvaro HerreraDate: 2006-07-31 22:14:17
Subject: trivial script for getting pgsql-committers patches
Previous:From: Joshua D. DrakeDate: 2006-07-31 21:46:45
Subject: Re: [HACKERS] 8.2 features?

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