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 1nyiqp-0007v7-CA for pgsql-bugs@arkaria.postgresql.org; Tue, 07 Jun 2022 23:43:07 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1nyiqo-0000HD-7F for pgsql-bugs@arkaria.postgresql.org; Tue, 07 Jun 2022 23:43:06 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nyiqn-0000Gh-VN for pgsql-bugs@lists.postgresql.org; Tue, 07 Jun 2022 23:43:05 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nyiql-0007OZ-MZ for pgsql-bugs@lists.postgresql.org; Tue, 07 Jun 2022 23:43:05 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 257Nh1K71432709; Tue, 7 Jun 2022 19:43:01 -0400 From: Tom Lane To: David Rowley cc: =?UTF-8?B?QWxlxaEgWmVsZW7DvQ==?= , PostgreSQL mailing lists Subject: Re: BUG #17512: Process running query fails with SIGSEV - nodeMemoize.c:349 In-reply-to: References: <17512-36fa5fab90f48af9@postgresql.org> <1264308.1654628854@sss.pgh.pa.us> Comments: In-reply-to David Rowley message dated "Wed, 08 Jun 2022 11:39:41 +1200" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <1432707.1654645381.1@sss.pgh.pa.us> Content-Transfer-Encoding: quoted-printable Date: Tue, 07 Jun 2022 19:43:01 -0400 Message-ID: <1432708.1654645381@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk David Rowley writes: > server closed the connection unexpectedly Ugh. > If I patch it with the attached rebustify_memoize_code.patch, I get: > # explain analyze select * from t1 inner join t1 t2 on t1.a=3Dt2.a where= t1.a<=3D2; > ERROR: unable to find memoization table entry > My thoughts are that we likely should make this code more robust, > despite the bug not being related to a broken data type. I'm only just > over the fence on that one though. Any thoughts? Strong +1, but please s/unable to/could not/, per message style guidelines. regards, tom lane