Foreign table scan estimates

While playing around with ANALYZE on foreign tables, I noticed
that the row count estimate for foreign scans is still
initialized to 1000 even if there are statistics for the
foreign table.  I think that this should be improved.

The attached patch illustrates my suggestion.

BTW, ist there any other place where foreign table statistics
should or do enter the planning process?

Yours,
Laurenz Albe