logrep stuck with 'ERROR: int2vector has too many elements' - Mailing list pgsql-hackers

From Erik Rijkers
Subject logrep stuck with 'ERROR: int2vector has too many elements'
Date
Msg-id 668ba539-33c5-8190-ca11-def2913cb94b@xs4all.nl
Whole thread Raw
Responses Re: logrep stuck with 'ERROR: int2vector has too many elements'
RE: logrep stuck with 'ERROR: int2vector has too many elements'
List 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

pgsql-hackers by date:

Previous
From: Pavel Stehule
Date:
Subject: Re: On login trigger: take three
Next
From: Alvaro Herrera
Date:
Subject: Re: logrep stuck with 'ERROR: int2vector has too many elements'