From: Tom Lane <tgl@sss.pgh.pa.us>
To: Richard Guo <guofenglinux@gmail.com>
Cc: Alvaro Herrera <alvherre@alvh.no-ip.org>
Cc: kyzevan23@mail.ru, PostgreSQL mailing lists <pgsql-bugs@lists.postgresql.org>
Subject: Re: BUG #17561: Server crashes on executing row() with very long argument list
Date: Fri, 29 Jul 2022 12:57:49 -0400
Message-ID: <3822706.1659113869@sss.pgh.pa.us> (raw)
In-Reply-To: <CAMbWs487ax-wLBEQ2be3MJYUUxZYPfmhxHF1gsOb7PQB1tTg=A@mail.gmail.com>
References: <20220729101411.7b45rvhlrsgcajjo@alvherre.pgsql>
<3753050.1659102953@sss.pgh.pa.us>
<3768321.1659105655@sss.pgh.pa.us>
<CAMbWs487ax-wLBEQ2be3MJYUUxZYPfmhxHF1gsOb7PQB1tTg=A@mail.gmail.com>
Richard Guo <guofenglinux@gmail.com> writes:
> The patch looks good to me. Just wondering if there are any other types
> of expressions that need to check for MaxTupleAttributeNumber in
> parse_expr.c.
As far as I can think, sub-SELECTs and ROW constructs are the only
SQL that can produce composites of non-pre-determined types.
For constructs producing named composite types, the limit on the
number of columns in a table should take care of it.
What I'm more troubled by is whether there are any ways to produce
a wide tuple that don't come through either the parser or a table
definition. Not sure what that could look like, other than C code
randomly constructing a RowExpr or some such.
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-bugs@postgresql.org
Cc: tgl@sss.pgh.pa.us, guofenglinux@gmail.com, alvherre@alvh.no-ip.org, pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #17561: Server crashes on executing row() with very long argument list
In-Reply-To: <3822706.1659113869@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox