Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
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: Mon, 31 Jul 2006 23:04:42 +0100
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
- References:
- Re: Forcing current WAL file to be archived
- From: Bruce Momjian
- Re: Forcing current WAL file to be archived
- From: Simon Riggs
- Re: Forcing current WAL file to be archived
- From: Tom Lane
- Re: Forcing current WAL file to be archived
- From: Simon Riggs
- Re: Forcing current WAL file to be archived
- From: Hannu Krosing
- Re: Forcing current WAL file to be archived
- Prev by Date: Re: DTrace enabled build fails
- Next by Date: trivial script for getting pgsql-committers patches
- Previous by thread: Re: Forcing current WAL file to be archived
- Next by thread: Re: Forcing current WAL file to be archived
- Indexes: