reviving "custom" dump - Mailing list pgsql-general

From Rob Sargent
Subject reviving "custom" dump
Date
Msg-id 78d93a34-2215-84bc-4c71-a8336e469dbe@gmail.com
Whole thread Raw
Responses Re: reviving "custom" dump  ("David G. Johnston" <david.g.johnston@gmail.com>)
Re: reviving "custom" dump  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-general
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?

pgsql-general by date:

Previous
From: Tom Lane
Date:
Subject: Re: programmatically retrieve details of a custom Postgres type
Next
From: "David G. Johnston"
Date:
Subject: Re: reviving "custom" dump