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

From: Nikolay Shaplov <n(dot)shaplov(at)postgrespro(dot)ru>
To: 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-06 10:39:06
Message-ID: 31814440.0auUPBzOZ3@thinkpad-pgpro
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

В письме от вторник, 6 июня 2023 г. 08:17:36 MSK пользователь Kyotaro
Horiguchi написал:
> At Tue, 06 Jun 2023 14:07:49 +0900 (JST), Kyotaro Horiguchi
> <horikyota(dot)ntt(at)gmail(dot)com> wrote in
> > A feasible fix might be to detect infinite recursion. The attached
> > works for the this specific case well.
>
> FWIW for this tentative version, fixed several misspelling in error
> messages and a comment.

Thank you for your work!

Actually I know how to find such bugs, but I do not know how to fix it. (Or,
more precisely, fixing will keep me for long from finding more)

Hope somebody will apply the fix to the proper branch :-)

--
Nikolay Shaplov aka Nataraj
Fuzzing Engineer at Postgres Professional
Matrix IM: @dhyan:nataraj.su

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message PG Bug reporting form 2023-06-06 11:16:47 BUG #17964: Missed query planner optimization
Previous Message PG Bug reporting form 2023-06-06 08:32:44 BUG #17963: Recursive table cannot be referenced when using LEFT JOIN instead of LATERAL in recursive term