Re: ORDER BY pushdowns seem broken in postgres_fdw - Mailing list pgsql-hackers

From David Rowley
Subject Re: ORDER BY pushdowns seem broken in postgres_fdw
Date
Msg-id CAApHDvrOrvY3j3uMaa8hVCyAzNKZuDZK-2dNe3zm-u+VB=QGkw@mail.gmail.com
Whole thread Raw
In response to Re: ORDER BY pushdowns seem broken in postgres_fdw  (Ronan Dunklau <ronan.dunklau@aiven.io>)
Responses Re: ORDER BY pushdowns seem broken in postgres_fdw  (Ronan Dunklau <ronan.dunklau@aiven.io>)
List pgsql-hackers
On Thu, 22 Jul 2021 at 19:00, Ronan Dunklau <ronan.dunklau@aiven.io> wrote:
> Please find it reattached.

+-- This will not be pushed either
+explain verbose select * from ft2 order by c1 using operator(public.<^);
+                                  QUERY PLAN
+-------------------------------------------------------------------------------
+ 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.

History lesson: costs off was added so we could test plans. Before
that, I don't think that the regression tests had any coverage for
plans.  Older test files still likely lack much testing with EXPLAIN.

David



pgsql-hackers by date:

Previous
From: Ronan Dunklau
Date:
Subject: Re: postgres_fdw: Handle boolean comparison predicates
Next
From: Peter Eisentraut
Date:
Subject: Re: A (but copied many) typo of char-mapping tables