Re: pgsql: Add support for forcing a switch to a new

From: Simon Riggs <simon(at)2ndquadrant(dot)com>
To: Tom Lane <tgl(at)postgresql(dot)org>
Cc: pgsql-committers(at)postgresql(dot)org
Subject: Re: pgsql: Add support for forcing a switch to a new
Date: 2006-08-07 15:34:37
Message-ID: 1154964877.2570.83.camel@localhost.localdomain
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

On Sun, 2006-08-06 at 00:53 -0300, Tom Lane wrote:
> Log Message:
> -----------
> Add support for forcing a switch to a new xlog file; cause such a switch
> to happen automatically during pg_stop_backup(). Add some functions for
> interrogating the current xlog insertion point and for easily extracting
> WAL filenames from the hex WAL locations displayed by pg_stop_backup
> and friends. Simon Riggs with some editorialization by Tom Lane.

Looks like some pretty good streamlining to me... you're too modest.

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

In response to

Browse pgsql-committers by date

  From Date Subject
Next Message Tom Lane 2006-08-07 16:57:57 pgsql: Make recovery from WAL be restartable, by executing a
Previous Message User Dpavlin 2006-08-07 14:32:50 pgestraier - pgestraier: subversion revision 64 commited to CVS