Re: reviving "custom" dump
| От | David G. Johnston |
|---|---|
| Тема | Re: reviving "custom" dump |
| Дата | |
| Msg-id | CAKFQuwZVDNmirtMSwsTaLtzee=s9syC+s8fKOG4d3bjTZPJZMQ@mail.gmail.com обсуждение исходный текст |
| Ответ на | reviving "custom" dump (Rob Sargent <robjsargent@gmail.com>) |
| Ответы |
Re: reviving "custom" dump
|
| Список | pgsql-general |
On Thu, Nov 10, 2022 at 11:13 PM Rob Sargent <robjsargent@gmail.com> wrote:
Short version: Does a current version of postgres tolerate ascii dumps from older versions?
I've been charged with reviving an old project. I have a dump dated July of 2021 which file tells me is a "PostgreSQL custom database dump V1.13-0". If our compute centre won't roll me a V12(?) postgres server, I'll need to use an "office" machine to bring this dataset back to life. If I pull that off can I make an ascii dump and import that into our main db server (V14) or will I have to also install V14 in the office and dump/restore with that?
You should read the description and notes sections for how this command works and its capabilities and potential limitations.
David J.
В списке pgsql-general по дате отправления: