Skip site navigation (1) Skip section navigation (2)

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 12:48:42
Message-ID: 20108.1350046122@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-hackers
Andres Freund <andres(at)2ndquadrant(dot)com> writes:
> When writing code which should be able to run inside and outside a normal 
> backend environment its sometimes useful to be able add a wrapper arround 
> elog/ereport for when executing inside the backend.
> Currently that requires relatively ugly macro surgery and/or recompiling the 
> file. I suggest adding velog/vereport or elog_va/vereport_va to make such 
> wrappers easier (still not easy though).

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.

			regards, tom lane


In response to

Responses

pgsql-hackers by date

Next:From: Andres FreundDate: 2012-10-12 13:09:28
Subject: Re: velog + vereport?
Previous:From: Andres FreundDate: 2012-10-12 11:57:39
Subject: Re: Deprecating RULES

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group