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 | CADKuZZBbEko8WkzToNOo0K3_oqZiNqgggMFmadZy=2fvkQnKQw@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 |
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@yesql.se> wrote:
> On 23 Mar 2023, at 12:30, Andrey Lizenko <lizenko79@gmail.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
В списке pgsql-bugs по дате отправления: