Re: Dumping/restoring fails on inherited generated column - Mailing list pgsql-hackers

From Daniel Gustafsson
Subject Re: Dumping/restoring fails on inherited generated column
Date
Msg-id 17D8397B-8C85-4B8D-9045-873DB693FA9F@yesql.se
Whole thread Raw
In response to Re: Dumping/restoring fails on inherited generated column  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
List pgsql-hackers
> On 25 Sep 2020, at 15:07, Peter Eisentraut <peter.eisentraut@2ndquadrant.com> wrote:

> We could probably fix this by having ALTER TABLE ONLY / DROP EXPRESSION update the attlocal column of direct children
totrue, to make the catalog state look like something that can be restored.  However, that's a fair amount of
complicatedcode, so for now I propose to just prohibit this command, meaning you can't use ONLY in this command if
thereare children.  This is new in PG13, so this change would have very limited impact in practice. 

That sounds a bit dramatic.  Do you propose to do that in v13 as well or just
in HEAD?  If the latter, considering that the window until the 14 freeze is
quite wide shouldn't we try to fix it first?

cheers ./daniel


pgsql-hackers by date:

Previous
From: Bharath Rupireddy
Date:
Subject: Re: Parallel INSERT (INTO ... SELECT ...)
Next
From: Masahiko Sawada
Date:
Subject: Re: Transactions involving multiple postgres foreign servers, take 2