Skip site navigation (1) Skip section navigation (2)

Re: [HACKERS] message for constraint

From: Jaime Casanova <systemguards(at)gmail(dot)com>
To: Jaime Casanova <systemguards(at)gmail(dot)com>, Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, Peter Eisentraut <peter_e(at)gmx(dot)net>, PostgreSQL-patches <pgsql-patches(at)postgresql(dot)org>
Subject: Re: [HACKERS] message for constraint
Date: 2006-01-16 20:59:45
Message-ID: c2d9e70e0601161259m6f67f0afv15cc8baabafc72f8@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-hackerspgsql-patches
On 1/16/06, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> wrote:
> Jaime Casanova wrote:
> > On 1/16/06, Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)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 ;)

In response to

Responses

pgsql-hackers by date

Next:From: Tom LaneDate: 2006-01-16 21:02:07
Subject: Re: Anyone see a need for BTItem/HashItem?
Previous:From: David FetterDate: 2006-01-16 20:59:42
Subject: Re: Anyone see a need for BTItem/HashItem?

pgsql-patches by date

Next:From: Tom LaneDate: 2006-01-16 21:04:58
Subject: Re: [HACKERS] message for constraint
Previous:From: Alvaro HerreraDate: 2006-01-16 20:49:55
Subject: Re: [HACKERS] message for constraint

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group