Re: Queries are taking way longer in 9.6 than 9.5

From: Merlin Moncure <mmoncure(at)gmail(dot)com>
To: Ravi Tammineni <rtammineni(at)partner(dot)aligntech(dot)com>
Cc: Chris Mair <chris(at)1006(dot)org>, Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>
Subject: Re: Queries are taking way longer in 9.6 than 9.5
Date: 2017-01-18 20:06:15
Message-ID: CAHyXU0xSSy0C-oZ9KFWJ0SK0v7NNNqTZ0A1whguaDLAAKNEmxA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgadmin-support pgsql-admin pgsql-general

On Wed, Jan 18, 2017 at 1:04 PM, Ravi Tammineni
<rtammineni(at)partner(dot)aligntech(dot)com> wrote:
> Hi Chris,
>
> Here is the query and execution plan in 9.5 and 9.6.

Can you verify tblpuorderstatus and tblpuorderstatushistory have all
indexes accounted for on both servers? It seems incredible server
would prefer wading through 11M records to 1298 nestloop. I'm curious
what plans you get if you try playing around with:

set enable_seqscan=false;
set enable_hashjoin=false;

...but I think we have two possibilities here:
1. schema mismatch
2. planner bug

merlin

In response to

Responses

Browse pgadmin-support by date

  From Date Subject
Next Message Melvin Davidson 2017-01-18 20:12:03 Re: Queries are taking way longer in 9.6 than 9.5
Previous Message Ravi Tammineni 2017-01-18 19:04:18 Re: Queries are taking way longer in 9.6 than 9.5

Browse pgsql-admin by date

  From Date Subject
Next Message Melvin Davidson 2017-01-18 20:12:03 Re: Queries are taking way longer in 9.6 than 9.5
Previous Message Ferrell, Denise D CTR NSWCDD, H11 2017-01-18 20:01:16 PostgreSQL 9.3 ERROR

Browse pgsql-general by date

  From Date Subject
Next Message Melvin Davidson 2017-01-18 20:12:03 Re: Queries are taking way longer in 9.6 than 9.5
Previous Message PAWAN SHARMA 2017-01-18 19:17:20 migrate Sql Server database to PostgreSql