Message-ID: <0e0c7ddf3461dacb46458164b34e56c17baad93a.camel@cybertec.at>
Subject: Re: pg_upgrade from Postgresql-12 to Postgresql-13 fails with
 "Creating dump of database schemas postgres *failure*"
From: Laurenz Albe <laurenz.albe@cybertec.at>
To: "Yoong S. Chow" <chowy1026@gmail.com>,
 pgsql-general@lists.postgresql.org,  pgsql-admin@lists.postgresql.org
Date: Fri, 18 Feb 2022 16:06:40 +0100
In-Reply-To: 
 <CACdHDupmCSG+z2NZt1xar2cpanC4S+-9OiU3hLm4FDa7_Wra6Q@mail.gmail.com>
References: 
	<CACdHDupmCSG+z2NZt1xar2cpanC4S+-9OiU3hLm4FDa7_Wra6Q@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"
User-Agent: Evolution 3.40.4 (3.40.4-2.fc34) 
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Archived-At: 
 <https://www.postgresql.org/message-id/0e0c7ddf3461dacb46458164b34e56c17baad93a.camel%40cybertec.at>
Precedence: bulk

On Fri, 2022-02-18 at 13:17 +0800, Yoong S. Chow wrote:
> I was trying to perform `pg_upgrade` from Postgresql-12 to Postgresql-13
> (after being advised that upgrading from Postgresql-12 to Postgresql-14
> is biting off much more than I could chew... ).

That was bad advice.

> The `pg_upgrade --check` went through OK. But the actual `pg_upgrade`
> always get error at the step of Creating dump of database schemas for
> `postgres` database.

Buried in your logs I find

  free(): invalid pointer

Perhaps you have found a PostgreSQL bug.  Then it would be gread if you
could provide a reproducer.

But perhaps there is an extension installed that causes that error?

Does a plain pg_dumpall succeed?

Yours,
Laurenz Albe
-- 
Cybertec | https://www.cybertec-postgresql.com