| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | Simon Riggs <simon(at)2ndquadrant(dot)com> |
| Cc: | Erik Rijkers <er(at)xs4all(dot)nl>, Sergei Kornilov <sk(at)zsrv(dot)org>, 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-11-06 21:16:33 |
| Message-ID: | eba539b8-9d15-a708-1702-c3271c30ad52@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 06/11/2018 14:28, Simon Riggs wrote:
> The simplest solution would be to exclude generated columns from the
> replication stream altogether.
>
>
> IMHO...
>
> Virtual generated columns need not be WAL-logged, or sent.
right
> Stored generated columns should be treated just like we'd treat a column
> value added by a trigger.
>
> e.g. if we had a Timestamp column called LastUpdateTimestamp we would
> want to send that value
Generated columns cannot have volatile expression results in them, so
this case cannot happen.
Also, we don't know whether the generation expression on the target is
the same (or even if it looks the same, consider locale issues etc.), so
we need to recompute the generated columns on the target anyway, so it's
pointless to send the already computed stored values.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jonah H. Harris | 2018-11-06 21:35:53 | Re: Disallow setting client_min_messages > ERROR? |
| Previous Message | Tom Lane | 2018-11-06 21:13:58 | Re: backend crash on DELETE, reproducible locally |