| From: | "George Pavlov" <gpavlov(at)mynewplace(dot)com> |
|---|---|
| To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: query log corrupted-looking entries |
| Date: | 2006-10-11 23:15:53 |
| Message-ID: | 8C5B026B51B6854CBE88121DBF097A864DF42A@ehost010-33.exch010.intermedia.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers |
> What PG version is this, on what operating system? Do you have
> redirect_stderr enabled?
Sorry, I should have included that:
PostgreSQL 8.1.3 on x86_64-redhat-linux-gnu, compiled by GCC gcc (GCC)
3.4.4 20050721 (Red Hat 3.4.4-2)
And yes, redirect_stderr = on. I have no definitive way of reproducing
it, just a vague one: "hit the server with lots of queries". Some
solution would be very welcome because once I have a "bad" log file like
that it is very hard (at least for me) to clean it up by hand.
George
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joshua D. Drake | 2006-10-11 23:27:29 | Re: more anti-postgresql FUD |
| Previous Message | Ron Johnson | 2006-10-11 23:13:24 | Re: question on renaming a foreign key |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Mark Woodward | 2006-10-11 23:18:11 | Re: Hints WAS: Index Tuning Features |
| Previous Message | Kai-Uwe Sattler | 2006-10-11 22:32:22 | Re: Index Tuning Features [2] |