From: Tom Lane <tgl@sss.pgh.pa.us>
To: MichaelDBA@sqlexec.com <michaeldba@sqlexec.com>
Cc: John Scalia <jayknowsunix@gmail.com>
Cc: pgsql-admin@lists.postgresql.org
Subject: Re: pg_dump weirdness
Date: Fri, 05 Nov 2021 20:47:56 -0400
Message-ID: <451539.1636159676@sss.pgh.pa.us> (raw)
In-Reply-To: <61A06E76-7897-4603-B6B4-CA67BBFC2547@sqlexec.com>
References: <492eb0ca-d43e-e732-61bd-17293fff431a@gmail.com>
<61A06E76-7897-4603-B6B4-CA67BBFC2547@sqlexec.com>
"MichaelDBA@sqlexec.com" <michaeldba@sqlexec.com> writes:
> You cannot use a newer version of pgdump to export and then insert it into an older version of PostgreSQL if I am understanding you correctly.
Well, you can try. You might get errors from DDL syntax the older server
doesn't understand, but usually that won't happen if the dump is taken
from a server of that vintage or older. We don't promise anything, but
I'd expect it to usually work.
I'm a little suspicious of the OP's claim that there were only warnings
and not errors while trying to restore the dump -- an error would go a
long way towards explaining the report. In any case, we'd need to see
all those warnings to have much chance of diagnosing this.
regards, tom lane
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 using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: tgl@sss.pgh.pa.us, michaeldba@sqlexec.com, jayknowsunix@gmail.com, pgsql-admin@lists.postgresql.org
Subject: Re: pg_dump weirdness
In-Reply-To: <451539.1636159676@sss.pgh.pa.us>
* 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