Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1hxlGw-00033Q-Nt for pgsql-hackers@arkaria.postgresql.org; Wed, 14 Aug 2019 04:52:30 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1hxlGv-0004Lb-BF for pgsql-hackers@arkaria.postgresql.org; Wed, 14 Aug 2019 04:52:29 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1hxlGu-0004LT-VU for pgsql-hackers@lists.postgresql.org; Wed, 14 Aug 2019 04:52:29 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.92) (envelope-from ) id 1hxlGn-0004Pk-PJ for pgsql-hackers@postgresql.org; Wed, 14 Aug 2019 04:52:27 +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 x7E4qIVZ011302; Wed, 14 Aug 2019 00:52:18 -0400 From: Tom Lane To: Amit Kapila cc: Robert Haas , Alvaro Herrera , Thomas Munro , vignesh C , Jerry Sievers , Tomas Vondra , pgsql-hackers Subject: Re: SegFault on 9.6.14 In-reply-to: References: <20190812190749.GA13961@alvherre.pgsql> <14905.1565646513@sss.pgh.pa.us> <4832.1565711932@sss.pgh.pa.us> Comments: In-reply-to Amit Kapila message dated "Wed, 14 Aug 2019 10:12:17 +0530" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <11300.1565758338.1@sss.pgh.pa.us> Date: Wed, 14 Aug 2019 00:52:18 -0400 Message-ID: <11301.1565758338@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Amit Kapila writes: > Another point which I am wondering is why can't we use the existing > REWIND flag to solve the current issue, basically if we have access to > that information in nodeLimit.c (ExecLimit), then can't we just pass > down that to ExecShutdownNode? The existing REWIND flag tells subnodes whether they should *optimize* for getting rewound or not. I don't recall right now (well past midnight) why that seemed like a useful definition, but if you grep for places that are paying attention to that flag, I'm sure you'll find out. We probably don't want to give up that distinction --- if it had been equally good to define the flag as a hard yes-or-no, I'm sure we would have taken that definition, because it's simpler. regards, tom lane