From: Nico Williams <nico@cryptonector.com>
To: Adam Brusselback <adambrusselback@gmail.com>
Cc: pgsql-hackers <pgsql-hackers@postgresql.org>
Subject: Re: generated columns
Date: Mon, 2 Oct 2017 13:10:43 -0500
Message-ID: <20171002181042.GI1251@localhost> (raw)
In-Reply-To: <CAMjNa7fhskTTMSLMUL=e1r-EOg2Q3-cSayEDB1MADmX_zzn1gw@mail.gmail.com>
References: <b151f851-4019-bdb1-699e-ebab07d2f40a@2ndquadrant.com>
<20171002152338.GH1251@localhost>
<CAMjNa7fhskTTMSLMUL=e1r-EOg2Q3-cSayEDB1MADmX_zzn1gw@mail.gmail.com>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: nico@cryptonector.com, adambrusselback@gmail.com
Subject: Re: generated columns
In-Reply-To: <20171002181042.GI1251@localhost>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox