Re: Duplicate key insert question - Mailing list pgsql-general

From Nigel J. Andrews
Subject Re: Duplicate key insert question
Date
Msg-id Pine.LNX.4.21.0307020929090.29474-100000@ponder.fairway2k.co.uk
Whole thread Raw
In response to Re: Duplicate key insert question  ("Shridhar Daithankar" <shridhar_daithankar@persistent.co.in>)
Responses Re: Duplicate key insert question  ("Shridhar Daithankar" <shridhar_daithankar@persistent.co.in>)
List pgsql-general
On Wed, 2 Jul 2003, Shridhar Daithankar wrote:

> On 2 Jul 2003 at 17:20, Jean-Christian Imbeault wrote:
>
> > Shridhar Daithankar wrote:
> > >
> > > No. It's just your server log.
> >
> > I was assuming that any users of this app who want it using postgres as
> > a database would want to stop these error messages from being logged.
> > (The developers know that these error messages are being logged, but
> > they don't see them as real errors)
>
> Well, with grep -v in log pipe, you are just preventing these messages from
> reaching log file. If a client does error checking. He would get the message
> anyway.


You've also got the issue of the same pgsql cluster being used for more than
one database and the potential for filtering out ERROR messages from other dbs
in the cluster that really shouldn't be filtered out.


--
Nigel J. Andrews


pgsql-general by date:

Previous
From: "Shridhar Daithankar"
Date:
Subject: Re: Duplicate key insert question
Next
From: Thomas Bamesberger
Date:
Subject: ERROR: fixrdesc: no pg_class entry for pg_class