From: | Rui DeSousa <rui(at)crazybean(dot)net> |
---|---|
To: | Andres Freund <andres(at)anarazel(dot)de> |
Cc: | Vijaykumar Jain <vjain(at)opentable(dot)com>, Scott Ribe <scott_ribe(at)elevated-dev(dot)com>, "pgsql-admin(at)lists(dot)postgresql(dot)org" <pgsql-admin(at)lists(dot)postgresql(dot)org> |
Subject: | Re: [External] standby replication server throws invalid memory alloc request size , does not start up |
Date: | 2018-06-28 17:40:13 |
Message-ID: | 269E778E-21FC-4EA4-846D-52C896E38CDB@crazybean.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
> On Jun 28, 2018, at 12:36 PM, Andres Freund <andres(at)anarazel(dot)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.
From | Date | Subject | |
---|---|---|---|
Next Message | Vijaykumar Jain | 2018-06-29 08:34:01 | Re: [External] Re: standby replication server throws invalid memory alloc request size , does not start up |
Previous Message | Andres Freund | 2018-06-28 17:04:20 | Re: [External] Re: standby replication server throws invalid memory alloc request size , does not start up |