Re: [External] standby replication server throws invalid memory allocrequest size , does not start up

Поиск
Список
Период
Сортировка
От Rui DeSousa
Тема Re: [External] standby replication server throws invalid memory allocrequest size , does not start up
Дата
Msg-id 269E778E-21FC-4EA4-846D-52C896E38CDB@crazybean.net
обсуждение исходный текст
Ответ на Re: [External] Re: standby replication server throws invalid memoryalloc request size , does not start up  (Andres Freund <andres@anarazel.de>)
Список pgsql-admin
Дерево обсуждения


On Jun 28, 2018, at 12:36 PM, Andres Freund <andres@anarazel.de> wrote:

How are you making the inference that that's the problem? It could very
well be a postgres bug or somebody having used pg_resetxlog or.. ?


Is this to me? Most RAID controllers I’ve seen have been setup with write back for performance and also they also seem to have faulty batteries.

I’m merely stating that the I/O path needs to be validated to insure fsync() actually works — otherwise a power failure will introduce data corruption without doubt.  

We know the event was occurred after a power failure; and that event would not have corrupted Postgres in a properly configured system; thus, pointing to a misconfiguration in the system.



 

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

Предыдущее
От: Andres Freund
Дата:
Сообщение: Re: [External] Re: standby replication server throws invalid memoryalloc request size , does not start up
Следующее
От: Vijaykumar Jain
Дата:
Сообщение: Re: [External] Re: standby replication server throws invalid memoryalloc request size , does not start up