| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Masahiko Sawada <masahiko(dot)sawada(at)2ndquadrant(dot)com> |
| Cc: | Daniel Gustafsson <daniel(at)yesql(dot)se>, andrewbille(at)gmail(dot)com, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Dumping/restoring fails on inherited generated column |
| Date: | 2020-10-02 17:07:04 |
| Message-ID: | d692cdbb-7072-c642-d4f4-9c37102211ce@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2020-09-29 18:37, Tom Lane wrote:
> Unfortunately this has still got a problem: it will mishandle the case of
> a child column that is GENERATED while its parent is not. Peter opined
> way upthread that we should not allow that, but according to my testing
> we do.
Did I opine that? Commit 086ffddf3656fb3d24d9a73ce36cb1102e42cc90
explicitly allowed that case. What we don't want is the other way around.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Mark Wong | 2020-10-02 17:45:58 | Re: buildfarm animal shoveler failing with "Illegal instruction" |
| Previous Message | Tom Lane | 2020-10-02 16:07:58 | Re: Rejecting redundant options in Create Collation |