| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Robert Treat <xzilla(at)users(dot)sourceforge(dot)net> |
| Cc: | Gavin Sherry <swm(at)linuxworld(dot)com(dot)au>, Hackers <pgsql-hackers(at)postgresql(dot)org>, pgsql-patches(at)postgresql(dot)org |
| Subject: | Re: [HACKERS] Proposed GUC Variable |
| Date: | 2002-08-29 16:14:24 |
| Message-ID: | 8775.1030637664@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
Robert Treat <xzilla(at)users(dot)sourceforge(dot)net> writes:
> One of my users is generating a notice message --> NOTICE: Adding
> missing FROM-clause entry for table "msg202" It might be helpful to
> dump out the query on notice messages like this, and it looks like a
> simple change as far as elog.c and guc.c are concerned, but would this
> be overkill?
Hm. Maybe instead of a boolean, what we want is a message level
variable: log original query if it triggers a message >= severity X.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | D'Arcy J.M. Cain | 2002-08-29 17:17:35 | Re: Proposed GUC Variable |
| Previous Message | Thomas F. O'Connell | 2002-08-29 16:13:03 | the optimizer and exists |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tomoyuki Niijima | 2002-08-29 16:43:58 | make check hang on AIX 5L p690 4way/I have two solutions |
| Previous Message | Tom Lane | 2002-08-29 16:11:19 | Re: Visibility regression test |