Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1kXRTB-0002zG-HH for pgsql-admin@arkaria.postgresql.org; Tue, 27 Oct 2020 16:05:09 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1kXRT9-00083n-5A for pgsql-admin@arkaria.postgresql.org; Tue, 27 Oct 2020 16:05:07 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1kXRT8-00083g-UE for pgsql-admin@lists.postgresql.org; Tue, 27 Oct 2020 16:05:06 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1kXRT6-0007Va-Dp for pgsql-admin@lists.postgresql.org; Tue, 27 Oct 2020 16:05:06 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 09RG4xAR1058473; Tue, 27 Oct 2020 12:05:00 -0400 From: Tom Lane To: Lars Aksel Opsahl cc: Laurenz Albe , "pgsql-admin@lists.postgresql.org" Subject: Re: free(): invalid pointer , when to dumping data to a new server In-reply-to: References: , ,<4ae13029956a4bbcb7f60aee6f97b62c6bf85b98.camel@cybertec.at> Comments: In-reply-to Lars Aksel Opsahl message dated "Tue, 27 Oct 2020 15:15:10 -0000" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <1058471.1603814699.1@sss.pgh.pa.us> Content-Transfer-Encoding: quoted-printable Date: Tue, 27 Oct 2020 12:04:59 -0400 Message-ID: <1058472.1603814699@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Lars Aksel Opsahl writes: > Here is the new stackstrace not too much info that helps mee thou. This is probably the reason why "bt" is producing garbage: > BFD: warning: /var/lib/systemd/coredump/core.postmaster.26.6f7d98107f544= 085a41c6f8b876418d0.298120.1603810048000000 is truncated: expected core fi= le size >=3D 2326896640, found: 2147483648 So the core file is being truncated at 2GB, but the process image was a little bit larger than that. You need to get a complete core file. First thing I'd check is the "ulimit -c" setting that the postmaster is being started under. I see that systemd is capturing the core dump, so it could also be that there's some systemd configuration you need to adjust ("man systemd-coredump" might help here). regards, tom lane