Re: [Re] [Re] Re: PANIC: could not write to log file

Поиск
Список
Период
Сортировка
От Tom Lane
Тема Re: [Re] [Re] Re: PANIC: could not write to log file
Дата
Msg-id 20330.1353687888@sss.pgh.pa.us
обсуждение исходный текст
Ответ на [Re] [Re] Re: PANIC: could not write to log file  ("Cyril VELTER" <cyril.velter@metadys.com>)
Ответы Re: PANIC: could not write to log file  ("Cyril VELTER" <cyril.velter@metadys.com>)
Список pgsql-hackers
"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

> for memory the first ones are 

> PANIC:  could not write to log file 117, segment 117 at offset 5660672, length 4096000: Invalid argument
> STATEMENT:  COMMIT
> PANIC:  could not write to log file 118, segment 74 at offset 12189696, length 475136: 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.)
        regards, tom lane



В списке pgsql-hackers по дате отправления:

Предыдущее
От: Tom Lane
Дата:
Сообщение: Re: [v9.3] Extra Daemons (Re: elegant and effective way for running jobs inside a database)
Следующее
От: Fujii Masao
Дата:
Сообщение: Re: Proposal for Allow postgresql.conf values to be changed via SQL