Re: [HACKERS] message for constraint - Mailing list pgsql-patches

From Jaime Casanova
Subject Re: [HACKERS] message for constraint
Date
Msg-id c2d9e70e0601161259m6f67f0afv15cc8baabafc72f8@mail.gmail.com
Whole thread Raw
In response to Re: [HACKERS] message for constraint  (Bruce Momjian <pgman@candle.pha.pa.us>)
Responses Re: [HACKERS] message for constraint  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-patches
On 1/16/06, Alvaro Herrera <alvherre@alvh.no-ip.org> wrote:
> Jaime Casanova wrote:
> > On 1/16/06, Bruce Momjian <pgman@candle.pha.pa.us> wrote:
>
> > what about lower the context part of the messages for plpgsql
> > functions? that seems debug info for me... just an idea ;)
> >
> > pruebas=# select prueba();
> > ERROR:  new row for relation "foo" violates check constraint "foo_fld_check"
> > CONTEXT:  SQL statement "insert into foo values (-1)"
> > PL/pgSQL function "prueba" line 2 at SQL statement
>
> It's not debug info in the sense of the DEBUG error levels.  These are
> meant as debug info of the server itself, like, say, a transaction
> started.  The CONTEXT line is exactly that, context information.
>

ok... maybe notice? log? i suppose that the ERROR  line is error level
so the idea is lowering the context so i can put
client_min_messages='error' and see just what the user can
understand...


--
regards,
Jaime Casanova
(DBA: DataBase Aniquilator ;)

pgsql-patches by date:

Previous
From: Jaime Casanova
Date:
Subject: Re: [HACKERS] message for constraint
Next
From: Tom Lane
Date:
Subject: Re: [HACKERS] message for constraint