Re: ToDo: enhanced diagnostic for plpgsql

From: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
To: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: ToDo: enhanced diagnostic for plpgsql
Date: 2010-11-26 20:43:50
Message-ID: 1290804089-sup-7837@alvh.no-ip.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Excerpts from Pavel Stehule's message of vie nov 26 07:37:42 -0300 2010:
> Hello
>
> there is difficult working with exception still. Isn't time to move forward?
>
> http://archives.postgresql.org/pgsql-general/2010-11/msg01129.php
>
> I am thinking, so we can little bit enhance a GET DIAGNOSTICS statement
>
> condition item names are defined in SQL 92 - mainly: TABLE_NAME,
> COLUM_NAME and MESSAGE_TEXT.

This is probably connected to my proposal here:
http://archives.postgresql.org/message-id/20090804171210.GL6494@alvh.no-ip.org

--
Álvaro Herrera <alvherre(at)commandprompt(dot)com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Pavel Stehule 2010-11-26 20:46:36 Re: ToDo: enhanced diagnostic for plpgsql
Previous Message Tom Lane 2010-11-26 20:39:33 Re: Re: [BUGS] BUG #5650: Postgres service showing as stopped when in fact it is running