Andres Freund <and...@2ndquadrant.com> writes: > On Friday, October 12, 2012 02:48:42 PM Tom Lane wrote: >> Um ... and that accomplishes what? You wouldn't have velog/vereport >> outside the backend either. If you were going to clone those in some >> form in the external environment, you might as well clone the existing >> elog infrastructure functions.
> The advantage is that if you something velog-ish you can have a function > which > accepts vararg arguments and forwards them. > E.g. > xlogreader->error(ERROR, "...", argument, argument); Meh. I can't get excited about that, but in any case, that looks like it would only justify a varargs version of errmsg(), not the entire ereport infrastructure. regards, tom lane -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers