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

From: Daniel Gustafsson <daniel(at)yesql(dot)se>
To: lizenko79(at)gmail(dot)com, pgsql-bugs <pgsql-bugs(at)lists(dot)postgresql(dot)org>
Subject: Re: BUG #17863: Unable to restore dump 12.12 -> 15.2
Date: 2023-03-23 09:42:57
Message-ID: 23B3BDA4-BE88-40FE-8008-722B1BF6DC82@yesql.se
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

> On 22 Mar 2023, at 22:42, PG Bug reporting form <noreply(at)postgresql(dot)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

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Andrey Lizenko 2023-03-23 11:30:20 Re: BUG #17863: Unable to restore dump 12.12 -> 15.2
Previous Message 1024 2023-03-23 08:32:04 An update deadlock bug