From: Michael Paquier <michael@paquier.xyz>
To: 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 14:25:12 +0900
Message-ID: <ZIasOCCcis6Nveqm@paquier.xyz> (raw)
In-Reply-To: <31814440.0auUPBzOZ3@thinkpad-pgpro>
References: <17962-4f00b6f26724858d@postgresql.org>
<20230606.140749.1678060452808896223.horikyota.ntt@gmail.com>
<20230606.141736.939081296219135931.horikyota.ntt@gmail.com>
<31814440.0auUPBzOZ3@thinkpad-pgpro>
On Tue, Jun 06, 2023 at 01:39:06PM +0300, Nikolay Shaplov wrote:
> Hope somebody will apply the fix to the proper branch :-)
Is that a side effect of 6bf0bc8 and 764a554? Hmm, I am not sure to
see how this refactoring is influencing the result here.
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.
--
Michael
Attachments:
signature.asc (application/pgp-signature, 832B) download
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: 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: <ZIasOCCcis6Nveqm@paquier.xyz>
* 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