| From: | Michael Paquier <michael(at)paquier(dot)xyz> |
|---|---|
| To: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
| Cc: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, Jaime Casanova <jaime(dot)casanova(at)2ndquadrant(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [HACKERS] generated columns |
| Date: | 2018-02-11 14:10:53 |
| Message-ID: | 20180211141053.GA11084@paquier.xyz |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Feb 01, 2018 at 09:29:09AM -0500, Peter Eisentraut wrote:
> That would be nice. I'm going to study this some more to see what can
> be done.
By the way, cannot we consider just doing stored generated columns as a
first cut? Both virtual and stored columns have their use cases, but
stored values have less complication and support actually a larger set
of features, including rowtypes, index and constraint support. So it
seems to me that if something goes into v11 then stored columns would be
a better choice at this stage of the development cycle. Other DBMSs
support stored values by default as well, and your v1 patch had a large
portion of the work done if I recall correctly.
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Merlin Moncure | 2018-02-11 15:00:24 | Re: JIT compiling with LLVM v9.0 |
| Previous Message | Nikolay Shaplov | 2018-02-11 13:51:49 | Re: [PATCH][PROPOSAL] Add enum releation option type |