Re: Empty tablespace directory after restore with psql -d dbname -f dump.sql - Mailing list pgsql-general

From Julien Rouhaud
Subject Re: Empty tablespace directory after restore with psql -d dbname -f dump.sql
Date
Msg-id CAOBaU_Y70Q0S1n6kgFdUFfU7eETW4G2_gC5iHAFVxW=5GFCcGA@mail.gmail.com
Whole thread Raw
In response to Empty tablespace directory after restore with psql -d dbname -f dump.sql  (frank picabia <fpicabia@gmail.com>)
List pgsql-general
Le sam. 15 mai 2021 à 01:14, frank picabia <fpicabia@gmail.com> a écrit :

We cancelled a web application upgrade part way through when it was realized
Postgres needed a version upgrade first.  Using the dump file extracted from
a full dump with pg_dumpall the DB was restored with a line like :

 psql -d dbname -f dump.sql

The file dump.sql was extracted from the full dump using the script
pg_extract.sh script provided on Github by someone (not sure which fork).

Others may want to take note, this tool does not include the declaration
of TABLESPACE and its location.  So the tablespace files will be
in the general data area.  \db+ reports tablespace is defined, but it's
just empty.  If you have a CREATE TABLESPACE with LOCATION in your full
dump, you should add it back into the extracted result for a single DB.

it would probably be much more helpful if you reported that to on the original repo, so other users will have a better chance to be aware of that problem, and the author might also learn about the issue and fix it. 

pgsql-general by date:

Previous
From: "David G. Johnston"
Date:
Subject: Re: Postgres upgrade 12 - issues with OIDs
Next
From: David Rowley
Date:
Subject: Re: Postgres upgrade 12 - issues with OIDs