Re: [External] Re: FDW, too long to run explain - Mailing list pgsql-general

From Jeff Janes
Subject Re: [External] Re: FDW, too long to run explain
Date
Msg-id CAMkU=1zCLHtUpwso8Xt2ZS9EtCY2KzkU8qdNfySdKpt_Q9BtaA@mail.gmail.com
Whole thread Raw
In response to Re: [External] Re: FDW, too long to run explain  (Vijaykumar Jain <vjain@opentable.com>)
Responses Re: [External] Re: FDW, too long to run explain  (Vijaykumar Jain <vjain@opentable.com>)
List pgsql-general
On Sun, Feb 17, 2019 at 6:32 AM Vijaykumar Jain <vjain@opentable.com> wrote:
I am yet to figure out the reason, what we have done is implement fake columns to represent samples and giving them random numbers and keeping other bulls to fake limit.

Most of the queries that were impacted were the ones that did not push order by and limit to foreign servers.
I am also trying to upgrade pg11 to make use of parallelisation.

postgres_fdw operates through declared cursors, and declared cursors inhibit parallel query.  This doesn't change in v11, see https://www.postgresql.org/docs/11/when-can-parallel-query-be-used.html

I'm not aware of any other changes in v11 that are likely to help you out.

Cheers,

Jeff

pgsql-general by date:

Previous
From: Vijaykumar Jain
Date:
Subject: Re: [External] Re: FDW, too long to run explain
Next
From: legrand legrand
Date:
Subject: pg_stat_statements doesn't track commit from pl/pgsql blocks