From: | Nico Williams <nico(at)cryptonector(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
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:46:42 |
Message-ID: | 20171002184641.GJ1251@localhost |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Mon, Oct 02, 2017 at 02:30:38PM -0400, Tom Lane wrote:
> 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?
Aha, thanks! Yes, that would be noticeable.
Nico
--
From | Date | Subject | |
---|---|---|---|
Next Message | Alexander Korotkov | 2017-10-02 19:02:26 | Re: GSoC 2017 : Patch for predicate locking in Gist index |
Previous Message | David Fetter | 2017-10-02 18:36:41 | Re: generated columns |