Re: Error codes revisited - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Error codes revisited
Date
Msg-id 16438.1046837043@sss.pgh.pa.us
Whole thread Raw
In response to Error codes revisited  (greg@turnstep.com)
Responses Re: Error codes revisited  (greg@turnstep.com)
Re: Error codes revisited  ("Ross J. Reedstrom" <reedstrm@rice.edu>)
List pgsql-hackers
greg@turnstep.com writes:
> What about a variable that allowed the codes to be switched on so a 
> number is returned instead of a string? This would be off by default 
> so as not to break existing applications. Similarly, we can return 
> other information (FILE, LINE, etc.) with different variables. This 
> should all be doable without a protocol change, as long as everything 
> is returned as a string in a standard format.

The *last* thing we need is a half-baked stopgap solution that we'll
have to be backwards-compatible with forevermore.  Fix it right or
don't do it at all, is MHO.

There is still barely enough time to do the long-threatened protocol
revision for 7.4, if we suck it up and get started on that now.  I've
been avoiding the issue myself, because it seems generally boring and
thankless work, but maybe it's time to face up to it?
        regards, tom lane


pgsql-hackers by date:

Previous
From: Gavin Sherry
Date:
Subject: Re: Updateable views...
Next
From: Eric D Nielsen
Date:
Subject: Re: Updateable views...