pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Rod Taylor <pg@rbt.ca>
To: Iain <iain@mst.co.jp>
Cc: Postgresql Performance <pgsql-performance@postgresql.org>
Cc: Mark Aufflick <mark@pumptheory.com>
Subject: Re: seq scan cache vs. index cache smackdown
Date: Mon, 14 Feb 2005 23:20:51 -0500
Message-ID: <1108441251.67118.111.camel@home> (raw)
In-Reply-To: <00a001c51312$35fb5510$7201a8c0@mst1x5r347kymb>
References: <FC8ED065-7EE0-11D9-904E-003065D62456@pumptheory.com>
	<00a001c51312$35fb5510$7201a8c0@mst1x5r347kymb>

> My concern is that this kind of testing has very little relevance to the 
> real world of multiuser processing where contention for the cache becomes an 
> issue.  It may be that, at least in the current situation, postgres is 
> giving too much weight to seq scans based on single user, straight line 

To be fair, a large index scan can easily throw the buffers out of whack
as well. An index scan on 0.1% of a table with 1 billion tuples will
have a similar impact to buffers as a sequential scan of a table with 1
million tuples.

Any solution fixing buffers should probably not take into consideration
the method being performed (do you really want to skip caching a
sequential scan of a 2 tuple table because it didn't use an index) but
the volume of data involved as compared to the size of the cache.

I've often wondered if a single 1GB toasted tuple could wipe out the
buffers. I would suppose that toast doesn't bypass them.
-- 
Rod Taylor <pg@rbt.ca>




view thread (24+ messages)  latest in thread

Message-ID: <1108441251.67118.111.camel@home>
Permalink:  ../1108441251.67118.111.camel@home/
Also on:    postgresql.org/message-id/1108441251.67118.111.camel@home

 · 

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: pg@rbt.ca, iain@mst.co.jp, mark@pumptheory.com
  Subject: Re: seq scan cache vs. index cache smackdown
  In-Reply-To: <1108441251.67118.111.camel@home>

* 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