| From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
|---|---|
| To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
| Cc: | PostgreSQL-patches <pgsql-patches(at)postgresql(dot)org> |
| Subject: | Re: [HACKERS] logging statement levels |
| Date: | 2004-04-06 15:00:28 |
| Message-ID: | 200404061500.i36F0SU11644@candle.pha.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
Andrew Dunstan wrote:
>
> Unless I'm missing something, this patch has the effect that with values
> of "ddl" or "mod" for log_statement, a statement with a parse error
> will not be logged, which was what I hoped to avoid.
Right. The query type can't be determined during a syntax error because
the parser couldn't identify the supplied command. I think that is
fine.
What it does allow is to for 'all' to display the command before the
syntax error.
--
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 | Tom Lane | 2004-04-06 15:08:49 | Re: Function to kill backend |
| Previous Message | Magnus Hagander | 2004-04-06 15:00:16 | Re: Function to kill backend |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2004-04-06 15:21:54 | Re: [HACKERS] logging statement levels |
| Previous Message | Tom Lane | 2004-04-06 13:56:13 | Re: hint infrastructure setup (v3) |