| From: | Amit Langote <amitlangote09(at)gmail(dot)com> |
|---|---|
| To: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: ATExecAddColumn() doesn't merge inherited properties |
| Date: | 2022-09-09 05:59:09 |
| Message-ID: | CA+HiwqFDjfh+rgCeT01F-sqXf64EYQQK+rpVos=BPaNZM1fE7w@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Sep 8, 2022 at 9:03 PM Amit Langote <amitlangote09(at)gmail(dot)com> wrote:
> While testing Alvaro's "cataloguing NOT NULL constraints" patch [1], I
> noticed a behavior of inherited column merging during ALTER TABLE that
> I thought might be a bug (though see at the bottom).
>
> I feel like we may have discussed this before and decided that the
> $subject is left that way intentionally, but wanted to bring this up
> again in the light of Alvaro's patch which touches nearby code.
> Should we try to fix this?
I found a not-so-old email where we indeed called this (allowing a
child table's column to be nullable when it is marked NOT NULL in a
parent) a bug that should be fixed:
--
Thanks, Amit Langote
EDB: http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2022-09-09 06:14:51 | Re: why can't a table be part of the same publication as its schema |
| Previous Message | Amit Kapila | 2022-09-09 05:58:19 | Re: why can't a table be part of the same publication as its schema |