Re: proposal: enable new error fields in plpgsql (9.4)
Noah Misch <noah@leadboat.com>
From: Noah Misch <noah@leadboat.com>
To: Pavel Stehule <pavel.stehule@gmail.com>
Cc: Rushabh Lathia <rushabh.lathia@gmail.com>,
Peter Eisentraut <peter_e@gmx.net>, Marko Tiikkaja <pgmail@joh.to>,
PostgreSQL Hackers <pgsql-hackers@postgresql.org>
Date: 2013-06-28T13:20:26Z
Lists: pgsql-hackers
On Fri, Jun 28, 2013 at 07:49:46AM +0200, Pavel Stehule wrote: > 2013/6/28 Noah Misch <noah@leadboat.com>: > > On Tue, Jun 25, 2013 at 03:56:27PM +0200, Pavel Stehule wrote: > >> cleaned patch is in attachment > > > > Of the five options you're adding to GET STACKED DIAGNOSTICS, four of them > > appear in the SQL standard. DATATYPE_NAME does not; I think we should call it > > PG_DATATYPE_NAME in line with our other extensions in this area. > > > > yes, but It should be fixed in 9.3 enhanced fields too - it should be > consistent with PostgreSQL fields What else, specifically, should be renamed? (Alternately, would you prepare a new version of the patch incorporating the proper name changes?) Thanks, nm -- Noah Misch EnterpriseDB http://www.enterprisedb.com