Re: Cleaning up missing ERRCODE assignments

From: Peter Geoghegan <pg(at)heroku(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Cleaning up missing ERRCODE assignments
Date: 2015-08-01 20:24:46
Message-ID: CAM3SWZTz6+MPLLTp99U7aX2GK7s4ypg6EAeDvFBaub6Bg0YNxw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sat, Aug 1, 2015 at 8:39 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> I propose to back-patch this into 9.5, but not further; it's not an
> important enough issue to justify changing SQLSTATE behavior in stable
> branches.

+1. As I've said in the past, I think that making it possible to
determine mechanically that a "can't happen" error has in fact
occurred is of huge value to the project.

--
Peter Geoghegan

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Noah Misch 2015-08-01 20:44:18 Re: TAP tests are badly named
Previous Message Piotr Stefaniak 2015-08-01 19:28:12 Null pointer passed as source to memcpy() in numeric.c:make_result() and numeric:set_var_from_var()