Re: ORDER BY pushdowns seem broken in postgres_fdw

From: Ronan Dunklau <ronan(dot)dunklau(at)aiven(dot)io>
To: David Rowley <dgrowleyml(at)gmail(dot)com>
Cc: Ranier Vilela <ranier(dot)vf(at)gmail(dot)com>, PostgreSQL Developers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Robert Haas <robertmhaas(at)gmail(dot)com>, Jeevan Chalke <jeevan(dot)chalke(at)enterprisedb(dot)com>, Ashutosh Bapat <ashutosh(dot)bapat(dot)oss(at)gmail(dot)com>
Subject: Re: ORDER BY pushdowns seem broken in postgres_fdw
Date: 2021-07-22 08:49:14
Message-ID: 4594273.tikkMDN7uQ@aivenronan
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers

Le jeudi 22 juillet 2021, 09:44:54 CEST David Rowley a écrit :
> +-- This will not be pushed either
> +explain verbose select * from ft2 order by c1 using operator(public.<^);
> +---------------------------------------------------------------------------
> ---- + Sort (cost=190.83..193.33 rows=1000 width=142)
> Can you also use explain (verbose, costs off) the same as the other
> tests in that area. Having the costs there would never survive a run
> of the buildfarm. Different hardware will produce different costs, e.g
> 32-bit hardware might cost cheaper due to narrower widths.

Sorry about that. Here it is.


Ronan Dunklau

Attachment Content-Type Size
v5_fix_postgresfdw_orderby_handling.patch text/x-patch 16.1 KB

In response to


Browse pgsql-hackers by date

  From Date Subject
Next Message Ranier Vilela 2021-07-22 09:00:15 Re: ORDER BY pushdowns seem broken in postgres_fdw
Previous Message Ronan Dunklau 2021-07-22 08:42:49 Re: Add proper planner support for ORDER BY / DISTINCT aggregates