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 28660.1155762563@sss.pgh.pa.us
Whole thread Raw
In response to Re: [PATCHES] Forcing current WAL file to be archived  (Simon Riggs <simon@2ndquadrant.com>)
Responses Re: [PATCHES] Forcing current WAL file to be archived  (Simon Riggs <simon@2ndquadrant.com>)
List pgsql-hackers
Simon Riggs <simon@2ndquadrant.com> writes:
> Wise one: what should my pg_proc look like?

> DATA(insert OID = 2850 ( pg_xlogfile_name_offset    PGNSP PGUID 12 f f t f
> i 1 2249 "25" "25 25 23" "i o o" _null_ pg_xlogfile_name_offset -
> _null_ ));

Oh, as far as that goes, the array columns need to look like something
array_in will eat; and you should provide parameter names so that
"select * from" will produce useful headings.  So probably more like

DATA(insert OID = 2850 ( pg_xlogfile_name_offset    PGNSP PGUID 12 f f t f i 1 2249 "25" "{25,25,23}" "{i,o,o}"
"{wal_offset,filename,offset}"pg_xlogfile_name_offset - _null_ )); 

I think you can get away without inner quotes (ie, not "{'i','o','o'}")
as long as you aren't using anything weird like spaces in a parameter name.

            regards, tom lane

pgsql-hackers by date:

Previous
From: Simon Riggs
Date:
Subject: Re: [PATCHES] Forcing current WAL file to be archived
Next
From: "Marc G. Fournier"
Date:
Subject: Re: BugTracker (Was: Re: 8.2 features status)