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 1hxIBH-0002ja-J3 for pgsql-hackers@arkaria.postgresql.org; Mon, 12 Aug 2019 21:48:43 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1hxIBG-0007ff-D4 for pgsql-hackers@arkaria.postgresql.org; Mon, 12 Aug 2019 21:48:42 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1hxIBG-0007fX-3w for pgsql-hackers@lists.postgresql.org; Mon, 12 Aug 2019 21:48:42 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1hxIBC-0006Ei-V8 for pgsql-hackers@postgresql.org; Mon, 12 Aug 2019 21:48:41 +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 x7CLmXX8014906; Mon, 12 Aug 2019 17:48:33 -0400 From: Tom Lane To: Robert Haas cc: Alvaro Herrera , Thomas Munro , vignesh C , Amit Kapila , Jerry Sievers , Tomas Vondra , pgsql-hackers Subject: Re: SegFault on 9.6.14 In-reply-to: References: <20190812190749.GA13961@alvherre.pgsql> Comments: In-reply-to Robert Haas message dated "Mon, 12 Aug 2019 17:42:21 -0400" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <14904.1565646513.1@sss.pgh.pa.us> Date: Mon, 12 Aug 2019 17:48:33 -0400 Message-ID: <14905.1565646513@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Robert Haas writes: > Being able to do that sort of thing was one of my goals in designing > the ExecShutdownNode stuff. Unfortunately, it's clear from this bug > report that it's still a few bricks short of a load, and Tom doesn't > seem real optimistic about how easy it will be to buy those bricks at > discount prices. But I hope we persist in trying to get there, because > I don't like the idea of saying that we'll never be smart enough to > know we're done with any part of the plan until we're definitely done > with the whole thing. I think that's leaving too much money on the > table. To clarify my position --- I think it's definitely possible to improve the situation a great deal. We "just" have to pass down more information about whether rescans are possible. What I don't believe is that that leads to a bug fix that would be sane to back-patch as far as 9.6. regards, tom lane