From: Scott Ribe <scott_ribe@elevated-dev.com>
To: Vijaykumar Jain <vjain@opentable.com>
Cc: pgsql-admin@lists.postgresql.org <pgsql-admin@lists.postgresql.org>
Subject: Re: standby replication server throws invalid memory alloc request size , does not start up
Date: Thu, 28 Jun 2018 07:26:28 -0600
Message-ID: <8F8408A0-7FEB-4F32-8E76-F7429DA0B481@elevated-dev.com> (raw)
In-Reply-To: <1E4C5445-F307-4AE9-B1B9-C85A38B0D930@opentable.com>
References: <1E4C5445-F307-4AE9-B1B9-C85A38B0D930@opentable.com>
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@elevated-dev.com
https://www.linkedin.com/in/scottribe/> On Jun 28, 2018, at 7:17 AM, Vijaykumar Jain <vjain@opentable.com> wrote:
>
> My only concern was do I need to worry about this error showing up again?
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: scott_ribe@elevated-dev.com, vjain@opentable.com, pgsql-admin@lists.postgresql.org
Subject: Re: standby replication server throws invalid memory alloc request size , does not start up
In-Reply-To: <8F8408A0-7FEB-4F32-8E76-F7429DA0B481@elevated-dev.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox