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

From Craig O'Shannessy
Subject Re: Optimiser desicion bringing system to its knees?
Date
Msg-id Pine.LNX.4.44.0311071405410.14188-100000@mail.ucw.com.au
Whole thread Raw
In response to Re: Optimiser desicion bringing system to its knees?  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-general
Ahh, this makes sense.

I've recently changed this into a partial index because I was getting
awful performance on it.

Thanks Tom, this gives me a stopgap fix until I can get 7.4 into
production.

Craig

On Thu, 6 Nov 2003, Tom Lane wrote:

> "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:
Date:
Subject: Re: Sequences without blank holes
Next
From: "Keith C. Perry"
Date:
Subject: Re: on connect trigger?