Postgres Pro
Downloads
Home   >   mailing lists

Re: BUG #17863: Unable to restore dump 12.12 -> 15.2 - Mailing list pgsql-bugs

From Andrey Lizenko
Subject Re: BUG #17863: Unable to restore dump 12.12 -> 15.2
Date
Msg-id CADKuZZBmyQkXHhAiP6ze0LWrGx2mFLVJ5+vzH=UyokDeFuiuoA@mail.gmail.com
Whole thread Raw
In response to Re: BUG #17863: Unable to restore dump 12.12 -> 15.2  (Andres Freund <andres@anarazel.de>)
Responses Re: BUG #17863: Unable to restore dump 12.12 -> 15.2
List pgsql-bugs
Tree view
If you use 12.12's pg_restore to convert the .dmp file to a text file (using
the --file=somefile, instead of -h/-d), does that work?

(just to be sure, that it is not a typo) 
The idea is to make a dump then start pg_restore in 12.12 to itself?

On Fri, 24 Mar 2023 at 22:27, Andres Freund <andres@anarazel.de> wrote:
Hi,

On 2023-03-22 21:42:56 +0000, PG Bug reporting form wrote:
> 12.12
>  pg_dump -Fc -Z 9 -v -f ./<db_name>_20230322.dmp <db_name>
>
> 15.2
> pg_restore -U <user_name> -h 127.0.0.1 -v -d ./<db_name>_20230322.dmp
>
> In short:
> pg_restore: processing data for table "<db_name>.consensus_estimate"
> pg_restore: error: could not uncompress data: (null)

If you use 12.12's pg_restore to convert the .dmp file to a text file (using
the --file=somefile, instead of -h/-d), does that work?

Greetings,

Andres Freund




--
Regards, Andrei Lizenko

pgsql-bugs by date:

Previous
From: PG Bug reporting form
Date:
Subject: BUG #17871: JIT during postgresql_fdw remote_estimates EXPLAIN have very negatively effect on planning time
Next
From: PG Bug reporting form
Date:
Subject: BUG #17872: Dropping an attribute of a composite type breaks indexes over the type silently