From: | John Scalia <jayknowsunix(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | michaeldba(at)sqlexec(dot)com, pgsql-admin(at)lists(dot)postgresql(dot)org |
Subject: | Re: pg_dump weirdness |
Date: | 2021-11-06 02:41:42 |
Message-ID: | ACC3CCDF-797E-493A-A28B-EF2E932D1C53@gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
I’ll capture the warnings on Monday and share them here, but I honestly 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(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
> "MichaelDBA(at)sqlexec(dot)com" <michaeldba(at)sqlexec(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | MichaelDBA | 2021-11-06 13:25:33 | Re: pg_dump weirdness |
Previous Message | Tom Lane | 2021-11-06 00:47:56 | Re: pg_dump weirdness |