Re: Optimiser desicion bringing system to its knees? - Mailing list pgsql-general

From Tom Lane
Subject Re: Optimiser desicion bringing system to its knees?
Date
Msg-id 24501.1068167216@sss.pgh.pa.us
Whole thread Raw
In response to Optimiser desicion bringing system to its knees?  (Craig O'Shannessy <craig@ucw.com.au>)
Responses Re: Optimiser desicion bringing system to its knees?  ("Craig O'Shannessy" <craig@ucw.com.au>)
List pgsql-general
"Craig O'Shannessy" <craig@ucw.com.au> writes:
> The explains below make it clear I think.  If I just change the table
> declaration order, I get MASSIVELY better performance.

Hm.  Is the lineitem_sku_reservation_idx index a partial index, by any
chance?  I see this bug fix in 7.2.2:

2002-08-22 12:20  tgl

    * src/backend/optimizer/path/indxpath.c (REL7_2_STABLE): Back-patch
    fix to make partial indexes usable on relations other than the
    first one listed in a query.  Per request from Oleg.

            regards, tom lane

pgsql-general by date:

Previous
From: Martijn van Oosterhout
Date:
Subject: Re: int8 primary keys still not using index without manual JDBC driver patch (7.4RC1)
Next
From:
Date:
Subject: on connect trigger