From: | ngpg(at)grymmjack(dot)com |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Proposed GUC Variable |
Date: | 2002-08-28 00:37:15 |
Message-ID: | Xns9277D1C7D74FF9wn7t0983uom3iu23n@64.49.215.80 |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-patches |
tgl(at)sss(dot)pgh(dot)pa(dot)us (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 ...
Just out of curiosity... how much harder would it be to have the GUC
variable represent the truncation length? so setting it to zero would be
equivalent to turning the feature off... I personally would have no use
for this feature, but I am just curious.
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2002-08-28 01:07:04 | Re: Open 7.3 items |
Previous Message | Tom Lane | 2002-08-27 23:34:18 | Re: fix for palloc() of user-supplied length |
From | Date | Subject | |
---|---|---|---|
Next Message | Gavin Sherry | 2002-08-28 01:59:40 | Re: Proposed GUC Variable |
Previous Message | Tom Lane | 2002-08-27 23:34:18 | Re: fix for palloc() of user-supplied length |