Re: enhanced error fields - Mailing list pgsql-hackers

From Tom Lane
Subject Re: enhanced error fields
Date
Msg-id 8098.1341959947@sss.pgh.pa.us
Whole thread Raw
In response to Re: enhanced error fields  (Alvaro Herrera <alvherre@commandprompt.com>)
Responses Re: enhanced error fields  (Pavel Stehule <pavel.stehule@gmail.com>)
List pgsql-hackers
Alvaro Herrera <alvherre@commandprompt.com> writes:
> FWIW about the new include:  I feel a strong dislike about the forward
> declaration you suggest.  Defining Relation in elog.h seems completely
> out of place.

Agreed.  Maybe a reasonable solution is to allow some ereport helper
functions (or, really, wrappers for the helper functions) to be declared
someplace else than elog.h.  They'd likely need to be implemented
someplace else than elog.c, too, so this doesn't seem unreasonable.

The generic helper function approach doesn't seem too unreasonable for
this: elog.h/.c would provide something like
err_generic_string(int fieldid, const char *str)

and then someplace else could provide functions built on this that
insert table/schema/column/constraint/etc names into suitable fields.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Alexander Korotkov
Date:
Subject: Re: Testing of various opclasses for ranges
Next
From: Daniel Farina
Date:
Subject: Re: Synchronous Standalone Master Redoux