Re: Proposed GUC Variable

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Ross J(dot) Reedstrom" <reedstrm(at)rice(dot)edu>
Cc: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, 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 22:34:40
Message-ID: 14477.1030487680@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-patches

"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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Rod Taylor 2002-08-27 22:39:48 Re: Proposed GUC Variable
Previous Message Tom Lane 2002-08-27 22:32:48 Re: fix for palloc() of user-supplied length

Browse pgsql-patches by date

  From Date Subject
Next Message Nigel J. Andrews 2002-08-27 22:38:20 Superuser Reserved Backend Slots - TODO item
Previous Message Tom Lane 2002-08-27 22:32:48 Re: fix for palloc() of user-supplied length