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

From Daniel Gustafsson
Subject Re: BUG #17863: Unable to restore dump 12.12 -> 15.2
Date
Msg-id 23B3BDA4-BE88-40FE-8008-722B1BF6DC82@yesql.se
Whole thread Raw
In response to BUG #17863: Unable to restore dump 12.12 -> 15.2  (PG Bug reporting form <noreply@postgresql.org>)
Responses Re: BUG #17863: Unable to restore dump 12.12 -> 15.2  (Andrey Lizenko <lizenko79@gmail.com>)
List pgsql-bugs
> On 22 Mar 2023, at 22:42, PG Bug reporting form <noreply@postgresql.org> wrote:

> pg_restore: processing data for table "<db_name>.consensus_estimate"
> pg_restore: error: could not uncompress data: (null)

This error indicates, as it clearly states, a failure to decompress the
compressed file, but it's a bit worrying that the error is (null) since this
really should report an error.  Handling an empty ->msg seems like something we
maybe should do.

Does dumping/restoring any database in your cluster work?  Is it just this one
that fails?

--
Daniel Gustafsson




pgsql-bugs by date:

Previous
From: "1024"
Date:
Subject: An update deadlock bug
Next
From: Andrey Lizenko
Date:
Subject: Re: BUG #17863: Unable to restore dump 12.12 -> 15.2