From: Tom Lane <tgl@sss.pgh.pa.us>
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
Date: Fri, 08 Nov 2019 10:06:38 -0500
Message-ID: <982.1573225598@sss.pgh.pa.us> (raw)
In-Reply-To: <16102-3fe2c9426d7faba1@postgresql.org>
References: <16102-3fe2c9426d7faba1@postgresql.org>
PG Bug reporting form <noreply@postgresql.org> 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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-bugs@postgresql.org
Cc: tgl@sss.pgh.pa.us, 82820676@qq.com
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: <982.1573225598@sss.pgh.pa.us>
References: <16102-3fe2c9426d7faba1@postgresql.org> <982.1573225598@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox