| From: | Daniel Gustafsson <daniel(at)yesql(dot)se> |
|---|---|
| To: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
| Cc: | Masahiko Sawada <masahiko(dot)sawada(at)2ndquadrant(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Dumping/restoring fails on inherited generated column |
| Date: | 2020-09-25 13:51:37 |
| Message-ID: | 17D8397B-8C85-4B8D-9045-873DB693FA9F@yesql.se |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> On 25 Sep 2020, at 15:07, Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> 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.
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Masahiko Sawada | 2020-09-25 14:11:27 | Re: Transactions involving multiple postgres foreign servers, take 2 |
| Previous Message | Bharath Rupireddy | 2020-09-25 13:09:32 | Re: Parallel INSERT (INTO ... SELECT ...) |