Re: Upgrading the backend's error-message infrastructure - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Upgrading the backend's error-message infrastructure
Date
Msg-id 22063.1047662584@sss.pgh.pa.us
Whole thread Raw
In response to Re: Upgrading the backend's error-message infrastructure  (johnnnnnn <john@phaedrusdeinus.org>)
Responses Re: Upgrading the backend's error-message infrastructure  (johnnnnnn <john@phaedrusdeinus.org>)
List pgsql-hackers
johnnnnnn <john@phaedrusdeinus.org> writes:
> It would seem to make more sense to me to provide a different
> function(s) which allows the lookup Messages, Details, and Hints based
> on the SQLSTATE.

This would constrain us to have a different SQLSTATE for every error
message, which we aren't going to do.  See elsewhere in thread.  It's
also unclear how you insert parameters into error strings if you do this.

> - Less clutter and wasted space on the wire.

I am not really concerned about shaving bytes transmitted for an error
condition.  If that's a performance-critical path for your app, you need
to rewrite the app ;-)

> - Removal of localization from error/notice generation libraries. This
> should make that section of code simpler and more fault-tolerant.

And you put it where, instead?

The existing scheme for localization works fine AFAICT.  I don't have
any interest in reinventing it (nor any chance of getting this done for
7.4, if I were to try...)
        regards, tom lane


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Roadmap for FE/BE protocol redesign
Next
From: Greg Stark
Date:
Subject: Re: SQL99 ARRAY support proposal