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 31F3A69D-5BB5-43AE-9372-D3D16CD695EA@yesql.se
Whole thread Raw
In response to Re: BUG #17863: Unable to restore dump 12.12 -> 15.2  (Andrey Lizenko <lizenko79@gmail.com>)
Responses Re: BUG #17863: Unable to restore dump 12.12 -> 15.2  (Andrey Lizenko <lizenko79@gmail.com>)
List pgsql-bugs
> On 24 Mar 2023, at 07:50, Andrey Lizenko <lizenko79@gmail.com> wrote:
>
> small reproducible test case
> It is so only on large table(s) with sizes at least more, than 1262 MB. I think it is about amount of data, not about
dataitself. 
> Like this
> psql:alizenko.sql:3108625: ERROR:  extra data after last expected column
> CONTEXT:  COPY <table_name2>, line 2424915: "1643415437295 KYOCY   MORNINGSTAR     f       {"rSquare": 38.657029,
"nonDivBeta":0.9944, "nonDivAlpha": 0.0042..." 
>
> Any ideas how to debug?

Does the indicated line in the dumped file indeed have too many columns, or
does it contain any value which is incorrectly quoted and thus tricks the
parser into believing so?  Is it the last line of the COPY into this table?

> Or I may try to obfuscate my example and share it somehow.

Sharing a 1Gb repro is cumbersome, maybe you can create a script which
generates data which can reproduce the problem?

--
Daniel Gustafsson




pgsql-bugs by date:

Previous
From: PG Bug reporting form
Date:
Subject: BUG #17867: pg_dump intermittently hangs
Next
From: Ricky
Date:
Subject: Fwd: BUG #17857: Uninstaller does not work