| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | ewaldo(at)healthetechs(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: BUG #16342: CREATE TABLE LIKE INCLUDING GENERATED column order issue |
| Date: | 2020-04-09 14:48:29 |
| Message-ID: | dff50573-9092-4ad0-8fb6-a1f01e736f13@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On 2020-04-05 17:26, Tom Lane wrote:
> Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> writes:
>> Confirmed. Attached is a patch to fix it. Thanks for the report!
>
> LGTM. Perhaps extend the comment block just above, adding something
> like "We must fill the attmap now so it can be used to process
> GENERATED default expressions in the per-column loop."
Committed with that.
Ethan, this will be in the next minor release of PostgreSQL 12.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ethan Waldo | 2020-04-09 14:55:25 | RE: BUG #16342: CREATE TABLE LIKE INCLUDING GENERATED column order issue |
| Previous Message | hubert depesz lubaczewski | 2020-04-09 14:08:36 | Loss of replication after simple misconfiguration |