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

From Simon Riggs
Subject Re: [PATCHES] Forcing current WAL file to be archived
Date
Msg-id 1155708347.2649.185.camel@holly
Whole thread Raw
In response to Re: [PATCHES] Forcing current WAL file to be archived  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: [PATCHES] Forcing current WAL file to be archived
List pgsql-hackers
On Tue, 2006-08-15 at 18:42 -0400, Tom Lane wrote:
> I wrote:
> > It'd definitely be nicer that way, but given the current limitations of
> > bootstrap mode I see no non-kluge way to make a built-in function have
> > OUT parameters.  (Hint: array_in doesn't work in bootstrap mode.)
>
> Actually, that turns out not to be so hard to fix as I thought.
> array_in only needs to work for the array types used in the core system
> tables, and bootstrap.c already has a hard-wired table of that info ...
> we only have to make it available to array_in.   Which I just did.

Cool; I'd noticed that this would have been the first such function.

> So let's fix pg_xlogfile_name_offset() to have two OUT parameters
> instead of returning a smushed-together string.

I'll do this, but I'm conscious that this is a cosmetic change.

I'm going on vacation very soon now, so test reports of the major
functionality would be greatly appreciated.

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


pgsql-hackers by date:

Previous
From: Josh Berkus
Date:
Subject: Re: BugTracker (Was: Re: 8.2 features status)
Next
From: "Jie Zhang"
Date:
Subject: Re: [PATCHES] WIP: bitmap indexes