Re: Proposed GUC Variable

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "Ross J(dot) Reedstrom" <reedstrm(at)rice(dot)edu>, Larry Rosenman <ler(at)lerctr(dot)org>, Gavin Sherry <swm(at)linuxworld(dot)com(dot)au>, Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au>, Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Proposed GUC Variable
Date: 2002-08-27 23:17:36
Message-ID: 200208272317.g7RNHar24970@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-patches


OK, just go with a boolean and admins can decide if they want it.

---------------------------------------------------------------------------

Tom Lane wrote:
> "Ross J. Reedstrom" <reedstrm(at)rice(dot)edu> writes:
> > I agree that a 'trimmed' query is likely to be useless, but the idea of
> > printing the query on ERROR is a big win for me:
>
> Certainly. I think though that an on-or-off GUC option is sufficient.
> We don't need a length, and we definitely don't need code to strip out
> whitespace as Bruce was suggesting ...
>
> regards, tom lane
>

--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2002-08-27 23:18:25 Re: LIMIT 1 FOR UPDATE or FOR UPDATE LIMIT 1?
Previous Message Neil Conway 2002-08-27 23:00:25 Re: fix for palloc() of user-supplied length

Browse pgsql-patches by date

  From Date Subject
Next Message Karl DeBisschop 2002-08-27 23:18:38 Re: Proposed GUC Variable
Previous Message Neil Conway 2002-08-27 23:00:25 Re: fix for palloc() of user-supplied length