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

From Tom Lane
Subject Re: [PATCHES] Forcing current WAL file to be archived
Date
Msg-id 19358.1155670145@sss.pgh.pa.us
Whole thread Raw
In response to Re: [PATCHES] Forcing current WAL file to be archived  ("Jim C. Nasby" <jnasby@pervasive.com>)
Responses Re: [PATCHES] Forcing current WAL file to be archived  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
"Jim C. Nasby" <jnasby@pervasive.com> writes:
> True, but making people parse the output of a function to seperate the
> two fields seems pretty silly. Is there some reason why
> pg_xlogfile_name_offset shouldn't be a SRF, or use two out parameters?

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.)
And the other alternatives like a predefined complex type seem even
more painful.  If you can think of a way to do this that has pain
not out of proportion to the gain, then I'm all for it ...

            regards, tom lane

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: [PATCHES] Custom variable class segmentation fault
Next
From: Tom Lane
Date:
Subject: Re: insert/update/delete returning and rules