Hi,
One reason the remote plans via FDW are different than the plans of queries
running directly on the remote server is that a cursor is used, which is
optimized for low number of rows according to cursor_tuple_fraction. Is there
any way to set parameters that affect the queries on the remote
On Sunday, 17 February 2019 20:58:47 EET Jeff Janes wrote:
> A question for the PostgreSQL hackers would be, Is it necessary and
> desirable that the EXPLAIN be issued in the same transaction as the
> eventual DECLARE and FETCHes? I don't think it is. I guess if the foreign
> side table
Related to this question:
Postgresql cursors are in most cases I've tried extremely slow. The cause is as
described in my previous answer, in my experience. Is there any plan or way to
improve this situation? For example, for FDW one would expect the plan on the
remote side to be similar, if
Hi,
We'd like to configure an RDS server for shared hosting. The idea is that every
customer will be using a different database and FDW will be configured, so that
the remote tables have access to the full data, but materialized views will be
pulling from them data specific to each customer.
