| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Ronan Dunklau <ronan(dot)dunklau(at)dalibo(dot)com> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, David Rowley <dgrowleyml(at)gmail(dot)com>, Andres Freund <andres(at)2ndquadrant(dot)com>, Christoph Berg <cb(at)df7cb(dot)de>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>, Markus Wanner <markus(at)bluegap(dot)ch> |
| Subject: | Re: Hide 'Execution time' in EXPLAIN (COSTS OFF) |
| Date: | 2014-10-16 16:19:58 |
| Message-ID: | 6378.1413476398@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Ronan Dunklau <ronan(dot)dunklau(at)dalibo(dot)com> writes:
> From my point of view as a FDW implementor, the feature I need is to have
> EXPLAIN (COSTS ON) with stable output for foreign scan nodes.
Well, as long as the FDW's costing is exactly predictable, you can have
that ...
> In the Multicorn FDW (Python API on top of the C-API), we introduced this
> commit to make the tests pass on 9.4:
> https://github.com/Kozea/Multicorn/commit/76decb360b822b57bf322892ed6c504ba44a8b28
> Clearly, we've lost the ability to test that the costs as set from the Python
> API are indeed used.
We did fix that yesterday. The remaining argument is about whether it's
practical to get platform-independent output out of EXPLAIN ANALYZE.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ryan Johnson | 2014-10-16 16:26:10 | Re: WIP: dynahash replacement for buffer table |
| Previous Message | Stephen Frost | 2014-10-16 16:01:28 | Re: Directory/File Access Permissions for COPY and Generic File Access Functions |