pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: Vitalii Tymchyshyn <tivv00@gmail.com>
To: Robert Haas <robertmhaas@gmail.com>
Cc: Josh Berkus <josh@agliodbs.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: reducing random_page_cost from 4 to 2 to force index scan
Date: Tue, 24 May 2011 12:12:34 +0300
Message-ID: <4DDB7682.9040402@gmail.com> (raw)
In-Reply-To: <BANLkTin2seetry0y0Nked0FMqwq-yDOGFw@mail.gmail.com>
References: <BANLkTikZhYc+h1=YDJfXwZEZc1tN3_VwCg@mail.gmail.com>
	<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>
	<4DDAB097.9070505@agliodbs.com>
	<BANLkTin2seetry0y0Nked0FMqwq-yDOGFw@mail.gmail.com>

Hello.

As of me, all this "hot" thing really looks like uncertain and dynamic 
enough.
Two things that I could directly use right now (and they are needed in 
pair) are:
1)Per-table/index/database bufferpools (split shared buffer into parts, 
allow to specify which index/table/database goes where)
2)Per-table/index cost settings

If I had this, I could allocate specific bufferpools for tables/indexes 
that MUST be hot in memory and set low costs for this specific tables.
P.S. Third thing, great to have to companion this two is "Load on 
startup" flag to automatically populate bufferpools with fast sequential 
read, but this can be easily emulated with a statement.

Best regards, Vitalii Tymchyshyn



view thread (43+ messages)

Message-ID: <4DDB7682.9040402@gmail.com>
Permalink:  ../4DDB7682.9040402@gmail.com/
Also on:    postgresql.org/message-id/4DDB7682.9040402@gmail.com

 · 

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: tivv00@gmail.com, robertmhaas@gmail.com, josh@agliodbs.com
  Subject: Re: reducing random_page_cost from 4 to 2 to force index scan
  In-Reply-To: <4DDB7682.9040402@gmail.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