Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1q6UKx-0001Kb-V6 for pgsql-bugs@arkaria.postgresql.org; Tue, 06 Jun 2023 10:54:52 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1q6UKt-0000YV-Sh for pgsql-bugs@arkaria.postgresql.org; Tue, 06 Jun 2023 10:54:47 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1q6U5q-0001Td-58 for pgsql-bugs@lists.postgresql.org; Tue, 06 Jun 2023 10:39:14 +0000 Received: from mail.postgrespro.ru ([93.174.131.139]) by makus.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1q6U5l-000Vv4-5U for pgsql-bugs@lists.postgresql.org; Tue, 06 Jun 2023 10:39:12 +0000 Received: from thinkpad-pgpro.localnet (unknown [192.168.28.62]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mail.postgrespro.ru (Postfix/25) with ESMTPSA id C73CCE20EA2; Tue, 6 Jun 2023 13:41:05 +0300 (MSK) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=postgrespro.ru; s=mx2023; t=1686048065; bh=0RrA2SKQDANXfhqDyi/dFIrRhUn4gnPd8h1j1agMFGk=; h=From:To:Subject:Date:Message-ID:In-Reply-To:References:From; b=HESqGiJU0TwA50XFrND7I9w4+Uti2T6++QUvn19WrSkOjos8XJOaiNugx5Ri61gYW q74ScHQaz5rVa7CeKsNtcga55oSXb3ncosVwEQgZQLOzrEB7+9qX9hDL8zD9xL2G49 I6mxCxpdq4FRGLJYXNyF+JnDlROcrALRfX4zwq9JZFsct55/8qjrgtECH/Uy/m4Jht TrqQA678U7GyxLRLT+VdqJjwTY06Vx3b68uhnCMHrUCgABdSfW9tDuUaNMh/mg/gAt 5kNQJG7bgjx44ku7Jpucbk34XDJtJxqOEPfDFDJgZqJE4OyyunE99Ajwdv66UnWNUo ihwK5vmz1Vu6Q== From: Nikolay Shaplov To: pgsql-bugs@lists.postgresql.org, Kyotaro Horiguchi Subject: Re: BUG #17962: postgresql 11 hangs on poly_contain with specific data Date: Tue, 06 Jun 2023 13:39:06 +0300 Message-ID: <31814440.0auUPBzOZ3@thinkpad-pgpro> In-Reply-To: <20230606.141736.939081296219135931.horikyota.ntt@gmail.com> References: <17962-4f00b6f26724858d@postgresql.org> <20230606.140749.1678060452808896223.horikyota.ntt@gmail.com> <20230606.141736.939081296219135931.horikyota.ntt@gmail.com> MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="UTF-8" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk =D0=92 =D0=BF=D0=B8=D1=81=D1=8C=D0=BC=D0=B5 =D0=BE=D1=82 =D0=B2=D1=82=D0=BE= =D1=80=D0=BD=D0=B8=D0=BA, 6 =D0=B8=D1=8E=D0=BD=D1=8F 2023 =D0=B3. 08:17:36 = MSK =D0=BF=D0=BE=D0=BB=D1=8C=D0=B7=D0=BE=D0=B2=D0=B0=D1=82=D0=B5=D0=BB=D1= =8C Kyotaro=20 Horiguchi =D0=BD=D0=B0=D0=BF=D0=B8=D1=81=D0=B0=D0=BB: > At Tue, 06 Jun 2023 14:07:49 +0900 (JST), Kyotaro Horiguchi > wrote in > > A feasible fix might be to detect infinite recursion. The attached > > works for the this specific case well. >=20 > 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= ,=20 more precisely, fixing will keep me for long from finding more) Hope somebody will apply the fix to the proper branch :-) =2D-=20 Nikolay Shaplov aka Nataraj =46uzzing Engineer at Postgres Professional Matrix IM: @dhyan:nataraj.su