| From: | Gregory Stark <stark(at)enterprisedb(dot)com> |
|---|---|
| To: | "Peter Eisentraut" <peter_e(at)gmx(dot)net> |
| Cc: | <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:28:17 |
| Message-ID: | 871w0bd9lq.fsf@oxford.xeocode.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
"Peter Eisentraut" <peter_e(at)gmx(dot)net> writes:
> Thomas H. wrote:
>> maybe its by design (to not insert badly encoded characters into the
>> utf8 encoded logs)? nevertheless to debug those faulty programm/codes,
>> it would help to see what query provokes the error...
>
> 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?
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Get trained by Bruce Momjian - ask me about EnterpriseDB's PostgreSQL training!
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2008-08-26 16:33:33 | Re: Behavior change in PG8.3? |
| Previous Message | Alvaro Herrera | 2008-08-26 16:27:11 | Re: Aborted VACUUM FULL -> crash + corruption (xlog non-existent) |