Received: from malur.postgresql.org ([2a02:16a8:dc51::56])
	by arkaria.postgresql.org with esmtps
 (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256)
	(Exim 4.89)
	(envelope-from <pgsql-admin-owner+archive@lists.postgresql.org>)
	id 1fYWwZ-00055X-Vc
	for pgsql-admin@arkaria.postgresql.org; Thu, 28 Jun 2018 13:26:40 +0000
Received: from localhost ([127.0.0.1] helo=malur.postgresql.org)
	by malur.postgresql.org with esmtp (Exim 4.89)
	(envelope-from <pgsql-admin-owner+archive@lists.postgresql.org>)
	id 1fYWwY-0001Gb-Ab
	for pgsql-admin@arkaria.postgresql.org; Thu, 28 Jun 2018 13:26:38 +0000
Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29])
	by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256)
	(Exim 4.89)
	(envelope-from <scott_ribe@elevated-dev.com>)
	id 1fYWwY-0001GS-3G
	for pgsql-admin@lists.postgresql.org; Thu, 28 Jun 2018 13:26:38 +0000
Received: from mailout.easymail.ca ([64.68.200.34])
	by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256)
	(Exim 4.89)
	(envelope-from <scott_ribe@elevated-dev.com>)
	id 1fYWwU-0006Iy-I9
	for pgsql-admin@lists.postgresql.org; Thu, 28 Jun 2018 13:26:37 +0000
Received: from localhost (localhost [127.0.0.1])
	by mailout.easymail.ca (Postfix) with ESMTP id AC68840CF9;
	Thu, 28 Jun 2018 13:26:31 +0000 (UTC)
Received: from mailout.easymail.ca ([127.0.0.1])
	by localhost (emo03-pco.easydns.vpn [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 2o4MJGsStrBf; Thu, 28 Jun 2018 13:26:31 +0000 (UTC)
Received: from [192.168.2.16] (unknown [8.39.228.117])
	(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
	(No client certificate requested)
	by mailout.easymail.ca (Postfix) with ESMTPSA id 0C5A7412F7;
	Thu, 28 Jun 2018 13:26:29 +0000 (UTC)
Content-Type: text/plain;
	charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 11.4 \(3445.8.2\))
Subject: Re: standby replication server throws invalid memory alloc request
 size , does not start up
From: Scott Ribe <scott_ribe@elevated-dev.com>
In-Reply-To: <1E4C5445-F307-4AE9-B1B9-C85A38B0D930@opentable.com>
Date: Thu, 28 Jun 2018 07:26:28 -0600
Cc: "pgsql-admin@lists.postgresql.org" <pgsql-admin@lists.postgresql.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <8F8408A0-7FEB-4F32-8E76-F7429DA0B481@elevated-dev.com>
References: <1E4C5445-F307-4AE9-B1B9-C85A38B0D930@opentable.com>
To: Vijaykumar Jain <vjain@opentable.com>
X-Mailer: Apple Mail (2.3445.8.2)
List-Id: <pgsql-admin.lists.postgresql.org>
List-Help: <https://lists.postgresql.org/manage/>
List-Subscribe: <https://lists.postgresql.org/manage/>
List-Post: <mailto:pgsql-admin@lists.postgresql.org>
List-Owner: <mailto:pgsql-admin-owner@lists.postgresql.org>
List-Archive: <https://www.postgresql.org/list/pgsql-admin>
Precedence: bulk

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:
>=20
> My only concern was do I need to worry about this error showing up =
again?