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 1kZxgY-0001ww-Jt for pgsql-hackers@arkaria.postgresql.org; Tue, 03 Nov 2020 14:53:22 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1kZxgX-0004SQ-IF for pgsql-hackers@arkaria.postgresql.org; Tue, 03 Nov 2020 14:53:21 +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 1kZxgW-0004SI-Pq for pgsql-hackers@lists.postgresql.org; Tue, 03 Nov 2020 14:53:21 +0000 Received: from wforward3-smtp.messagingengine.com ([64.147.123.22]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1kZxgS-0007o2-P5 for pgsql-hackers@lists.postgresql.org; Tue, 03 Nov 2020 14:53:20 +0000 Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailforward.west.internal (Postfix) with ESMTP id F04B5C2B; Tue, 3 Nov 2020 09:53:12 -0500 (EST) Received: from mailfrontend2 ([10.202.2.163]) by compute1.internal (MEProxy); Tue, 03 Nov 2020 09:53:13 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm1; bh=Ow6gb9wyfErrUQ1gkI704bmXfGxxv2LqPgOtakfub UM=; b=nVC5D/9Bcd7dwSa/KoPAnYfLjlK/yx+HfW8zJ97g2yeBdxtlHqQSGaifK BIwCzghXoVkLj1WI9mwAmhq0z2ibzeRCn05FJJw1NasgzfD5Y5q1cLI+8Rce/uvB HYkXQXdlwTZDqPlAHrNiiyU6I+4BoTOfjbFVNpWSliHH2WSEsoN4qqOe3yAE45Cc tRI1/aGvkrwYrX3q82Ec/z+3rQ6nDATIO3cbo5IdMQNUvkP9kS3UKZksqlW3iEmn 0ZCfoNo6h70JYoHQvOGjQz3h+fEoNpbPpjxxY8foBVXS5sois+jEW0Hx1F58Z/m2 nMPYvTIZAKFU8KtNkuRLtC75wP3GA== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedujedruddtfedgieejucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepuffhvfhfohfkffgfgggjtgfgsehtjeertddtfeejnecuhfhrohhmpefrvght vghrucfgihhsvghnthhrrghuthcuoehpvghtvghrrdgvihhsvghnthhrrghuthesvdhnug hquhgrughrrghnthdrtghomheqnecuggftrfgrthhtvghrnheptdehfefgvdduffdufedv jeefudekgeduveejvefhuddukeeuhfdvveeujeefvdetnecuffhomhgrihhnpedvnhguqh hurggurhgrnhhtrdgtohhmnecukfhppeekjedrudejjedrjedurddvvdejnecuvehluhhs thgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomhepphgvthgvrhdrvghish gvnhhtrhgruhhtsedvnhguqhhurggurhgrnhhtrdgtohhm X-ME-Proxy: Received: from april.pezone.net (p57b147e3.dip0.t-ipconnect.de [87.177.71.227]) by mail.messagingengine.com (Postfix) with ESMTPA id DDD443064680; Tue, 3 Nov 2020 09:53:11 -0500 (EST) Subject: Re: Dumping/restoring fails on inherited generated column From: Peter Eisentraut To: Masahiko Sawada , Tom Lane References: <15830.1575468847@sss.pgh.pa.us> <31905.1575491779@sss.pgh.pa.us> <24369.1580758361@sss.pgh.pa.us> <3f272982-0e0d-17a1-3fb6-fedc74197676@2ndquadrant.com> <3169466.1594841366@sss.pgh.pa.us> Cc: PostgreSQL Hackers Organization: 2ndQuadrant Message-ID: <87182204-d0ab-abd1-15fc-9da4e251efc6@2ndquadrant.com> Date: Tue, 3 Nov 2020 15:53:10 +0100 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:52.0) Gecko/20100101 Thunderbird/52.9.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On 2020-09-25 15:07, Peter Eisentraut wrote: > We could probably fix this by having ALTER TABLE ONLY / DROP EXPRESSION > update the attlocal column of direct children to true, to make the > catalog state look like something that can be restored. However, that's > a fair amount of complicated code, so for now I propose to just prohibit > this command, meaning you can't use ONLY in this command if there are > children. This is new in PG13, so this change would have very limited > impact in practice. With the minor releases coming up, I have committed this patch and will work on getting the remaining pg_dump issues fixed as well. -- Peter Eisentraut http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services