pg.ddx.io pgsql-hackers@postgresql.org mailing list archive
help / color / mirror / Atom feed From: Tomas Vondra <tomas.vondra@2ndquadrant.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: David Rowley <david.rowley@2ndquadrant.com>
Cc: Stephen Frost <sfrost@snowman.net>
Cc: Andres Freund <andres@anarazel.de>
Cc: PostgreSQL-development <pgsql-hackers@postgresql.org>
Subject: Re: Parallel Aggregates for string_agg and array_agg
Date: Wed, 28 Mar 2018 16:05:05 +0200
Message-ID: <1ffa699d-ff84-4c21-10cb-4d8b36017bab@2ndquadrant.com> (raw )
In-Reply-To: <18741.1522245278@sss.pgh.pa.us >
References: <CAKJS1f8cB3cc5AK=wPvByhU_jKkgd81iRt2kE6cru8uxx2HCuA@mail.gmail.com >
<24abe018-b3c6-2117-b5b9-39e660db00bd@2ndquadrant.com >
<CAKJS1f8LV7AT=AAhdYGKtGrGkSkEgO6C_SW2Ztz1sR3encisqw@mail.gmail.com >
<1b6ee15c-c218-761e-0120-c1ed438e2db2@2ndquadrant.com >
<657be73a-a21d-0ae1-5c62-870afbdfddd4@2ndquadrant.com >
<CAKJS1f-bKAD+s-CJetRQPjmrR-gF-kfvwfzhQm-A0PA-nsr1xw@mail.gmail.com >
<20180326022647.GL24540@tamriel.snowman.net >
<CAKJS1f-axkksX3XzduLJuTL=o8CSwf1NaQYO6=iHSXR_B3pCKQ@mail.gmail.com >
<20180326132009.GN24540@tamriel.snowman.net >
<CAKJS1f8JVpUUkYP2c+RyVRdpS1dnjB_DA5fbcDSL3qfMRqc81Q@mail.gmail.com >
<6538.1522096067@sss.pgh.pa.us >
<25812.1522108164@sss.pgh.pa.us >
<CAKJS1f87rFqL0=ksfs+3mmQvg_R0RRGEXyayxHkwYnFqeKpngQ@mail.gmail.com >
<CAKJS1f9oTWG4oc7B2WfDhT11KhxeV1miLQ+PzB6hY=iJeHM28A@mail.gmail.com >
<452e8b7f-418b-4e61-c212-c0e4410b94ad@2ndquadrant.! com >
<19216.1522207699@sss.pgh.pa.us >
<f1fc0953-93a9-! 41f3-ecd4-dbc0acd63f23@2ndquadrant.com >
<18741.1522245278@sss.pgh.pa.us >
On 03/28/2018 03:54 PM, Tom Lane wrote:
> Tomas Vondra <tomas.vondra@2ndquadrant.com> writes:
>> On 03/28/2018 05:28 AM, Tom Lane wrote:
>>> Getting a solution that would work for other polymorphic serialization
>>> functions seems like a bit of a research project to me. In the meantime,
>>> I think David's right that what we need to look at is the actual input
>>> type of the aggregate, and then assume that what's to be serialized is
>>> an array of that. Conceivably an aggregate could be built that uses
>>> these serial/deserial functions and yet its input type is something else
>>> than what it constructs an array of ... but I find it a bit hard to
>>> wrap my brain around what that would be exactly.
>
>> But David's fix doesn't check the aggregate to produce an array of the
>> input type (or anyarray). It could easily be an aggregate computing a
>> bloom filter or something like that, which has no such issues in the
>> serial/deserial functions.
>
> Oh, if he's not restricting it to these serialization functions, I
> agree that seems wrong. I thought the discussion was about what to
> do after checking the functions.
>
Nope, David's patch does not check what the serial/deserial functions
are (and checks aggref->aggargtypes directly, not the exprType thing).
>> Also, if it's checking aggref->aggargtypes, it'll reject anyelement
>> parameters, no?
>
> I had in mind to look at exprType() of the argument.
>
Right, I'm fine with that.
regards
--
Tomas Vondra http://www.2ndQuadrant.com
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
view thread (77+ messages) latest in thread
Message-ID: <1ffa699d-ff84-4c21-10cb-4d8b36017bab@2ndquadrant.com>
Permalink: ../1ffa699d-ff84-4c21-10cb-4d8b36017bab@2ndquadrant.com/
Also on: postgresql.org/message-id/1ffa699d-ff84-4c21-10cb-4d8b36017bab@2ndquadrant.com
copy link · copy postgr.es
reply 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: tomas.vondra@2ndquadrant.com, tgl@sss.pgh.pa.us, david.rowley@2ndquadrant.com, sfrost@snowman.net, andres@anarazel.de
Subject: Re: Parallel Aggregates for string_agg and array_agg
In-Reply-To: <1ffa699d-ff84-4c21-10cb-4d8b36017bab@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