From: Tom Lane <tgl@sss.pgh.pa.us>
To: Michael Paquier <michael@paquier.xyz>
Cc: Nikolay Shaplov <n.shaplov@postgrespro.ru>
Cc: pgsql-bugs@lists.postgresql.org, Kyotaro Horiguchi <horikyota.ntt@gmail.com>
Subject: Re: BUG #17962: postgresql 11 hangs on poly_contain with specific data
Date: Mon, 12 Jun 2023 09:14:26 -0400
Message-ID: <1166430.1686575666@sss.pgh.pa.us> (raw)
In-Reply-To: <ZIasOCCcis6Nveqm@paquier.xyz>
References: <17962-4f00b6f26724858d@postgresql.org>
<20230606.140749.1678060452808896223.horikyota.ntt@gmail.com>
<20230606.141736.939081296219135931.horikyota.ntt@gmail.com>
<31814440.0auUPBzOZ3@thinkpad-pgpro>
<ZIasOCCcis6Nveqm@paquier.xyz>
Michael Paquier <michael@paquier.xyz> writes:
> Anyway, I am not really convinced that we need to do anything here,
> either, knowing that v12 is able to fail early without relying on
> check_stack_depth(), and that v11 will be EOL'd in a couple of
> months.
Yeah, I couldn't get excited about it either. The fact that an
underflow check stops the loop seems a bit accidental. But the
proposed patch is not noticeably less magic than that, and who's
to say whether it doesn't cause unnecessary failures in other
cases besides the one given?
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, michael@paquier.xyz, n.shaplov@postgrespro.ru, horikyota.ntt@gmail.com
Subject: Re: BUG #17962: postgresql 11 hangs on poly_contain with specific data
In-Reply-To: <1166430.1686575666@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