On Tue, Oct 5, 2010 at 10:25 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Shigeru HANADA <hanada@metrosystems.co.jp> writes:
>> Can we treat statistics of a foreign table separately?
>
>> 1. Same as local tables (maybe required)
>> (pg_statistic.*, pg_class.reltuples/relpages)
>
> This whole discussion seems to me to be about trying to do things outside
> the FDW that should properly be left inside the FDW. Who's to say that
> the remote side even *has* statistics of the sort that PG creates?
>
> We should provide an API that lets the FDW return a cost estimate for a
> proposed access path. Where it gets the cost estimate from is not
> something that should be presupposed.
Unless there's some way for the FDW to have local tables for caching
its statistics, the chances of this having decent performance seem to
be near-zero.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise Postgres Company