On 02/24/2011 12:13 PM, Greg Smith wrote:
> That's not quite the right filter. You want to screen out
> everything that isn't a unique index, not just the primary key ones.
> You probably can't drop any of those without impacting database
Ah yes. I was considering adding the clause for unique indexes. Filthy
> Also, as a picky point, you really should use functions like
> pg_relation_size instead of doing math on relpages.
You know, I always think about that, but I'm essentially lazy. :) I
personally haven't ever had the old *8 trick fail, but from your
perspective of working with so many variations, I could see how you'd
want to avoid it.
I'll be good from now on. ;)
OptionsHouse | 141 W. Jackson Blvd. | Suite 800 | Chicago IL, 60604
for terms and conditions related to this email
In response to
pgsql-performance by date
|Next:||From: Dave Crooke||Date: 2011-02-24 19:55:31|
|Subject: Picking out the most recent row using a time stamp column|
|Previous:||From: Vik Reykja||Date: 2011-02-24 19:33:00|
|Subject: Re: Pushing IN (subquery) down through UNION ALL?|