logrep stuck with 'ERROR: int2vector has too many elements'

From: Erik Rijkers <er(at)xs4all(dot)nl>
To: pgsql-hackers(at)postgresql(dot)org
Subject: logrep stuck with 'ERROR: int2vector has too many elements'
Date: 2023-01-15 09:35:24
Message-ID: 668ba539-33c5-8190-ca11-def2913cb94b@xs4all.nl
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hello,

Logical replication sometimes gets stuck with
ERROR: int2vector has too many elements

I can't find the exact circumstances that cause it but it has something
to do with many columns (or adding many columns) in combination with
perhaps generated columns.

This replication test, in a slightly different form, used to work. This
is also suggested by the fact that the attached runs without errors in
REL_15_STABLE but gets stuck in HEAD.

What it does: it initdbs and runs two instances, primary and replica. In
the primary 'pgbench -is1' done, and many columns, including 1 generated
column, are added to all 4 pgbench tables. This is then
pg_dump/pg_restored to the replica, and a short pgbench is run. The
result tables on primary and replica are compared for the final result.
(To run it will need some tweaks to directory and connection parms)

I ran it on both v15 and v16 for 25 runs: with the parameters as given
15 has no problem while 16 always got stuck with the int2vector error.
(15 can actually be pushed up to the max of 1600 columns per table
without errors)

Both REL_15_STABLE and 16devel built from recent master on Debian 10,
gcc 12.2.0.

I hope someone understands what's going wrong.

Thanks,

Erik Rijkers

Attachment Content-Type Size
logrepbug.sh application/x-shellscript 8.5 KB

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2023-01-15 11:33:40 Re: logrep stuck with 'ERROR: int2vector has too many elements'
Previous Message Pavel Stehule 2023-01-15 06:32:17 Re: On login trigger: take three