Re: Viewing new 9.3 error fields - Mailing list pgsql-hackers

From Dickson S. Guedes
Subject Re: Viewing new 9.3 error fields
Date
Msg-id 1365704911.4410.28.camel@dba01
Whole thread Raw
In response to Viewing new 9.3 error fields  (Bruce Momjian <bruce@momjian.us>)
List pgsql-hackers
Em Qui, 2013-04-11 às 14:08 -0400, Bruce Momjian escreveu:
> This blog entry displays the new 9.3 error fields, schema/table/constraint:
>
>
http://www.depesz.com/2013/03/07/waiting-for-9-3-provide-database-object-names-as-separate-fields-in-error-messages/
>
>     $ INSERT INTO t (i) VALUES (1);
>     psql:z.sql:16: ERROR:  23505: duplicate key value violates unique constraint "t2_pkey"
>     DETAIL:  Key (i)=(1) already exists.
>     CONTEXT:  SQL statement "INSERT INTO t2 (i) VALUES (NEW.i)"
>     PL/pgSQL function copy_value() line 4 at SQL statement
> -->    SCHEMA NAME:  public
> -->    TABLE NAME:  t2
> -->    CONSTRAINT NAME:  t2_pkey
>     LOCATION:  _bt_check_unique, nbtinsert.c:398
>
> However, I am unable to see this in psql:
>
>     CREATE TABLE ledger (id SERIAL, balance NUMERIC(10,2) unique);
>
>     SET log_error_verbosity = 'verbose';
>
>     INSERT INTO ledger VALUES (DEFAULT, 1);
>
>     INSERT INTO ledger VALUES (DEFAULT, 1);
>     ERROR:  duplicate key value violates unique constraint "ledger_balance_key"
>     DETAIL:  Key (balance)=(1.00) already exists.
> -->
>
> What am I missing?


Isn't it on log output?

--
Dickson S. Guedes
mail/xmpp: guedes@guedesoft.net - skype: guediz
http://guedesoft.net - http://www.postgresql.org.br
http://www.rnp.br/keyserver/pks/lookup?search=0x8F3E3C06D428D10A

pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Viewing new 9.3 error fields
Next
From: Alvaro Herrera
Date:
Subject: Re: Viewing new 9.3 error fields