| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Nico Williams <nico(at)cryptonector(dot)com> |
| Cc: | Adam Brusselback <adambrusselback(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: generated columns |
| Date: | 2017-10-02 18:30:38 |
| Message-ID: | 10550.1506969038@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Nico Williams <nico(at)cryptonector(dot)com> writes:
> On Mon, Oct 02, 2017 at 12:50:14PM -0400, Adam Brusselback wrote:
>> So for me, i'd rather default to compute on read, as long storing the
>> pre-computed value is an option when necessary.
> Sure, I agree. I was just wondering whether there might be any other
> difference besides performance characteristics. The answer to that is,
> I think, "no".
What about non-immutable functions in the generation expression?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Fetter | 2017-10-02 18:36:41 | Re: generated columns |
| Previous Message | Tom Lane | 2017-10-02 18:23:35 | Re: Horrible CREATE DATABASE Performance in High Sierra |