Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
From: John Scalia <jayknowsunix@gmail.com>
Mime-Version: 1.0 (1.0)
Subject: Re: pg_dump weirdness
Date: Fri, 5 Nov 2021 22:41:42 -0400
Message-Id: <ACC3CCDF-797E-493A-A28B-EF2E932D1C53@gmail.com>
References: <451539.1636159676@sss.pgh.pa.us>
Cc: michaeldba@sqlexec.com, pgsql-admin@lists.postgresql.org
In-Reply-To: <451539.1636159676@sss.pgh.pa.us>
To: Tom Lane <tgl@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/ACC3CCDF-797E-493A-A28B-EF2E932D1C53%40gmail.com>
Precedence: bulk

I=E2=80=99ll capture the warnings on Monday and share them here, but I hones=
tly saw nothing that should have broken the load. Plus, no one has mentioned=
 why the restore took over 1/2 hour but nothing was loaded.

Sent from my iPhone

> On Nov 5, 2021, at 20:47, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>=20
> =EF=BB=BF"MichaelDBA@sqlexec.com" <michaeldba@sqlexec.com> writes:
>> You cannot use a newer version of pgdump to export and then insert it int=
o an older version of PostgreSQL if I am understanding you correctly.
>=20
> 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.
>=20
> 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.
>=20
>            regards, tom lane