Re: [HACKERS] generated columns - Mailing list pgsql-hackers

From Nico Williams
Subject Re: [HACKERS] generated columns
Date
Msg-id 20171002181042.GI1251@localhost
Whole thread Raw
In response to Re: [HACKERS] generated columns  (Adam Brusselback <adambrusselback@gmail.com>)
Responses Re: [HACKERS] generated columns
List 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".


-- 
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: [HACKERS] list of credits for release notes
Next
From: Andrew Borodin
Date:
Subject: Re: [HACKERS] GSoC 2017 : Patch for predicate locking in Gist index