[prev in list] [next in list] [prev in thread] [next in thread] 

List:       pgsql-performance
Subject:    Re: [PERFORM] Slow query after upgrade from 9.0 to 9.2
From:       Jeff Janes <jeff.janes () gmail ! com>
Date:       2013-01-11 17:12:16
Message-ID: CAMkU=1z0iabTNxVHKRbW5oKW+gcCac+O9x4OpETa_ygRdqomkA () mail ! gmail ! com
[Download RAW message or body]

On Fri, Jan 11, 2013 at 12:13 AM, Andrzej Zawadzki <zawadaa@wp.pl> wrote:
> On 10.01.2013 19:17, Jeff Janes wrote:

>> Also, if you temporarily set enable_seqscan=off on 9.2, what plan do
>> you then get?
>
> Plan is different.
>

> "                Join Filter: (sa.arrear_import_id = ai.id)"

It is hard to imagine why it is not using
sygma_arrear_arrear_import_id_idx for this given the plan is now
accessing the index anyway.  Have the types or encodings or collations
somehow become incompatible so that this index can no longer fulfill
it?

What if you just write a very simple join between the two tables with
the above join condition, with another highly selective condition on
ai?

Cheers,

Jeff


-- 
Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-performance
[prev in list] [next in list] [prev in thread] [next in thread]