| From: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com> |
|---|---|
| To: | Vijaykumar Jain <vjain(at)opentable(dot)com> |
| Cc: | auxsvr <auxsvr(at)gmail(dot)com>, pgsql-general(at)lists(dot)postgresql(dot)org |
| Subject: | Re: [External] Re: FDW, too long to run explain |
| Date: | 2019-02-17 21:36:44 |
| Message-ID: | CAMkU=1zCLHtUpwso8Xt2ZS9EtCY2KzkU8qdNfySdKpt_Q9BtaA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Sun, Feb 17, 2019 at 6:32 AM Vijaykumar Jain <vjain(at)opentable(dot)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
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | legrand legrand | 2019-02-17 21:52:07 | pg_stat_statements doesn't track commit from pl/pgsql blocks |
| Previous Message | Vijaykumar Jain | 2019-02-17 21:14:44 | Re: [External] Re: FDW, too long to run explain |