From: | David Rowley <dgrowleyml(at)gmail(dot)com> |
---|---|
To: | Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Amit Kapila <amit(dot)kapila(at)enterprisedb(dot)com> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Combining Aggregates |
Date: | 2015-03-04 09:41:12 |
Message-ID: | CAApHDvpbQN4js34VB_jYbwosTEeYbHiL-MerkcjrU-MaEMcTYA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 21 February 2015 at 07:16, Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com>
wrote:
>
> 2) serialize/deserialize functions
> ----------------------------------
>
> This thread mentions "parallel queries" as a use case, but that means
> passing data between processes, and that requires being able to
> serialize and deserialize the aggregate state somehow. For actual data
> types that's not overly difficult I guess (we can use in/out functions),
> but what about aggretates using 'internal' state? I.e. aggregates
> passing pointers that we can't serialize?
>
>
This is a good question. I really don't know the answer to it as I've not
looked at the Robert's API for passing data between backends yet.
Maybe Robert or Amit can answer this?
Regards
David Rowley
From | Date | Subject | |
---|---|---|---|
Next Message | Jeevan Chalke | 2015-03-04 09:43:40 | Re: How about to have relnamespace and relrole? |
Previous Message | David Rowley | 2015-03-04 09:37:19 | Re: Combining Aggregates |