| From: | Scott Ribe <scott_ribe(at)elevated-dev(dot)com> |
|---|---|
| To: | Vijaykumar Jain <vjain(at)opentable(dot)com> |
| Cc: | "pgsql-admin(at)lists(dot)postgresql(dot)org" <pgsql-admin(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: standby replication server throws invalid memory alloc request size , does not start up |
| Date: | 2018-06-28 13:26:28 |
| Message-ID: | 8F8408A0-7FEB-4F32-8E76-F7429DA0B481@elevated-dev.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
You need to worry, very much, that your setup did not preserve data write ordering when the power went out.
- you might have fsync turned off in PG
- you might be using a non-journaled filesystem
- your disks might be cheating on sync commands (consumer grade disks are notorious for this)
- you might be using consumer-grade flash that can't flush its cache on power loss
This highly unlikely to be a PG bug, and you do need to worry that it could have been the master if you had been less lucky.
--
Scott Ribe
scott_ribe(at)elevated-dev(dot)com
https://www.linkedin.com/in/scottribe/
> On Jun 28, 2018, at 7:17 AM, Vijaykumar Jain <vjain(at)opentable(dot)com> wrote:
>
> My only concern was do I need to worry about this error showing up again?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Scott Ribe | 2018-06-28 13:30:06 | Re: standby replication server throws invalid memory alloc request size , does not start up |
| Previous Message | Vijaykumar Jain | 2018-06-28 13:17:52 | standby replication server throws invalid memory alloc request size , does not start up |