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

From: Julien Rouhaud <rjuju123(at)gmail(dot)com>
To: frank picabia <fpicabia(at)gmail(dot)com>
Cc: "pgsql-generallists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org>
Subject: Re: Empty tablespace directory after restore with psql -d dbname -f dump.sql
Date: 2021-05-16 12:45:02
Message-ID: CAOBaU_Y70Q0S1n6kgFdUFfU7eETW4G2_gC5iHAFVxW=5GFCcGA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Le sam. 15 mai 2021 à 01:14, frank picabia <fpicabia(at)gmail(dot)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.

>

In response to

Browse pgsql-general by date

  From Date Subject
Next Message David Rowley 2021-05-16 12:57:32 Re: Postgres upgrade 12 - issues with OIDs
Previous Message David G. Johnston 2021-05-16 01:00:42 Re: Postgres upgrade 12 - issues with OIDs