| From: | "Christopher Kings-Lynne" <chriskl(at)familyhealth(dot)com(dot)au> |
|---|---|
| To: | "Bruce Momjian" <pgman(at)candle(dot)pha(dot)pa(dot)us>, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | "Hackers" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Proposed GUC Variable |
| Date: | 2002-08-23 04:26:52 |
| Message-ID: | GNELIHDDFBOCMGBFGEFOMENKCDAA.chriskl@familyhealth.com.au |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
> > debug_query_string doesn't necessarily have a lot to do with the
> > proximate cause of the error. Consider queries issued by rules,
> > triggers, plpgsql functions, etc.
>
> Maybe. I think giving the user the string that caused the error is
> probably what they want, rather than a rule or trigger that they can't
> tie back to an actual query.
Yeah, I'd agree with that.
Chris
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2002-08-23 05:01:00 | psql password prompt |
| Previous Message | Christopher Kings-Lynne | 2002-08-23 04:25:19 | Another tsearch bug... |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2002-08-23 04:27:18 | Re: another NAMEDATALEN fix |
| Previous Message | Bruce Momjian | 2002-08-23 04:24:59 | Re: Proposed GUC Variable |