Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1f1EuY-00084t-Ii for pgsql-hackers@arkaria.postgresql.org; Wed, 28 Mar 2018 17:30:58 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1f1EuX-0005Oq-Hp for pgsql-hackers@arkaria.postgresql.org; Wed, 28 Mar 2018 17:30:57 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1f1EuX-0005Oh-7U for pgsql-hackers@lists.postgresql.org; Wed, 28 Mar 2018 17:30:57 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1f1EuU-00033i-GH for pgsql-hackers@lists.postgresql.org; Wed, 28 Mar 2018 17:30:56 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.4/8.14.4) with ESMTP id w2SHUnd6000875; Wed, 28 Mar 2018 13:30:49 -0400 From: Tom Lane To: Peter Geoghegan cc: Kyotaro HORIGUCHI , Aleksandr Parfenov , PostgreSQL Hackers Subject: Re: PostgreSQL crashes with SIGSEGV In-reply-to: References: <20180326.211438.61614860.horiguchi.kyotaro@lab.ntt.co.jp> Comments: In-reply-to Peter Geoghegan message dated "Mon, 26 Mar 2018 20:40:51 -0700" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <873.1522258249.1@sss.pgh.pa.us> Date: Wed, 28 Mar 2018 13:30:49 -0400 Message-ID: <874.1522258249@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Peter Geoghegan writes: > On Mon, Mar 26, 2018 at 5:14 AM, Kyotaro HORIGUCHI > wrote: >> If no one objects, I'll mark this as Ready for Commit in a couple >> of days. > Thank you for the review, Horiguchi-san. It's hard to decide how > important each goal is when coming up with a back-patchable fix like > this. When the goals are somewhat in competition with each other, a > second or a third opinion is particularly appreciated. It looks good to me. The only real objection would be if someone came up with a test case proving that there's a significant performance degradation from the extra copies. But given that these are back branches, it would take a pretty steep penalty for me to want to take the risk of refactoring to avoid that. I've pushed it with some cosmetic adjustments. regards, tom lane