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 1iVNMp-00040b-Ho for pgsql-bugs@arkaria.postgresql.org; Thu, 14 Nov 2019 22:13:31 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1iVNMo-0002nr-4o for pgsql-bugs@arkaria.postgresql.org; Thu, 14 Nov 2019 22:13:30 +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 1iVNMn-0002nk-Pf for pgsql-bugs@lists.postgresql.org; Thu, 14 Nov 2019 22:13:29 +0000 Received: from mail-wm1-x342.google.com ([2a00:1450:4864:20::342]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1iVNMg-0006AO-7u for pgsql-bugs@lists.postgresql.org; Thu, 14 Nov 2019 22:13:28 +0000 Received: by mail-wm1-x342.google.com with SMTP id q70so7566851wme.1 for ; Thu, 14 Nov 2019 14:13:21 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=2ndquadrant-com.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:content-transfer-encoding:in-reply-to :user-agent; bh=e3cMeSrv9hmUoJu4cXOzBVBoj7nVds/CK0ni6kAhD/U=; b=VSbyoimJtu2ZLGuf2kPN3OaD1cq+Lwl/LxJzhfXm/ulFn9dMddyCqH6mtqRZ1Af00i UI9qFFmxp5mI9XzhIIsytISmNhuvz9RzOXBWPPlKPIChpmPLfsY4QOmdA5zeAy5rYX+R vSjGcV7bVu+S4KqX46EGpvvgV2v5U+m8oUmw4m64xFZ89j96rG1nPGhtLX6y2v0BHp8W q+yg1wEIdxuacaFxRITKMr3BFqJG0VPr2gvJPevkSD66OCN5vlSzZ1idNGj25/5nxVac w53t71KE7afA96+E0buCboYQvKL0f8OMAMXDr1o8mjCRBjH4fsQwHdKTTj4zpiNLxB/O 9LSg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:content-transfer-encoding :in-reply-to:user-agent; bh=e3cMeSrv9hmUoJu4cXOzBVBoj7nVds/CK0ni6kAhD/U=; b=GtAow4+ZHY8ocjTFbC/W6FmbV2wwg96kwBwzDyuvbiJiCYjdF4FGK6rkuLl+KuGmGH NdCbDEBcgD+YCO2jSTzn6ywecXFfqGthlYFJVfB+Gz5dSclLU/8nac6wZVLo7wpcMJ/Q V2oVwis4RvbQNb3w2koAfsQaJdb3AOSsei7Xvez/mBth9G1Llta6GscI9OQf3UEF9Mul G2hN1sDrDJYsPBngmuDHVkv6cCvJB8jmSom5doJJts77FuzQROmmgMOxN06+yMdcF/mK /P8PFKjNnf/t/7O7P3aMBsmxx9V1Mcrf6saetCb2KK3lyIj6TcauChH8fVfcCnxOZ4Ud r4Tw== X-Gm-Message-State: APjAAAUrih6AFfvxMQEQD9xDcNoRkmFedDfb6ytQkdu2NH/gcFJLqEzq bWI4vFJDjMnnOF+5YF/tIvlseQ== X-Google-Smtp-Source: APXvYqyTuMATlZGdrormZ3Lk2j3paVH2+gWYOjQfpWKlJFpGuEPeVTmX09oCUfKP4/6qiVOrHtyWtA== X-Received: by 2002:a7b:c445:: with SMTP id l5mr10365509wmi.140.1573769600664; Thu, 14 Nov 2019 14:13:20 -0800 (PST) Received: from localhost (ip-86-49-253-92.net.upcbroadband.cz. [86.49.253.92]) by smtp.gmail.com with ESMTPSA id y6sm8743073wrr.19.2019.11.14.14.13.18 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 14 Nov 2019 14:13:18 -0800 (PST) Date: Thu, 14 Nov 2019 23:13:17 +0100 From: Tomas Vondra To: Fan|| <82820676@qq.com> Cc: pgsql-bugs Subject: Re: =?utf-8?B?5Zue5aSN77yaIEJVRyAjMTYxMDI6IFRhYmxlIGNhbid0IGJl?= =?utf-8?Q?_drop_on_PostgreSQ?= =?utf-8?Q?L?= 10.09 if the table was created from PostgreSQL 10.10 Message-ID: <20191114221317.bef2at6wzh3pt5bv@development> References: <16102-3fe2c9426d7faba1@postgresql.org> <982.1573225598@sss.pgh.pa.us> <8523951573232347@vla1-78135a9f092e.qloud-c.yandex.net> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: NeoMutt/20180716 List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk 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" >主题: 回复: 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