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

From Shridhar Daithankar
Subject Re: Duplicate key insert question
Date
Msg-id 3F02E674.27715.4EBDD15@localhost
Whole thread Raw
In response to Re: Duplicate key insert question  ("Nigel J. Andrews" <nandrews@investsystems.co.uk>)
List pgsql-general
On 2 Jul 2003 at 9:30, Nigel J. Andrews wrote:

> > 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.


Well, if you put the entire error message in grep string, that should not
affect much as it contains index name. Of course, unless you have same index in
two different databases. Tough luck then..

Bye
 Shridhar

--
Fun experiments:    Get a can of shaving cream, throw it in a freezer for about a
week.    Then take it out, peel the metal off and put it where you want...
bedroom, car, etc.  As it thaws, it expands an unbelievable amount.


pgsql-general by date:

Previous
From: Thomas Bamesberger
Date:
Subject: ERROR: fixrdesc: no pg_class entry for pg_class
Next
From: Stephan Szabo
Date:
Subject: Re: URGENT: How to change ON CASCADE RESTRICT to DELETE?