From: Burgess, Freddie <Freddie.Burgess@maxar.com>
To: pgsql-bugs@lists.postgresql.org <pgsql-bugs@lists.postgresql.org>
Subject: pg_dump error attempting to upgrade from PostgreSQL 10 to PostgreSQL 12
Date: Thu, 5 Nov 2020 21:19:17 +0000
Message-ID: <DM3P110MB0265AC329BFBD64AB2ADF78BE6EE0@DM3P110MB0265.NAMP110.PROD.OUTLOOK.COM> (raw)
Simple steps:
BACKUP: pg_dump -U postgres -d <database> > sherlock.dmp <- From the pg10 instance
RESTORE: psql -U postgres -d <database> -1 -f sherlock.dmp <- On the pg12 instance
Postgres Log:
free(): invalid pointer
free(): invalid pointer
2020-11-05 14:07:33.784 EST [26] LOG: background worker "parallel worker" (PID 150) was terminated by signal 6: Aborted
2020-11-05 14:07:33.784 EST [26] LOG: terminating any other active server processes
2020-11-05 14:07:33.784 EST [32] WARNING: terminating connection because of crash of another server process
2020-11-05 14:07:33.784 EST [32] DETAIL: The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.
2020-11-05 14:07:33.784 EST [32] HINT: In a moment you should be able to reconnect to the database and repeat your command.
2020-11-05 14:07:33.784 EST [61] WARNING: terminating connection because of crash of another server process
2020-11-05 14:07:33.784 EST [61] DETAIL: The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.
2020-11-05 14:07:33.784 EST [61] HINT: In a moment you should be able to reconnect to the database and repeat your command.
2020-11-05 14:07:34.699 EST [26] LOG: all server processes terminated; reinitializing
2020-11-05 14:07:42.266 EST [154] LOG: database system was interrupted; last known up at 2020-11-05 14:06:02 EST
2020-11-05 14:08:05.855 EST [154] LOG: database system was not properly shut down; automatic recovery in progress
2020-11-05 14:08:05.859 EST [154] LOG: redo starts at 7E/93B22C8
2020-11-05 14:08:15.931 EST [154] LOG: invalid record length at 7F/74ECBE30: wanted 24, got 0
2020-11-05 14:08:15.931 EST [154] LOG: redo done at 7F/74ECBDF8
2020-11-05 14:08:41.673 EST [26] LOG: database system is ready to accept connections
PostgreSQL is installed on a docker container, running on a EC2 instance with 256 GB of memory
This electronic communication and any attachments may contain confidential and proprietary information of Maxar, Inc. If you are not the intended recipient, or an agent or employee responsible for delivering this communication to the intended recipient, or if you have received this communication in error, please do not print, copy, retransmit, disseminate or otherwise use the information. Please indicate to the sender that you have received this communication in error, and delete the copy you received.
Maxar reserves the right to monitor any electronic communication sent or received by its employees, agents or representatives.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-bugs@postgresql.org
Cc: Freddie.Burgess@maxar.com
Subject: Re: pg_dump error attempting to upgrade from PostgreSQL 10 to PostgreSQL 12
In-Reply-To: <DM3P110MB0265AC329BFBD64AB2ADF78BE6EE0@DM3P110MB0265.NAMP110.PROD.OUTLOOK.COM>
References: <DM3P110MB0265AC329BFBD64AB2ADF78BE6EE0@DM3P110MB0265.NAMP110.PROD.OUTLOOK.COM>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox