Re: Proposed GUC Variable

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Bruce Momjian <pgman(at)candle(dot)pha(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:20:19
Message-ID: 16699.1030076419@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-patches

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.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Lamar Owen 2002-08-23 04:23:11 Re: v7.2.2 packaged ...
Previous Message J. R. Nield 2002-08-23 03:58:47 20020822_02_pitr.patch.gz

Browse pgsql-patches by date

  From Date Subject
Next Message Bruce Momjian 2002-08-23 04:24:59 Re: Proposed GUC Variable
Previous Message Bruce Momjian 2002-08-23 04:16:49 Re: Point in time recovery 20020822_01_pitr.patch