Re: BUG #17863: Unable to restore dump 12.12 -> 15.2
| От | Andrey Lizenko |
|---|---|
| Тема | Re: BUG #17863: Unable to restore dump 12.12 -> 15.2 |
| Дата | |
| Msg-id | CADKuZZC04-7BR_tUL-cb6X_ybXxWs8HMBF5MBGfCcYP8-CEN5w@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: BUG #17863: Unable to restore dump 12.12 -> 15.2 (Daniel Gustafsson <daniel@yesql.se>) |
| Ответы |
Re: BUG #17863: Unable to restore dump 12.12 -> 15.2
|
| Список | pgsql-bugs |
(copying here as it was a misclick about "reply all" button)
I'll try to, but even plain text dump didn't work
I'll try to, but even plain text dump didn't work
psql:<db_name>_20230323.sql:5672327: ERROR: extra data after last expected column
CONTEXT: COPY alpha_beta, line 3828998: "1643415437295 SRSR MORN1661692859461 NODK MORNINGSTAR f {"fiscalYearEndMonth": "12"} 0P00019YC1 0C00..."
I can check md5sum if there is an idea about network issue.
On Thu, 23 Mar 2023 at 10:43, Daniel Gustafsson <daniel@yesql.se> wrote:
> 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
Regards, Andrei Lizenko
В списке pgsql-bugs по дате отправления: