| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Douglas Doole <dougdoole(at)gmail(dot)com> |
| Cc: | Konstantin Knizhnik <k(dot)knizhnik(at)postgrespro(dot)ru>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [PATCH] Push limit to sort through a subquery |
| Date: | 2017-08-24 02:43:41 |
| Message-ID: | CA+TgmoYa3QKKrLj5rX7UvGqhH73G1Li4B-EKxrmASaca2tFu9Q@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Aug 23, 2017 at 6:55 PM, Douglas Doole <dougdoole(at)gmail(dot)com> wrote:
> From previous experience, pushing the limit to the workers has the potential
> to be a big win .
Here's a not-really-tested draft patch for that.
> I haven't played with parallel mode at all yet. Is it possible to disable
> force_parallel_mode for the new test?
Yeah, I suppose that's another alternative.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| Attachment | Content-Type | Size |
|---|---|---|
| push-down-bound-to-workers.patch | application/octet-stream | 15.6 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Masahiko Sawada | 2017-08-24 03:38:10 | Combination with priority-based and quorum-based synchronous replications |
| Previous Message | Fabien COELHO | 2017-08-24 02:39:03 | Re: [WIP] Zipfian distribution in pgbench |