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

From Alvaro Herrera
Subject Re: logrep stuck with 'ERROR: int2vector has too many elements'
Date
Msg-id 20230115113340.stsnesk744z57vlu@alvherre.pgsql
Whole thread Raw
In response to logrep stuck with 'ERROR: int2vector has too many elements'  (Erik Rijkers <er@xs4all.nl>)
Responses Re: logrep stuck with 'ERROR: int2vector has too many elements'
Re: logrep stuck with 'ERROR: int2vector has too many elements'
List pgsql-hackers
On 2023-Jan-15, Erik Rijkers wrote:

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

Weird.  This error comes from int2vectorin which amusingly only wants to
read up to FUNC_MAX_ARGS values in the array (100 in the default config,
but it can be changed in pg_config_manual.h).  I wonder how come we
haven't noticed this before ... surely we use int2vector's for other
things than function argument lists nowadays.

At the same time, I don't understand why it fails in 16 but not in 15.
Maybe something changed in the way we process the column lists in 16?


-- 
Álvaro Herrera         PostgreSQL Developer  —  https://www.EnterpriseDB.com/
"Update: super-fast reaction on the Postgres bugs mailing list. The report
was acknowledged [...], and a fix is under discussion.
The wonders of open-source !"
             https://twitter.com/gunnarmorling/status/1596080409259003906



pgsql-hackers by date:

Previous
From: Erik Rijkers
Date:
Subject: logrep stuck with 'ERROR: int2vector has too many elements'
Next
From: Erik Rijkers
Date:
Subject: Re: logrep stuck with 'ERROR: int2vector has too many elements'