Re: Proposed GUC Variable

From: "Christopher Kings-Lynne" <chriskl(at)familyhealth(dot)com(dot)au>
To: "Markus Bertheau" <twanger(at)bluetwanger(dot)de>, "Bruce Momjian" <pgman(at)candle(dot)pha(dot)pa(dot)us>
Cc: "Hackers" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Proposed GUC Variable
Date: 2002-08-23 09:13:08
Message-ID: GNELIHDDFBOCMGBFGEFOAENNCDAA.chriskl@familyhealth.com.au
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-patches

So long as the change is only evident in the log, I agree.

Chris

> -----Original Message-----
> From: pgsql-hackers-owner(at)postgresql(dot)org
> [mailto:pgsql-hackers-owner(at)postgresql(dot)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
>

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Vince Vielhaber 2002-08-23 09:45:52 Re: My head is spinning
Previous Message Tatsuo Ishii 2002-08-23 08:20:59 Re: pgstattuple change using SRF

Browse pgsql-patches by date

  From Date Subject
Next Message Bruce Momjian 2002-08-23 15:24:19 Re: Proposed GUC Variable
Previous Message Markus Bertheau 2002-08-23 07:54:57 Re: Proposed GUC Variable