| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | Rob Sargent <robjsargent(at)gmail(dot)com> |
| Cc: | "pgsql-generallists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: reviving "custom" dump |
| Date: | 2022-11-11 06:29:10 |
| Message-ID: | CAKFQuwZVDNmirtMSwsTaLtzee=s9syC+s8fKOG4d3bjTZPJZMQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Thu, Nov 10, 2022 at 11:13 PM Rob Sargent <robjsargent(at)gmail(dot)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?
>
>
https://www.postgresql.org/docs/current/app-pgdump.html
You should read the description and notes sections for how this command
works and its capabilities and potential limitations.
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2022-11-11 06:29:29 | Re: reviving "custom" dump |
| Previous Message | Rob Sargent | 2022-11-11 06:13:28 | reviving "custom" dump |