Re: pg_dump weirdness
От | John Scalia |
---|---|
Тема | Re: pg_dump weirdness |
Дата | |
Msg-id | ACC3CCDF-797E-493A-A28B-EF2E932D1C53@gmail.com обсуждение исходный текст |
Ответ на | Re: pg_dump weirdness (Tom Lane <tgl@sss.pgh.pa.us>) |
Список | 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@sss.pgh.pa.us> wrote: > > "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 understandingyou 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
В списке pgsql-admin по дате отправления: