| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Merlin Moncure <mmoncure(at)gmail(dot)com> |
| Cc: | Alexander Reshetov <alexander(dot)v(dot)reshetov(at)gmail(dot)com>, PostgreSQL General <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Missed LIMIT clause pushdown in FDW API |
| Date: | 2016-03-30 13:33:03 |
| Message-ID: | 31924.1459344783@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Merlin Moncure <mmoncure(at)gmail(dot)com> writes:
> On Wed, Mar 30, 2016 at 3:52 AM, Alexander Reshetov
> <alexander(dot)v(dot)reshetov(at)gmail(dot)com> wrote:
>> As far as I know there is no LIMIT clause pushdown in FDW API.
>> Is there some reasons not to support LIMIT clause pushdown?
It was impossible to do it before 3fc6e2d7f5b652b4, committed 3 weeks
ago. Now that that infrastructure exists, someone might look into
using it for this purpose ... but not before 9.7 at the earliest.
> Working for me on 9.5 with postgres_fdw...
Really? It's true that postgres_fdw won't fetch more rows than it
actually needs from the remote --- but that's not the same as telling
the remote planner to prefer a fast-start plan.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Amit Langote | 2016-03-30 13:51:44 | Re: pg_restore casts check constraints differently |
| Previous Message | Pavlov, Vladimir | 2016-03-30 13:24:19 | Re: Multixacts wraparound monitoring |