Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1lnZmz-0000L6-79 for pgsql-performance@arkaria.postgresql.org; Mon, 31 May 2021 04:44:33 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1lnZmx-0004GJ-Io for pgsql-performance@arkaria.postgresql.org; Mon, 31 May 2021 04:44:31 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1lnZmx-0004GB-Ad for pgsql-performance@lists.postgresql.org; Mon, 31 May 2021 04:44:31 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1lnZmu-0004XW-Mr for pgsql-performance@lists.postgresql.org; Mon, 31 May 2021 04:44:30 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 14V4iRjL2524030; Mon, 31 May 2021 00:44:27 -0400 From: Tom Lane To: "Dean Gibson (DB Administrator)" cc: "pgsql-performance@lists.postgresql.org" Subject: Re: AWS forcing PG upgrade from v9.6 a disaster In-reply-to: <5463af86-9007-1094-78bf-18e54c60edaf@mailpen.com> References: <88dec70b-eb63-0b72-0b5d-253851ef127b@mailpen.com> <92cc8563-195f-8727-d887-5f2bb63f231f@mailpen.com> <2370D2C6-4D91-4C96-9410-11EFD9954B21@thebuild.com> <5463af86-9007-1094-78bf-18e54c60edaf@mailpen.com> Comments: In-reply-to "Dean Gibson (DB Administrator)" message dated "Sun, 30 May 2021 21:23:43 -0700" MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-ID: <2524028.1622436267.1@sss.pgh.pa.us> Content-Transfer-Encoding: 8bit Date: Mon, 31 May 2021 00:44:27 -0400 Message-ID: <2524029.1622436267@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk "Dean Gibson (DB Administrator)" writes: > I thought that having a "USING" clause, was semantically equivalent to > an "ON" clause with the equalities explicitly stated.  So no, I didn't > try that. USING is not that, or at least not only that ... read the manual. I'm wondering if what you saw is some side-effect of the aliasing that USING does. regards, tom lane