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 1grwx7-0000ul-Cw for pgsql-hackers@arkaria.postgresql.org; Fri, 08 Feb 2019 03:35:45 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1grwx5-0000du-Nx for pgsql-hackers@arkaria.postgresql.org; Fri, 08 Feb 2019 03:35:43 +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 1grwx5-0000dn-H3 for pgsql-hackers@lists.postgresql.org; Fri, 08 Feb 2019 03:35:43 +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 1grwx3-0001hc-Bb for pgsql-hackers@postgresql.org; Fri, 08 Feb 2019 03:35:43 +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 x183ZYvQ024521; Thu, 7 Feb 2019 22:35:34 -0500 From: Tom Lane To: Peter Geoghegan cc: Alvaro Herrera , PostgreSQL Hackers Subject: Re: Fixing findDependentObjects()'s dependency on scan order (regressions in DROP diagnostic messages) In-reply-to: References: <20190205212829.GA20127@alvherre.pgsql> <4572.1549404528@sss.pgh.pa.us> <20444.1549423295@sss.pgh.pa.us> <26049.1549516498@sss.pgh.pa.us> Comments: In-reply-to Peter Geoghegan message dated "Thu, 07 Feb 2019 18:53:34 -0800" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <24519.1549596934.1@sss.pgh.pa.us> Date: Thu, 07 Feb 2019 22:35:34 -0500 Message-ID: <24520.1549596934@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Peter Geoghegan writes: > On Wed, Feb 6, 2019 at 9:15 PM Tom Lane wrote: >> I have a mostly-working patch along these lines that I hope to >> finish up and post tomorrow. > Do you think that you'll end up pushing the HEAD-only fix shortly? I have a working patch now, but I think I'm too tired to explain it, so I'm going to post it tomorrow instead. It's a big enough change that it might be advisable for someone to review it --- are you interested? regards, tom lane