reviving "custom" dump

Started by Rob Sargentover 3 years ago5 messagesgeneral
Jump to latest
#1Rob Sargent
robjsargent@gmail.com

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?

#2David G. Johnston
david.g.johnston@gmail.com
In reply to: Rob Sargent (#1)
Re: reviving "custom" dump

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?

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.

#3Tom Lane
tgl@sss.pgh.pa.us
In reply to: Rob Sargent (#1)
Re: reviving "custom" dump

Rob Sargent <robjsargent@gmail.com> writes:

Short version: Does a current version of postgres tolerate ascii dumps
from older versions?

We intend it to. Have you got an actual problem?

regards, tom lane

#4Rob Sargent
robjsargent@gmail.com
In reply to: Tom Lane (#3)
Re: reviving "custom" dump

On 11/10/22 23:29, Tom Lane wrote:

Rob Sargent<robjsargent@gmail.com> writes:

Short version: Does a current version of postgres tolerate ascii dumps
from older versions?

We intend it to. Have you got an actual problem?

regards, tom lane

I have to lay out options in the morning.  Thanks.  Now off to follow
David's justified pointer.

#5Rob Sargent
robjsargent@gmail.com
In reply to: David G. Johnston (#2)
Re: reviving "custom" dump

On 11/10/22 23:29, David G. Johnston wrote:

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?

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.

Off by one error here perhaps:  I have a custom dump in hand, it's
restoring that is the problem.  But pretty sure the take home from
pg_restore is "Use the newer version both ways".  Though mildly amused
at the

; Dumped from database version: 8.3.5
; Dumped by pg_dump version: 8.3.8

in the re-ordering example!