Re: Proposed GUC Variable - Mailing list pgsql-hackers

From Neil Conway
Subject Re: Proposed GUC Variable
Date
Msg-id 87fzx58nmr.fsf@mailbox.samurai.com
Whole thread Raw
In response to Re: Proposed GUC Variable  (Markus Bertheau <twanger@bluetwanger.de>)
List pgsql-hackers
Markus Bertheau <twanger@bluetwanger.de> writes:
> On Fri, 2002-08-23 at 04:46, Bruce Momjian wrote:
> > 
> >     * Add GUC parameter to print queries that generate errors
> 
> Maybe don't make that an option, but rather do it always. I don't
> see where that would hurt.

It would hurt in situations in which an error is expected to occur
(e.g. INSERT into table, if constraint violation then do XYZ). It
would also make the logs a lot larger + less readable if long (say,
100 line) queries are being executed.

I don't think either situation is particularly common, but I do think
it's worth keeping a GUC variable for it. The GUC var should probably
default to being enabled though.

Cheers,

Neil

-- 
Neil Conway <neilc@samurai.com> || PGP Key ID: DB3C29FC



pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: [GENERAL] integer[] Update Questions
Next
From: Lamar Owen
Date:
Subject: Re: v7.2.2 Released ... but not announced ...