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 1iT5ri-0004K7-VN for pgsql-bugs@arkaria.postgresql.org; Fri, 08 Nov 2019 15:07:59 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1iT5rh-00064w-Oc for pgsql-bugs@arkaria.postgresql.org; Fri, 08 Nov 2019 15:07:57 +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 1iT5qX-00040y-2E for pgsql-bugs@lists.postgresql.org; Fri, 08 Nov 2019 15:06:45 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1iT5qU-0007vl-Ia for pgsql-bugs@lists.postgresql.org; Fri, 08 Nov 2019 15:06: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 xA8F6cdI000983; Fri, 8 Nov 2019 10:06:40 -0500 From: Tom Lane To: 82820676@qq.com cc: pgsql-bugs@lists.postgresql.org Subject: Re: BUG #16102: Table can't be drop on PostgreSQL 10.09 if the table was created from PostgreSQL 10.10 In-reply-to: <16102-3fe2c9426d7faba1@postgresql.org> References: <16102-3fe2c9426d7faba1@postgresql.org> Comments: In-reply-to PG Bug reporting form message dated "Fri, 08 Nov 2019 09:28:55 +0000" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <981.1573225598.1@sss.pgh.pa.us> Date: Fri, 08 Nov 2019 10:06:38 -0500 Message-ID: <982.1573225598@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk PG Bug reporting form writes: > Have anyone meet table can't be drop on PostgreSQL 10.09 if the table was > created from PostgreSQL 10.10? Certainly possible, seeing that the 10.10 release notes mention additional dependency rules for partitioned tables: * Install dependencies to prevent dropping partition key columns > 2) Remove v10.10 and use v10.09 start with same storage (our downgrade test > on K8s, storage are decouple with application ) It is not, never has been, and never will be supported to try to run a cluster with an older server version after it's been modified by a newer one. We have enough trouble ensuring forwards compatibility. Having said that, the 10.10 bug fix should only have made a difference in cases where a table's partition key columns involve non-built-in types, which isn't the case in your example. I wonder whether this is pilot error, e.g. you created and dropped the pgbench_accounts table in some other schema than "public", but there's still one in "public". regards, tom lane