Skip site navigation (1) Skip section navigation (2)

Re: reducing random_page_cost from 4 to 2 to force index scan

From: Josh Berkus <josh(at)agliodbs(dot)com>
To: pgsql-performance(at)postgresql(dot)org
Subject: Re: reducing random_page_cost from 4 to 2 to force index scan
Date: 2011-05-23 19:08:07
Message-ID: 4DDAB097.9070505@agliodbs.com (view raw or flat)
Thread:
Lists: pgsql-performance
> Well, all of that stuff sounds impractically expensive to me... but I
> just work here.

I'll point out that the simple version, which just checks for hot tables
and indexes, would improve estimates greatly and be a LOT less
complicated than these proposals.  Certainly having some form of
block-based or range-based stats would be better, but it also sounds
hard enough to maybe never get done.

Having user-accessible "hot" stats would also be useful to DBAs.

-- 
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com

In response to

Responses

pgsql-performance by date

Next:From: Robert HaasDate: 2011-05-23 19:08:16
Subject: Re: Performance degradation of inserts when database size grows
Previous:From: Robert HaasDate: 2011-05-23 19:05:44
Subject: Re: Performance degradation of inserts when database size grows

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group