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 1kXPgk-00078c-C8 for pgsql-admin@arkaria.postgresql.org; Tue, 27 Oct 2020 14:11:02 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1kXPgj-000090-9k for pgsql-admin@arkaria.postgresql.org; Tue, 27 Oct 2020 14:11:01 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1kXPgj-00008t-2I for pgsql-admin@lists.postgresql.org; Tue, 27 Oct 2020 14:11:01 +0000 Received: from mail-ej1-x643.google.com ([2a00:1450:4864:20::643]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1kXPgc-00019H-0L for pgsql-admin@lists.postgresql.org; Tue, 27 Oct 2020 14:10:59 +0000 Received: by mail-ej1-x643.google.com with SMTP id ce10so2437561ejc.5 for ; Tue, 27 Oct 2020 07:10:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cybertec-at.20150623.gappssmtp.com; s=20150623; h=message-id:subject:from:to:date:in-reply-to:references:user-agent :mime-version:content-transfer-encoding; bh=vOc+NqgkaP9ct8x4z+r2m5NZq/QBlR8egH1Tyyal6ps=; b=hojWtqdAIYKdCTD3r4pP4eC7XVf7DpUnLnPQVLRoKC3Zx9wB4ZEgYyunQ7DndwohRi NVW0PE9LiXQHfZFgxQw1+uaLndbfD1c5Adlzjxd4Z6h7QdPp152N74tvW35hZqKGbmkD CMZhJj3JkAJ+vuNU8fcVEdyUOFjVdOyj8ZnBm6Mgvj0JeAqzhpVFIiVqt9/VmrEXAPHI NXjq8SeLNuHY0yf66gWlYRqmBTqk0Czi5SaytFCtMI1dxUMZSG3VEBxAYxHcI3keoz6J Dt+1jyD+dpUSEq+ZWqsmwoFpi29cCYBzKA3Qk8215iQNNqJ92q4h+hzO/SbdNWyRrUbM AreQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:message-id:subject:from:to:date:in-reply-to :references:user-agent:mime-version:content-transfer-encoding; bh=vOc+NqgkaP9ct8x4z+r2m5NZq/QBlR8egH1Tyyal6ps=; b=szhPWTqKjv6T4delOgUP5w64Jc0ZV2Urafeyk5fj0HN8WE6CS/r3g9h8sghxtxPC89 dl4hJ3tf0vd90wk3T577WNL6BN+/6BNFiGxcy9aLykMSypuhVy3lCDplmEZF0qz05Kyo gaQDUQ7qP4TGPpGYMMx7OGo/phMfqqvajbzUsZHvOnshTVgOXRYHQLfzIhGGBp1psg72 GLrK4SfDcenILboL63A/vK6Y/7gW+LkfrqePUpOEI4yr4krvYx+gcrCXEH6VaUk6p6Co MP+B9CX4wRMyjy1efnstY4LrhTLW9YrBQofEAtTOexU5JgES5yr7P6/NSOVULwKQzc5e LqpQ== X-Gm-Message-State: AOAM530TqGqD9Qp6Y9G+cO8FTOplMADjGJWDwsVlSEoT42lOYyKWMa/L 2D8SSwo4+DavJCMzYOcTiSlcVw== X-Google-Smtp-Source: ABdhPJyr2TdMWaohwCWMsjqQfx2MCNUagu43jgDSNi2Ov50rDsX6b2s6ojJnJhtWiAs+v4BqvERoOA== X-Received: by 2002:a17:906:a1d8:: with SMTP id bx24mr2497265ejb.161.1603807851959; Tue, 27 Oct 2020 07:10:51 -0700 (PDT) Received: from localhost.localdomain (217-149-174-2.nat.highway.telekom.at. [217.149.174.2]) by smtp.gmail.com with ESMTPSA id bx24sm1130330ejb.51.2020.10.27.07.10.51 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 27 Oct 2020 07:10:51 -0700 (PDT) Message-ID: <4ae13029956a4bbcb7f60aee6f97b62c6bf85b98.camel@cybertec.at> Subject: Re: free(): invalid pointer , when to dumping data to a new server From: Laurenz Albe To: Lars Aksel Opsahl , "pgsql-admin@lists.postgresql.org" Date: Tue, 27 Oct 2020 15:10:50 +0100 In-Reply-To: References: , Content-Type: text/plain; charset="UTF-8" User-Agent: Evolution 3.36.5 (3.36.5-1.fc32) MIME-Version: 1.0 Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On Mon, 2020-10-26 at 10:22 +0000, Lars Aksel Opsahl wrote: > I have done some more testing and postgres also crashes right after 'pg_restore --section=pre-data -1' > is done also. Here I also see the 'free(): invalid pointer' in the postgres log. > > This happens on with Postgres 12 and Postgres 13. and any version of postgis I have tested with. > > The pre-data input is little bit more than 200.000 lines with more than 6000 CREATE statements, > if I test with the first 100 lines it does not crash. It seems like no data are lost here because > the server does recovery at startup. > > I tested on another with CentOS and the same software and it worked ok > > The server diagnostic does not indicate any memory errors. > > Dnf search does not give mee any debuginfo file for postgres You'll have to edit "/etc/yum.repos.d/pgdg-fedora-all.repo" and set the "PostgreSQL 13 for Fedora $releasever - $basearch - Debuginfo" repository to "enabled=1". Then you can install the debuginfo packages and generate a stack trace. Yours, Laurenz Albe -- Cybertec | https://www.cybertec-postgresql.com