Re: Optimiser desicion bringing system to its knees?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Craig O'Shannessy" <craig(at)ucw(dot)com(dot)au>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Optimiser desicion bringing system to its knees?
Date: 2003-11-07 01:06:56
Message-ID: 24501.1068167216@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

"Craig O'Shannessy" <craig(at)ucw(dot)com(dot)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

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message btober 2003-11-07 01:27:55 on connect trigger?
Previous Message Martijn van Oosterhout 2003-11-07 00:45:01 Re: int8 primary keys still not using index without manual JDBC driver patch (7.4RC1)