| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Jim C(dot) Nasby" <jnasby(at)pervasive(dot)com> |
| Cc: | Simon Riggs <simon(at)2ndquadrant(dot)com>, Alvaro Herrera <alvherre(at)commandprompt(dot)com>, pgsql-hackers(at)postgresql(dot)org, pgsql-patches(at)postgresql(dot)org, Bruce Momjian <bruce(at)momjian(dot)us>, Hannu Krosing <hannu(at)skype(dot)net> |
| Subject: | Re: [HACKERS] Forcing current WAL file to be archived |
| Date: | 2006-08-15 19:29:05 |
| Message-ID: | 19358.1155670145@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
"Jim C. Nasby" <jnasby(at)pervasive(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2006-08-15 19:52:11 | Re: insert/update/delete returning and rules |
| Previous Message | Tom Lane | 2006-08-15 19:22:19 | Re: [PATCHES] Custom variable class segmentation fault |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | korryd@enterprisedb.com | 2006-08-15 20:12:33 | Re: [PATCHES] PL instrumentation plugin and Rendezvous variable |
| Previous Message | Tom Lane | 2006-08-15 19:22:19 | Re: [PATCHES] Custom variable class segmentation fault |