On Thu, Nov 14, 2019 at 04:13:10PM +0800, Fan|| wrote:
>Sorry, sent to wrong mail.
>Sent again.
>
Please don't top post, it makes following the discussion much harder.
>
>------------------ 原始邮件 ------------------
>发件人: "我自己的邮箱"<82820676@qq.com>;
>发送时间: 2019年11月12日(星期二) 上午9:32
>收件人: "Sergei Kornilov"<sk@zsrv.org>;
>
>主题: 回复： BUG #16102: Table can't be drop on PostgreSQL 10.09 if the table was created from PostgreSQL 10.10
>
>Hello,
>
>Thanks for the reply. I understand this is an issue really sounds strange.
>
>So, form document it saying that it should be not problem when switching between minor release.
The linked docs are about internal on-disk format, and that's true. It
simply means minor releases do no change on-disk format of data files,
so pg_upgrade nor dump/reload is needed.
The issue here is that a minor version fixed some sorf of bug, affecting
catalog contents, probably by adding a missing dependency between
objects. The older minor release is unaware of that, making the drop
fail. But that's expected, as Tom explains.
We need to be able to make these changes, because that's what bug fixes
often require. And we can't stop doing that.
So we only support upgrades, i.e. going from 12.0 -> 12.1 -> 12.3 ...
and the chance of us supporting downgrades is pretty much nil.
>Will you assign someone take to look this issue? Do you need the full
>script? It's like 100% reproduce.
>
Unlikely. Very few users need the capability to downgrade to older minor
releases, and I don't think anyone is going to work on that. If it is an
important feature for you, you'll need to look into what would it take
to support it and submit a patch.
regards
--
Tomas Vondra http://www.2ndQuadrant.com
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services