From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
Cc: | Amit Langote <amitlangote09(at)gmail(dot)com>, pgsql-committers(at)lists(dot)postgresql(dot)org |
Subject: | Re: pgsql: Improve handling of inherited GENERATED expressions. |
Date: | 2023-01-12 20:44:29 |
Message-ID: | 1340662.1673556269@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers |
I wrote:
> Yeah. I think best bet may be to drop the problematic table(s),
> as we've done for other de-supported DDL situations. A quick
> experiment suggests that
> DROP TABLE gtest_normal_child;
> DROP TABLE gtest_normal_child2;
> should do it.
Some testing here confirms that the attached patch is enough to
un-break things for HEAD. Since you mentioned you have some other
quasi-urgent BF fixes, maybe the thing to do is to roll up a release
now and then work on the bigger idea at leisure.
regards, tom lane
Attachment | Content-Type | Size |
---|---|---|
fix-generated-child-tables.patch | text/x-diff | 1.2 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Dunstan | 2023-01-12 21:41:40 | Re: pgsql: Improve handling of inherited GENERATED expressions. |
Previous Message | Alexander Korotkov | 2023-01-12 15:30:06 | pgsql: Fix jsonpath existense checking of missing variables |