[Postgres-xl-general] Different query plans on different coordinators in same cluster
Mason Sharp
msharp at translattice.com
Fri Aug 29 10:47:58 PDT 2014
On Wed, Aug 27, 2014 at 9:46 AM, Dennis <dennisr at visi.com> wrote:
> Yep tried those things. Actually I have the same issue on a vanilla
> postgresql install with the same data regarding the query plans.
>
> What I am actually most concerned with now is that after running vacuum
> analyze against t_week_f on coordinator1 ALL queries are now degraded not
> just those involving t_week_f. The problem now seems to be (disregarding
> the slower query plan) that the REMOTE PLAN threads on coordinator1 are
> using 100% cpu and all queries timings have degraded to more than 10 to 20
> times slower in general.
>
> It looks like the REMOTE PLAN thread is thrashing and not completing
> correctly possibly.
>
>
So, if you set this in your session:
set enable_bitmapscan=off
You still get a slow plan, not a fast one? A different slow plan? What does
it look like?
Thanks,
Mason
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.postgres-xl.org/pipermail/postgres-xl-general-postgres-xl.org/attachments/20140829/937e53b9/attachment.htm>
More information about the postgres-xl-general
mailing list