Re: Proposed GUC Variable - Mailing list pgsql-hackers

From Christopher Kings-Lynne
Subject Re: Proposed GUC Variable
Date
Msg-id GNELIHDDFBOCMGBFGEFOAENNCDAA.chriskl@familyhealth.com.au
Whole thread Raw
In response to Re: Proposed GUC Variable  (Markus Bertheau <twanger@bluetwanger.de>)
Responses Re: Proposed GUC Variable
List pgsql-hackers
So long as the change is only evident in the log, I agree.

Chris

> -----Original Message-----
> From: pgsql-hackers-owner@postgresql.org
> [mailto:pgsql-hackers-owner@postgresql.org]On Behalf Of Markus Bertheau
> Sent: Friday, 23 August 2002 3:55 PM
> To: Bruce Momjian
> Cc: Christopher Kings-Lynne; Hackers
> Subject: Re: [HACKERS] Proposed GUC Variable
> 
> 
> 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. And killing configuration options that are
> unneeded is always a Good Thing.
> 
> -- 
> Markus Bertheau.
> Berlin, Berlin.
> Germany.
> 
> 
> ---------------------------(end of broadcast)---------------------------
> TIP 6: Have you searched our list archives?
> 
> http://archives.postgresql.org
> 



pgsql-hackers by date:

Previous
From: Tatsuo Ishii
Date:
Subject: Re: pgstattuple change using SRF
Next
From: Justin Clift
Date:
Subject: Re: Excellent DBMS Resource Site