Re: BUG #17863: Unable to restore dump 12.12 -> 15.2

From: Andrey Lizenko <lizenko79(at)gmail(dot)com>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: pgsql-bugs(at)lists(dot)postgresql(dot)org, Daniel Gustafsson <daniel(at)yesql(dot)se>
Subject: Re: BUG #17863: Unable to restore dump 12.12 -> 15.2
Date: 2023-03-27 09:17:46
Message-ID: CADKuZZBmyQkXHhAiP6ze0LWrGx2mFLVJ5+vzH=UyokDeFuiuoA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

>
> 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(at)anarazel(dot)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

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message PG Bug reporting form 2023-03-27 10:00:01 BUG #17872: Dropping an attribute of a composite type breaks indexes over the type silently
Previous Message PG Bug reporting form 2023-03-27 08:04:59 BUG #17871: JIT during postgresql_fdw remote_estimates EXPLAIN have very negatively effect on planning time