On Tue, Jan 31, 2017 at 2:25 AM, Etsuro Fujita <fujita.ets...@lab.ntt.co.jp>

> On 2017/01/31 18:24, Abbas Butt wrote:
>> Postgres_fdw optimizes remote queries by pushing down the where clause.
>> This feature does not work consistently when the query is executed from
>> within a pl/pgsql function. The optimization works when the function
>> executes the query for the first 5 times, and fails afterwards.
> I understand that this is because PostgreSQL starts using generic plan
>> with pulled up where clause after the 5th invocation hoping that it
>> would be faster since we have skiped planning the query on each
>> invocation, but in this case this decision is causing the query to slow
>> down.
>> How should we fix this problem?
> ANALYZE for the foreign table doesn't work?


analyze ts.tickets;
WARNING:  skipping "tickets" --- cannot analyze this foreign table

> Best regards,
> Etsuro Fujita


Ph: 92.334.5100153
Skype ID: gabbasb
www.enterprisedb.co <http://www.enterprisedb.com/>m

*Follow us on Twitter*

Visit EnterpriseDB for tutorials, webinars, whitepapers
<http://www.enterprisedb.com/resources-community> and more

Reply via email to