Re: PANIC: could not write to log file
От | Cyril VELTER |
---|---|
Тема | Re: PANIC: could not write to log file |
Дата | |
Msg-id | 2674.3532669@A0B26CC9.AE6B.4C00.9DB4.128BBA13E61B обсуждение исходный текст |
Ответ на | Re: [Re] [Re] Re: PANIC: could not write to log file (Tom Lane <tgl@sss.pgh.pa.us>) |
Список | pgsql-hackers |
On 23/11/12 17:24:48 mailto:tgl@sss.pgh.pa.us wrote : > "Cyril VELTER" <cyril.velter@metadys.com> writes: > > I follow up on my previous message. Just got two more crash today very similar to the first ones : > > > PANIC: could not write to log file 118, segment 237 at offset 2686976, length 5578752: Invalid argument > > STATEMENT: COMMIT > > PANIC: could not write to log file 118, segment 227 at offset 9764864, length 57344: Invalid argument > > STATEMENT: COMMIT > > Hm, those write lengths seem rather large. What have you got > wal_buffers set to? Does it help if you back it off to whatever you > were using in the 8.2 installation? (The default back in 8.2 days > seems to have been 64kB, if that helps.) I changed wal_buffer to 64kb friday evening. It worked flawlessly this week end (but with very litlle load). I got anotherPANIC this morning with the same kind of message, but just before there is a FATAL : FATAL: could not create signal handler thread PANIC: could not write to log file 121, segment 168 at offset 9592832,length 8192: Invalid argument Unfortunatly there is no error code in the FATAL message. Best regards, cyril
В списке pgsql-hackers по дате отправления: