| From: | Sergei Kornilov <sk(at)zsrv(dot)org> |
|---|---|
| To: | Simon Riggs <simon(at)2ndquadrant(dot)com>, Erik Rijkers <er(at)xs4all(dot)nl> |
| Cc: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, Jaime Casanova <jaime(dot)casanova(at)2ndquadrant(dot)com> |
| Subject: | Re: [HACKERS] generated columns |
| Date: | 2018-10-31 13:01:41 |
| Message-ID: | 39798611540990901@myt4-174696c9aa9d.qloud-c.yandex.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi
> OK, so the problem is COPY.
>
> Which means we have an issue with restore. We need to be able to pg_dump a table with generated columns, then restore it afterwards. More generally, we need to be able to handle data that has already been generated - the "generate" idea should apply to new data not existing data.
pg_dump was fixed in published patch (i check this yesterday). It does not COPY generated columns values, only non-generated.
regards, Sergei
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Amit Kapila | 2018-10-31 13:09:07 | Re: WIP: Avoid creation of the free space map for small tables |
| Previous Message | Simon Riggs | 2018-10-31 12:53:11 | Re: [HACKERS] generated columns |