From: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
To: Heikki Linnakangas <hlinnaka@iki.fi>
Cc: David Rowley <david.rowley@2ndquadrant.com>
Cc: pgsql-hackers@postgresql.org
Subject: Re: [HACKERS] Aggregate transition state merging vs. hypothetical set functions
Date: Mon, 21 May 2018 10:14:58 -0400
Message-ID: <d2e1afd4-659c-50d6-1b20-7cfd3675e909@2ndquadrant.com> (raw)
In-Reply-To: <7410.1507935678@sss.pgh.pa.us>
References: <4834.1507849699@sss.pgh.pa.us>
<58219c24-ed31-3a3d-db28-ace9390973c5@iki.fi>
<5691.1507903523@sss.pgh.pa.us>
<7410.1507935678@sss.pgh.pa.us>
On 10/13/17 19:01, Tom Lane wrote:
>> Moving on to the exact color of the bikeshed: it seems like the right
>> way to present this to users of CREATE AGGREGATE is in terms of "does
>> the final function modify the transition state?". So maybe the values
>> could be spelled
>> SMODIFY = READ_ONLY ffunc never touches state, ok as window agg
>> SMODIFY = SHARABLE ffunc does some one-time change like sorting,
>> so state merging is OK but not window agg
>> SMODIFY = READ_WRITE ffunc trashes state, can't do merging either
>> I'm not set on these names by any means; anyone have a better idea?
Is "sharable" the preferred spelling, as opposed to "shareable"?
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
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 from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-hackers@postgresql.org
Cc: peter.eisentraut@2ndquadrant.com, tgl@sss.pgh.pa.us, hlinnaka@iki.fi, david.rowley@2ndquadrant.com
Subject: Re: [HACKERS] Aggregate transition state merging vs. hypothetical set functions
In-Reply-To: <d2e1afd4-659c-50d6-1b20-7cfd3675e909@2ndquadrant.com>
References: <4834.1507849699@sss.pgh.pa.us> <58219c24-ed31-3a3d-db28-ace9390973c5@iki.fi> <5691.1507903523@sss.pgh.pa.us> <7410.1507935678@sss.pgh.pa.us> <d2e1afd4-659c-50d6-1b20-7cfd3675e909@2ndquadrant.com>
* 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