From: | Andres Freund <andres(at)2ndquadrant(dot)com> |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Subject: | Re: velog + vereport? |
Date: | 2012-10-12 15:56:35 |
Message-ID: | 201210121756.35668.andres@2ndquadrant.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Friday, October 12, 2012 04:59:39 PM Tom Lane wrote:
> Andres Freund <andres(at)2ndquadrant(dot)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.
Yes, that sounds good enough. Are you vetoing that idea (in that case I won't
pursue it) or just aren't excited about it?
Andres
--
Andres Freund http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Pavel Stehule | 2012-10-12 15:58:05 | Re: proposal - assign result of query to psql variable |
Previous Message | Tom Lane | 2012-10-12 15:28:01 | Re: line type |