Re: query log corrupted-looking entries
От | George Pavlov |
---|---|
Тема | Re: query log corrupted-looking entries |
Дата | |
Msg-id | 8C5B026B51B6854CBE88121DBF097A86CDDA32@ehost010-33.exch010.intermedia.net обсуждение исходный текст |
Ответ на | Re: query log corrupted-looking entries (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: query log corrupted-looking entries
|
Список | pgsql-general |
From: Tom Lane [mailto:tgl@sss.pgh.pa.us] > "George Pavlov" <gpavlov@mynewplace.com> writes: > > ... Also redirect_stderr = on. > > Hm. Well, that's the bit that ought to get you into the PIPE_BUF > exception. There's been some speculation that a change like the > attached would help. I've found that it makes no difference with > my libc, but maybe yours is different --- want to try it? I will. I may need some time though, since I first need to find a way to reproduce the problem reliably on my test environments and right now I cannot seem to. I have seen the problem mostly under production loads (also under certain kinds of stress-testing, but I forget exactly which kind...) In the meantime I went and looked at the logs in more detail and the corrupted entries seem much more prevalent than what I originally thought. Apart from the ones pgfouine complains about there are many more such lines. For example out of a (average-load) day's log file with 17+ million lines pgfouine complains about 8 lines, but there are in fact 1400+ lines with these kinds of entries. George
В списке pgsql-general по дате отправления: