From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
Cc: | Erik Rijkers <er(at)xs4all(dot)nl>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: logrep stuck with 'ERROR: int2vector has too many elements' |
Date: | 2023-01-15 16:06:33 |
Message-ID: | 1408806.1673798793@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> writes:
> On 2023-Jan-15, Erik Rijkers wrote:
>> 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.
Yeah. So remove the limit in int2vectorin (probably also oidvectorin),
or change logrep to use int2[] not int2vector, or both.
> 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?
Probably didn't have a dependency on int2vector before.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Nathan Bossart | 2023-01-15 16:10:54 | Re: Code review in dsa.c |
Previous Message | Zhang Mingli | 2023-01-15 16:04:56 | Re: Code review in dsa.c |