pg.ddx.io pgsql-performance@postgresql.org mailing list archive
help / color / mirror / Atom feed From: Josh Berkus <josh@agliodbs.com>
To: pgsql-performance@postgresql.org
Subject: Re: reducing random_page_cost from 4 to 2 to force index scan
Date: Mon, 23 May 2011 12:08:07 -0700
Message-ID: <4DDAB097.9070505@agliodbs.com> (raw )
In-Reply-To: <BANLkTik0FgfvNvhXC6+AW0jTrGq5RUbFLw@mail.gmail.com >
References: <BANLkTikZhYc+h1=YDJfXwZEZc1tN3_VwCg@mail.gmail.com >
<4DB6F4BB020000250003CEB9@gw.wicourts.gov >
<BANLkTindB68ogMg8zrR7GrYEV+mQQddj0A@mail.gmail.com >
<BANLkTik6OaVkJGEjs5--vcynUE36mWbzbg@mail.gmail.com >
<2823.1305314437@sss.pgh.pa.us >
<BANLkTimTqXAy7_KqQz_OW1RvMbDd9ojfqg@mail.gmail.com >
<4DCD90F5.2010501@agliodbs.com >
<BANLkTikcVUeRfocJPe_W+jfi5k1+gcLnxg@mail.gmail.com >
<4DD0195A.9040305@agliodbs.com >
<BANLkTika=a95=Pm97Evi-Q7e_9vs4FnkCQ@mail.gmail.com >
<4DD07855.8080907@postnewspapers.com.au >
<4DD07B4E.1020503@2ndquadrant.com >
<4DD0AB16.5060808@krogh.cc >
<4DD0ACD0.1090801@krogh.cc >
<BANLkTikTWeZxWQFxM1SJg=0=OtCkCX_-dA@mail.gmail.com >
<16676.1305560805@sss.pgh.pa.us >
<B91EFACD-9560-45CB-8614-120D57B5A2F0@nasby.net >
<4DD487CF.8010003@2ndquadrant.com >
<BANLkTiktoq=GZjBgPNakwS8_DNK2rmYi2Q@mail.gmail.com >
<091662B1-58B5-489D-8A92-0251A1E01E7C@nasby.net >
<BANLkTik0FgfvNvhXC6+AW0jTrGq5RUbFLw@mail.gmail.com >
> 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
view thread (43+ messages) latest in thread
Message-ID: <4DDAB097.9070505@agliodbs.com>
Permalink: ../4DDAB097.9070505@agliodbs.com/
Also on: postgresql.org/message-id/4DDAB097.9070505@agliodbs.com
copy link · copy postgr.es
reply Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: josh@agliodbs.com
Subject: Re: reducing random_page_cost from 4 to 2 to force index scan
In-Reply-To: <4DDAB097.9070505@agliodbs.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox