Re: [HACKERS] Aggregate transition state merging vs. hypothetical setfunctions - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: [HACKERS] Aggregate transition state merging vs. hypothetical setfunctions
Date
Msg-id d2e1afd4-659c-50d6-1b20-7cfd3675e909@2ndquadrant.com
Whole thread Raw
In response to Re: [HACKERS] Aggregate transition state merging vs. hypothetical set functions  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: [HACKERS] Aggregate transition state merging vs. hypothetical set functions  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
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


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: PostgreSQL: PY3 files in PY2 installation
Next
From: Tom Lane
Date:
Subject: Re: [HACKERS] Aggregate transition state merging vs. hypothetical set functions