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

From: Andrey Lizenko <lizenko79(at)gmail(dot)com>
To: Daniel Gustafsson <daniel(at)yesql(dot)se>
Cc: 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 11:37:51
Message-ID: CADKuZZBbEko8WkzToNOo0K3_oqZiNqgggMFmadZy=2fvkQnKQw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

will try to, it would take some time. But may be we have two problems here.

On Thu, 23 Mar 2023 at 12:32, Daniel Gustafsson <daniel(at)yesql(dot)se> wrote:

> > On 23 Mar 2023, at 12:30, Andrey Lizenko <lizenko79(at)gmail(dot)com> wrote:
> >
> > (copying here as it was a misclick about "reply all" button)
> >
> > 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.
>
> Are you able to generate a small reproducible test case with a schema like
> yours and a row of data which fails like this?
>
> --
> Daniel Gustafsson
>
>

--
Regards, Andrei Lizenko

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message PG Bug reporting form 2023-03-23 12:22:53 BUG #17865: Logical decoding : JDBC - Out of memory exception (WAL2JSON Format -1) gives a wrong associated LSN
Previous Message Daniel Gustafsson 2023-03-23 11:31:58 Re: BUG #17863: Unable to restore dump 12.12 -> 15.2