| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Gregory Stark <stark(at)enterprisedb(dot)com> |
| Cc: | "Peter Eisentraut" <peter_e(at)gmx(dot)net>, pgsql-bugs(at)postgresql(dot)org, "Thomas H(dot)" <me(at)alternize(dot)com>, "Bruce Momjian" <bruce(at)momjian(dot)us> |
| Subject: | Re: BUG #4281: some types of errors do not log statements |
| Date: | 2008-08-26 16:50:29 |
| Message-ID: | 9963.1219769429@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Gregory Stark <stark(at)enterprisedb(dot)com> writes:
> "Peter Eisentraut" <peter_e(at)gmx(dot)net> writes:
>> Well, the problem is mainly that there is no query, because the bytes arriving
>> are garbage. A human observer could make sense of it in some cases, but not
>> a computer in the general case.
> How is that different from any other syntax error?
It's not a syntax error, it's an encoding error, and we daren't try to
spit the data back out for fear of getting more encoding errors and
ending up in an infinite recursion in elog.c.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jeff Davis | 2008-08-26 17:38:24 | Re: non-deterministic error related to MIN/MAX optimization |
| Previous Message | Tom Lane | 2008-08-26 16:33:33 | Re: Behavior change in PG8.3? |