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 1k5q4E-0000wj-EC for pgsql-bugs@arkaria.postgresql.org; Wed, 12 Aug 2020 12:41:18 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1k5q4D-0002H2-7n for pgsql-bugs@arkaria.postgresql.org; Wed, 12 Aug 2020 12:41:17 +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 1k5q4D-0002Gv-1e for pgsql-bugs@lists.postgresql.org; Wed, 12 Aug 2020 12:41:17 +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 1k5q4A-00017v-FW for pgsql-bugs@lists.postgresql.org; Wed, 12 Aug 2020 12:41:16 +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 07CCfBL0103737; Wed, 12 Aug 2020 08:41:11 -0400 From: Tom Lane To: demirci.alikemal@gmail.com cc: pgsql-bugs@lists.postgresql.org Subject: Re: BUG #16578: When making an insert, the database goes to recover mode In-reply-to: <16578-e899b292ba2566a1@postgresql.org> References: <16578-e899b292ba2566a1@postgresql.org> Comments: In-reply-to PG Bug reporting form message dated "Wed, 12 Aug 2020 07:45:03 -0000" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <103735.1597236071.1@sss.pgh.pa.us> Date: Wed, 12 Aug 2020 08:41:11 -0400 Message-ID: <103736.1597236071@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk PG Bug reporting form writes: > When this script is run, we get the following error. > 2020-08-12 10:37:18.676 +03 [94157] LOG: server process (PID 5175) was > terminated by signal 11: Segmentation fault That's interesting, but there is no way to tell from here whether it's a bug, or corrupted data, or what. Can you provide a self-contained test case? regards, tom lane