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

From Simon Riggs
Subject Re: Forcing current WAL file to be archived
Date
Msg-id 1155661632.2649.152.camel@holly
Whole thread Raw
In response to Re: Forcing current WAL file to be archived  (Alvaro Herrera <alvherre@commandprompt.com>)
Responses Re: [HACKERS] Forcing current WAL file to be archived
List pgsql-patches
On Tue, 2006-08-15 at 11:10 -0400, Alvaro Herrera wrote:
> Simon Riggs wrote:
>
>
>
> > postgres=# select pg_xlogfile_name_offset(pg_switch_xlog());
> >       pg_xlogfile_name_offset
> > -----------------------------------
> >  000000010000000000000001 16777216
> > (1 row)
>
> > I've not taken up Jim Nasby's suggestion to make this an SRF with
> > multiple return rows/columns since that much complexity isn't justified
> > IMHO.
>
> Hum, but two columns here seem warranted, don't they?

Maybe. People can write any function they like though, so I'm loathe to
agonize over this too much.

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


pgsql-patches by date:

Previous
From: Tom Lane
Date:
Subject: Re: [Patch] - Fix for bug #2558, InitDB failed to run
Next
From: "Jim C. Nasby"
Date:
Subject: Re: [HACKERS] Forcing current WAL file to be archived