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 ) id 1fYa13-0000Uq-NO for pgsql-admin@arkaria.postgresql.org; Thu, 28 Jun 2018 16:43:29 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1fYa11-0007b5-IS for pgsql-admin@arkaria.postgresql.org; Thu, 28 Jun 2018 16:43:27 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1fYa11-0007ay-7k for pgsql-admin@lists.postgresql.org; Thu, 28 Jun 2018 16:43:27 +0000 Received: from mailout.easymail.ca ([64.68.200.34]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1fYa0x-0001pk-Ui for pgsql-admin@lists.postgresql.org; Thu, 28 Jun 2018 16:43:25 +0000 Received: from localhost (localhost [127.0.0.1]) by mailout.easymail.ca (Postfix) with ESMTP id 7214321B63; Thu, 28 Jun 2018 16:43:22 +0000 (UTC) Received: from mailout.easymail.ca ([127.0.0.1]) by localhost (emo02-pco.easydns.vpn [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dxKfPApw-mbU; Thu, 28 Jun 2018 16:43:22 +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 15AFD2150E; Thu, 28 Jun 2018 16:43:17 +0000 (UTC) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 11.4 \(3445.8.2\)) Subject: Re: [External] Re: standby replication server throws invalid memory alloc request size , does not start up From: Scott Ribe In-Reply-To: <20180628163642.lg2akxxkyplhxgni@alap3.anarazel.de> Date: Thu, 28 Jun 2018 10:43:16 -0600 Cc: Rui DeSousa , Vijaykumar Jain , "pgsql-admin@lists.postgresql.org" Content-Transfer-Encoding: quoted-printable Message-Id: References: <1E4C5445-F307-4AE9-B1B9-C85A38B0D930@opentable.com> <8F8408A0-7FEB-4F32-8E76-F7429DA0B481@elevated-dev.com> <16835199-C26C-4962-B1BD-3B9766770FAA@opentable.com> <3B059AC5-D674-4D97-9E28-6B17A3FF73D4@crazybean.net> <20180628163642.lg2akxxkyplhxgni@alap3.anarazel.de> To: Andres Freund X-Mailer: Apple Mail (2.3445.8.2) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk > On Jun 28, 2018, at 10:36 AM, Andres Freund = wrote: >=20 > 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.. ? There could always be a postgres bug, however misconfigured cache layers = are a very common cause of this kind of symptom, and postgres bugs very = rare. I don't believe pg_resetxlog would cause this particular problem. = Failure to recovery yes, but not illegal memory operation.=