| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Simon Riggs <simon(at)2ndquadrant(dot)com> |
| Cc: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: generated columns |
| Date: | 2017-09-14 00:15:13 |
| Message-ID: | CA+Tgmobe2CiJ3xHuaGgvv43nZVyR3oyQ6tx_r3nSYsdZMirzMQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Sep 12, 2017 at 10:04 PM, Simon Riggs <simon(at)2ndquadrant(dot)com> wrote:
> I think an option to decide whether the default is STORED or VIRTUAL
> would be useful.
That seems like it could be a bit of a foot-gun. For example, an
extension author who uses generated columns will have to be careful to
always specify one or the other, because they don't know what the
default will be on the system where it's deployed. Similarly for an
author of a portable application. I think it'll create fewer
headaches if we just pick a default and stick with it.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2017-09-14 00:16:49 | Re: Is it time to kill support for very old servers? |
| Previous Message | Thomas Munro | 2017-09-13 23:57:32 | Re: Parallel Hash take II |