| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Douglas Doole <dougdoole(at)gmail(dot)com>, 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 15:47:25 |
| Message-ID: | 17392.1503589645@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> 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.
Both this patch and the already-committed one contain useless (and not
very cheap) expression_returns_set tests. Since commit 69f4b9c85,
SRFs could only appear in the tlist of ProjectSet nodes.
No opinion on whether this patch is right otherwise.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2017-08-24 16:41:23 | Re: [PATCH] Push limit to sort through a subquery |
| Previous Message | Pavel Stehule | 2017-08-24 15:30:49 | Re: proposal: psql command \graw |