| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Dumping/restoring fails on inherited generated column |
| Date: | 2020-02-03 18:58:43 |
| Message-ID: | d6ebcc2e-3e6f-6915-6616-70ef665aed66@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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.)
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| Attachment | Content-Type | Size |
|---|---|---|
| v2-0001-Fix-dumping-of-inherited-generated-columns.patch | text/plain | 1004 bytes |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2020-02-03 19:32:41 | Re: Dumping/restoring fails on inherited generated column |
| Previous Message | Jeff Davis | 2020-02-03 18:29:55 | Re: Memory-Bounded Hash Aggregation |