Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1f71GQ-0006yZ-Tw for pgsql-admin@arkaria.postgresql.org; Fri, 13 Apr 2018 16:09:27 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1f71GP-0005cH-VN for pgsql-admin@arkaria.postgresql.org; Fri, 13 Apr 2018 16:09:25 +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 1f71GP-0005c7-L4 for pgsql-admin@lists.postgresql.org; Fri, 13 Apr 2018 16:09:25 +0000 Received: from tamriel.snowman.net ([2001:470:e38f::11]) by makus.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1f71GM-0002n4-VH for pgsql-admin@postgresql.org; Fri, 13 Apr 2018 16:09:24 +0000 Received: by tamriel.snowman.net (Postfix, from userid 1000) id 2BB3C5F79C; Fri, 13 Apr 2018 12:09:22 -0400 (EDT) Date: Fri, 13 Apr 2018 12:09:22 -0400 From: Stephen Frost To: Don Seiler Cc: pgsql-admin Subject: Re: ERROR: invalid memory alloc in Pg 9.6.6 Message-ID: <20180413160921.GO27724@tamriel.snowman.net> References: MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="ewIlFbbLnYFKahON" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.24 (2015-08-30) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk --ewIlFbbLnYFKahON Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Greetings, * Don Seiler (don@seiler.us) wrote: > Started seeing "invalid memory alloc" errors in a non-production DB (9.6.= 6) > all of a sudden this afternoon. It's running on CentOS 7.4 on VMWare. >=20 > I ran a pg_dump on that DB and got this error almost immediately: >=20 > pg_dump: [archiver (db)] query failed: ERROR: invalid memory alloc reque= st > size 8830452760576 That's interesting. An invalid memory alloc request size complaint such as that tends to be an indicator of corruption or a bug in the backend possibly. Certainly curious that you were able to run the query and not hit that.. Are you sure you were running it exactly the way pg_dump does? There's a bunch of setup that pg_dump does early on, maybe log all queries when you run the pg_dump and then in a psql session try running them..? If you can reliably reproduce this with either pg_dump or psql, then the next step would perhaps be jumping in with gdb to see where that error is being hit.. Thanks! Stephen --ewIlFbbLnYFKahON Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAEBCgAGBQJa0NYxAAoJEO1sijiDR2RVa5gP/0IoIs6C3SpEYT/EfKule1sY ID8+8zzAIHEJsg3dlKte9yfCnYzzMdhTT0WBpnHxyiEAk/ejARA6aDB4yF8DDHRc QrSl0oTkoEgeU0xVojF2smFz80D9KFuiOkkoTyBfmt2e44T/T/GTUU59h1EElXJo O69dgd0dI7cTM/rZY7tZcRT7HWi+B+cCEyDDAWEnMl/092hFVVqelY5dxHRE5jzF cpgR7xyrh4/qZ6UG4f3S9oJNc9Ztp5Jx3tNyNEFdxwB0IGacuMvkxMC1T6TXSuqt 6xzvP9/1d5GWYvqmNitkjFzEc2PSCZc/PNLbnNsEl6oR5Rp04I8qKH6XsRTRqa3n mVk3c6JDjnlyH6qlDPXpWRuj700gaFPWkNFBWzW+49k/swjp8Bs55s5WBV/w6yl2 HjML9enNeJx8jMzfyIpHWblTLd3rLBqU77GVPQATl2zQWnodBRDpLn9qDaNIWNxG sr3fKPBKjupWjFXSgHwub+em3k3ZVOiOcRzplv6jTRSosLvcunGPCPBedtP/G2PM trI64vykxkzsdYcnQ3scJZQQ8oKrN7g2k7TciYp5GRrJEDc9PUrOlgxZaGZAIaqi 6o+oFP2QuDHSAIUK0ONeln8vsNSFJlqsikomEocwUsFTmfltWQ8Y2W4xLk1zbEL9 pVX0/t9a8o8hadEUvVGC =WvRm -----END PGP SIGNATURE----- --ewIlFbbLnYFKahON--