Re: Possible Corrputed shared memory
От | Tom Lane |
---|---|
Тема | Re: Possible Corrputed shared memory |
Дата | |
Msg-id | 16010.1438441421@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | Re: Possible Corrputed shared memory (James Sebastian <james.sebastian@gmail.com>) |
Ответы |
Re: Possible Corrputed shared memory
|
Список | pgsql-novice |
James Sebastian <james.sebastian@gmail.com> writes: > On 1 August 2015 at 20:10, Tom Lane <tgl@sss.pgh.pa.us> wrote: >> [ scratches head... ] It should certainly not have taken very long to >> replay 10 WAL segments worth of data. I surmise that the problems >> you were having before the shutdown were worse than you thought, ie >> checkpoints were failing to complete, probably due to a persistent >> I/O error, so that there was a whole lot more than normal to replay >> after the last successful checkpoint. Is there any evidence of such >> distress in the postmaster log? > We had very slow application performance and many hanging threads as per > pgadmin -> server status > Also logs had the following which also indicating probably high I/O (as per > google search results) > 2015-07-30 10:10:21 IST WARNING: pgstat wait timeout > 2015-07-30 10:12:21 IST WARNING: pgstat wait timeout Well, those might mean problems with the stats collector subprocess, but that's pretty noncritical; it would certainly not have prevented checkpoints from completing. No other unexplained log entries? regards, tom lane
В списке pgsql-novice по дате отправления: