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

>
> Does the indicated line in the dumped file indeed have too many columns

will check
it was generated by pg_dump -Fp ... as an ordinary sql file
but, may be makes sense - was trying to restore by this:

> pg_dump -V
> pg_dump (PostgreSQL) *12.12* (Ubuntu 12.12-0ubuntu0.20.04.1)

psql -V
> psql (PostgreSQL) *13.3*

Is it the last line of the COPY into this table?

Answer is above. I'm still trying to reproduce in the correct short way. At
the moment I don't understand, where is the problem - it is happening in
random places.

On Fri, 24 Mar 2023 at 09:13, Daniel Gustafsson <daniel(at)yesql(dot)se> wrote:

> > On 24 Mar 2023, at 07:50, Andrey Lizenko <lizenko79(at)gmail(dot)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 data itself.
> > 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
>
>

--
Regards, Andrei Lizenko