Re: velog + vereport?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Andres Freund <andres(at)2ndquadrant(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: velog + vereport?
Date: 2012-10-12 16:02:44
Message-ID: 25314.1350057764@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Andres Freund <andres(at)2ndquadrant(dot)com> writes:
> On Friday, October 12, 2012 04:59:39 PM Tom Lane wrote:
>> 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?

Well, I'm not excited about adding more elog.c infrastructure in advance
of having a use-case in the core code --- how would we know if it got
broken? That's not meant as an absolute veto, but I'm not terribly
comfortable about adding code speculatively.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Sébastien Lardière 2012-10-12 16:03:40 Re: Truncate if exists
Previous Message Pavel Stehule 2012-10-12 15:58:05 Re: proposal - assign result of query to psql variable