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 1hjAZK-0003dx-Jb for pgsql-bugs@arkaria.postgresql.org; Thu, 04 Jul 2019 22:51:10 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1hjAZH-0004O5-Qy for pgsql-bugs@arkaria.postgresql.org; Thu, 04 Jul 2019 22:51:07 +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 1hjAZH-0004Iq-I1 for pgsql-bugs@lists.postgresql.org; Thu, 04 Jul 2019 22:51:07 +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 1hjAZA-0005T7-G1 for pgsql-bugs@lists.postgresql.org; Thu, 04 Jul 2019 22:51:06 +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 x64MosmQ016957; Thu, 4 Jul 2019 18:50:54 -0400 From: Tom Lane To: "David G. Johnston" cc: Manuel Rigger , PostgreSQL mailing lists Subject: Re: ALTER TABLE results in "ERROR: could not open relation with OID 43707388" In-reply-to: References: Comments: In-reply-to "David G. Johnston" message dated "Thu, 04 Jul 2019 09:24:27 -0700" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <16955.1562280654.1@sss.pgh.pa.us> Date: Thu, 04 Jul 2019 18:50:54 -0400 Message-ID: <16956.1562280654@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk "David G. Johnston" writes: > On Thu, Jul 4, 2019 at 7:42 AM Manuel Rigger > wrote: >> I would expect that the statements are equivalent to the following, >> where the ALTER TABLE actions were split up, and which execute without >> errors: > This has been fixed for version 11.5 which is as yet unreleased. Really? Cause it still fails in HEAD for me. It might be related to that new-in-11.4 bug, or to the old bug we were trying to fix, but I fear it's a distinct problem. I've not had time to dig into the code though. regards, tom lane