| 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: | 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-23 04:24:59 |
| Message-ID: | 200208230424.g7N4OxA28610@candle.pha.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
Tom Lane wrote:
> Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> > Someone asked for that recently, and the email is in my mailbox for
> > consideration. I think it is a great idea, and we have
> > debug_query_string that holds the current query.
>
> 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.
--
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Christopher Kings-Lynne | 2002-08-23 04:25:19 | Another tsearch bug... |
| Previous Message | Lamar Owen | 2002-08-23 04:23:11 | Re: v7.2.2 packaged ... |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Christopher Kings-Lynne | 2002-08-23 04:26:52 | Re: Proposed GUC Variable |
| Previous Message | Tom Lane | 2002-08-23 04:20:19 | Re: Proposed GUC Variable |