Re: BUG #17962: postgresql 11 hangs on poly_contain with specific data

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Nikolay Shaplov <n(dot)shaplov(at)postgrespro(dot)ru>
Cc: pgsql-bugs(at)lists(dot)postgresql(dot)org, Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>
Subject: Re: BUG #17962: postgresql 11 hangs on poly_contain with specific data
Date: 2023-06-12 05:25:12
Message-ID: ZIasOCCcis6Nveqm@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

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

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Michael Paquier 2023-06-12 06:52:40 Re: pg_dump assertion failure with "-n pg_catalog"
Previous Message Michael Paquier 2023-06-12 05:04:53 Re: Server crash with parallel workers with Postgres 14.7