| From: | "Ross J(dot) Reedstrom" <reedstrm(at)rice(dot)edu> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| 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:30:04 |
| Message-ID: | 20020827223004.GA20278@rice.edu |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
On Tue, Aug 27, 2002 at 06:08:40PM -0400, Tom Lane wrote:
> Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> > But we should have some default to print some of the query,
>
> Why? So far you've been told by two different people (make that three
> now) that such a behavior is useless, and no one's weighed in in its
> favor ...
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: right now I'm logging
_all_ queries on our development machine (and sometimes on our production
machine. when there's trouble) so my logs would get considerably smaller.
A settable trim length would probably be a good idea, I suppose, for
those slinging 'bytea' and toasted texts around.
Ross
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Larry Rosenman | 2002-08-27 22:31:53 | Re: Proposed GUC Variable |
| Previous Message | Marc Lavergne | 2002-08-27 22:24:07 | Re: C vs. C++ contributions |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Larry Rosenman | 2002-08-27 22:31:53 | Re: Proposed GUC Variable |
| Previous Message | Tom Lane | 2002-08-27 22:18:36 | Re: rules regression test fix |