| From: | Nico Williams <nico(at)cryptonector(dot)com> |
|---|---|
| To: | Adam Brusselback <adambrusselback(at)gmail(dot)com> |
| Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: generated columns |
| Date: | 2017-10-02 18:10:43 |
| Message-ID: | 20171002181042.GI1251@localhost |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Oct 02, 2017 at 12:50:14PM -0400, Adam Brusselback wrote:
> I know that for my use-cases, having both options available would be very
> appreciated. The vast majority of the computed columns I would use in my
> database would be okay to compute on read. But there are for sure some
> which would be performance prohibitive to have compute on read, so i'd
> rather have those stored.
>
> 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".
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Borodin | 2017-10-02 18:11:55 | Re: GSoC 2017 : Patch for predicate locking in Gist index |
| Previous Message | Bruce Momjian | 2017-10-02 17:55:52 | Re: list of credits for release notes |