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 1kIBPY-0008Am-0J for pgsql-bugs@arkaria.postgresql.org; Tue, 15 Sep 2020 13:54:20 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1kIBPW-0003Mg-SN for pgsql-bugs@arkaria.postgresql.org; Tue, 15 Sep 2020 13:54:18 +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 1kIBPW-0003MZ-MP for pgsql-bugs@lists.postgresql.org; Tue, 15 Sep 2020 13:54:18 +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 1kIBPQ-0001eo-4h for pgsql-bugs@lists.postgresql.org; Tue, 15 Sep 2020 13:54:18 +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 08FDs1Q51287700; Tue, 15 Sep 2020 09:54:07 -0400 From: Tom Lane To: 139250065@qq.com cc: pgsql-bugs@lists.postgresql.org Subject: Re: BUG #16616: Segmentation fault when use explain In-reply-to: <16616-a0b27501abf6e83a@postgresql.org> References: <16616-a0b27501abf6e83a@postgresql.org> Comments: In-reply-to PG Bug reporting form message dated "Tue, 15 Sep 2020 03:47:30 -0000" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <1287698.1600178041.1@sss.pgh.pa.us> Date: Tue, 15 Sep 2020 09:54:01 -0400 Message-ID: <1287699.1600178041@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk PG Bug reporting form writes: > I created a extension by C language, and deltatype is a new data type > ... > explain select * from contract_index64s where delta_type <> > 'new'::deltatype limit 1; > server closed the connection unexpectedly I'd say the first assumption is a bug in your extension. Have you tried watching this under a debugger, or examining the stack trace from a crash? regards, tom lane