From: | "Craig O'Shannessy" <craig(at)ucw(dot)com(dot)au> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Optimiser desicion bringing system to its knees? |
Date: | 2003-11-07 03:06:59 |
Message-ID: | Pine.LNX.4.44.0311071405410.14188-100000@mail.ucw.com.au |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | 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(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
>
From | Date | Subject | |
---|---|---|---|
Next Message | Keith C. Perry | 2003-11-07 03:07:54 | Re: on connect trigger? |
Previous Message | Christopher Kings-Lynne | 2003-11-07 02:32:54 | Re: pg_stat |