From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Steve <cheetah(at)tanabi(dot)org> |
Cc: | Scott Marlowe <smarlowe(at)g2switchworks(dot)com>, PostgreSQL Performance <pgsql-performance(at)postgresql(dot)org> |
Subject: | Re: Strangely Variable Query Performance |
Date: | 2007-04-13 03:49:54 |
Message-ID: | 12360.1176436194@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-patches pgsql-performance |
Steve <cheetah(at)tanabi(dot)org> writes:
> Just dropping that index had no effect, but there's a LOT of indexes that
> refer to receipt. So on a hunch I tried dropping all indexes that refer
> to receipt date and that worked -- so it's the indexes that contain
> receipt date that are teh problem.
I'm still not having any luck reproducing the failure here. Grasping at
straws again, I wonder if it's got something to do with the order in
which the planner examines the indexes --- which is OID order. Could
you send me the results of
select indexrelid::regclass from pg_index where indrelid = 'detail_summary'::regclass order by indexrelid;
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Steve | 2007-04-13 03:55:00 | Re: Strangely Variable Query Performance |
Previous Message | Greg Smith | 2007-04-13 03:29:56 | Re: Benchmarking tools for the Postgres, EDB and Oracle Database |
From | Date | Subject | |
---|---|---|---|
Next Message | Steve | 2007-04-13 03:55:00 | Re: Strangely Variable Query Performance |
Previous Message | Tom Lane | 2007-04-13 02:40:14 | Re: Strangely Variable Query Performance |
From | Date | Subject | |
---|---|---|---|
Next Message | Steve | 2007-04-13 03:55:00 | Re: Strangely Variable Query Performance |
Previous Message | Greg Smith | 2007-04-13 02:50:08 | Re: Question about memory allocations |