| From: | James Sewell <james(dot)sewell(at)lisasoft(dot)com> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Paul Ramsey <pramsey(at)cleverelephant(dot)ca>, David Rowley <david(dot)rowley(at)2ndquadrant(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Parallel Aggregate |
| Date: | 2016-03-14 23:52:36 |
| Message-ID: | CANkGpBtSeWy8vcqgCZ0s_at1dHmir0=XFCCB+4sPmHFuON_h4g@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Mar 15, 2016 at 9:32 AM, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
>
> I kind of doubt this would work well, but somebody could write a patch
> for it and try it out.
OK I'll give this a go today and report back.
Would the eventual plan be to use pg_proc.procost for the functions from
each aggregate concerned? If so I might have a peek at that too, although I
imagine I won't get far.
Cheers,
--
------------------------------
The contents of this email are confidential and may be subject to legal or
professional privilege and copyright. No representation is made that this
email is free of viruses or other defects. If you have received this
communication in error, you may not copy or distribute any part of it or
otherwise disclose its contents to anyone. Please advise the sender of your
incorrect receipt of this correspondence.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Rowley | 2016-03-14 23:56:29 | Re: Parallel Aggregate |
| Previous Message | Robert Haas | 2016-03-14 23:52:07 | Re: Explain [Analyze] produces parallel scan for select Into table statements. |