From: | Shaun Thomas <sthomas(at)optionshouse(dot)com> |
---|---|
To: | 'Jeff Janes' <jeff(dot)janes(at)gmail(dot)com> |
Cc: | "pgsql-performance(at)postgresql(dot)org" <pgsql-performance(at)postgresql(dot)org> |
Subject: | Re: Loose Index Scans by Planner? |
Date: | 2012-08-25 14:39:11 |
Message-ID: | 0683F5F5A5C7FE419A752A034B4A0B97221FFA51@sswchi5pmbx2.peak6.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-performance |
> Not always. The case for having (col1,col2) might be very
> compelling.
True. But in our case, the table has like 8M rows, so and col1 is some kind of job identifier, so it's evenly distributed. Col2 on the other hand is a customer id, so it has much higher cardinality. Previous DBA missed it during creation, and it was never loud enough in the logs for me to notice it until recently. Looks like I need to do a column-ordering audit. :)
> If only someone else would offer to do it for me....
Don't look at me. My C is rustier than a 50-year-old bike chain. :)
______________________________________________
See http://www.peak6.com/email_disclaimer/ for terms and conditions related to this email
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2012-08-25 16:20:57 | Re: [v9.3] writable foreign tables |
Previous Message | Amit kapila | 2012-08-25 11:46:11 | Re: [WIP] Performance Improvement by reducing WAL for Update Operation |
From | Date | Subject | |
---|---|---|---|
Next Message | Felix Schubert | 2012-08-25 21:26:11 | Re: Slow Performance on a XEON E5504 |
Previous Message | Scott Marlowe | 2012-08-25 13:04:51 | Re: Slow Performance on a XEON E5504 |