Peter Eisentraut <peter.eisentraut@2ndquadrant.com> writes:
> On 2019-12-04 21:36, Tom Lane wrote:
>> I wonder if the right fix is to not generate a DO_ATTRDEF
>> object at all for generated columns in child tables. Am
>> I right in guessing that we propagate generated-ness to
>> child tables automatically?
> Right. New patch using that approach attached. (Could use more
> extensive comments.)
This looks more plausible than the previous attempt, but it's clearly
still not right, because this is what it changes in the regression
test dump:
--- r.dump.head 2020-02-03 14:16:15.774305437 -0500
+++ r.dump.patch 2020-02-03 14:18:08.599109703 -0500
@@ -15244,14 +15244,7 @@
-- Name: gtest1_1 b; Type: DEFAULT; Schema: public; Owner: postgres
--
-ALTER TABLE ONLY public.gtest1_1 ALTER COLUMN b SET DEFAULT (a * 2);
-
-
---
--- Name: gtest30_1 b; Type: DEFAULT; Schema: public; Owner: postgres
---
-
-ALTER TABLE ONLY public.gtest30_1 ALTER COLUMN b SET DEFAULT (a * 2);
+ALTER TABLE ONLY public.gtest1_1 ALTER COLUMN b SET DEFAULT NULL;
--
This is showing us at least two distinct problems. Now as for
"gtest30_1", what we have is that in the parent table "gtest30", column b
exists but it has no default; the generated property is only added
at the child table gtest30_1. So we need to emit ALTER COLUMN SET
GENERATED ALWAYS for gtest30_1.b. HEAD is already doing the wrong
thing there (it's emitting the expression, but as a plain default
not GENERATED). And this patch makes it emit nothing, even worse.
I think the key point here is that "attislocal" refers to whether the
column itself is locally defined, not to whether its default is.
Things are evidently also going wrong for "gtest1_1". In that case
the generated property is inherited from the parent gtest1, so we
shouldn't be emitting anything ... how come the patch fails to
make it do that?
regards, tom lane