From: Tom Lane <tgl@sss.pgh.pa.us>
To: "MichaelDBA@sqlexec.com" <michaeldba@sqlexec.com>
cc: John Scalia <jayknowsunix@gmail.com>, pgsql-admin@lists.postgresql.org
Subject: Re: pg_dump weirdness
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>
Comments: In-reply-to "MichaelDBA@sqlexec.com" <michaeldba@sqlexec.com>
	message dated "Fri, 05 Nov 2021 16:59:02 -0400"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <451538.1636159676.1@sss.pgh.pa.us>
Content-Transfer-Encoding: quoted-printable
Date: Fri, 05 Nov 2021 20:47:56 -0400
Message-ID: <451539.1636159676@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/451539.1636159676%40sss.pgh.pa.us>
Precedence: bulk

"MichaelDBA@sqlexec.com" <michaeldba@sqlexec.com> writes:
> You cannot use a newer version of pgdump to export and then insert it in=
to 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