Re: BUG #17561: Server crashes on executing row() with very long argument list

From: Richard Guo <guofenglinux(at)gmail(dot)com>
To: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
Cc: kyzevan23(at)mail(dot)ru, PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org>
Subject: Re: BUG #17561: Server crashes on executing row() with very long argument list
Date: 2022-07-29 10:58:15
Message-ID: CAMbWs48hx8V1PQKHw+fL=ZBPn5Ri+xDPW9wg6oYfmN4qk0=FxA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Fri, Jul 29, 2022 at 6:14 PM Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
wrote:

> Hah, of course. I suppose we'd need something like this ... haven't
> looked for other problem spots.

Yeah, that's what we need to do. I think the check condition should be
something like:

if (cur_resno - 1 > MaxAttrNumber)

Thanks
Richard

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Ajin Cherian 2022-07-29 11:35:57 Re: Excessive number of replication slots for 12->14 logical replication
Previous Message Richard Guo 2022-07-29 10:30:01 Re: BUG #17560: Planner can not find plan with lowest cost