pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Jean-Luc Lachance <jllachan@nsd.ca>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: jim@nasby.net, "scott.marlowe" <scott.marlowe@ihs.com>
Cc: Matthew Nuzum <cobalt@bearfruit.org>
Cc: 'Josh Berkus' <josh@agliodbs.com>
Cc: 'Pgsql-Performance' <pgsql-performance@postgresql.org>
Subject: Re: Caching (was Re: choosing the right platform)
Date: Thu, 10 Apr 2003 14:59:55 -0400
Message-ID: <3E95BF2B.B93FD0EF@nsd.ca> (raw)
References: <00a001c2febb$631141d0$6900a8c0@mattspc>
	<Pine.LNX.4.33.0304091152550.22442-100000@css120.ihs.com>
	<20030409184744.W31861@flake.decibel.org>
	<11732.1049934037@sss.pgh.pa.us>
	<3E957F44.A1106F6A@nsd.ca>
	<4072.1049985615@sss.pgh.pa.us>

How can we solve the problem of cache trashing when scanning large
tables?

Tom Lane wrote:
> 
> Jean-Luc Lachance <jllachan@nsd.ca> writes:
> > Shouldn't there be a way to lock some tables in PG cache?
> 
> In my opinion, no.  I do not think a manual locking feature could
> possibly be used effectively.  It could very easily be abused to
> decrease net performance, though :-(
> 
> It does seem that a smarter buffer management algorithm would be a good
> idea, but past experiments have failed to show any measurable benefit.
> Perhaps those experiments were testing the wrong conditions.  I'd still
> be happy to see LRU(k) or some such method put in, if someone can prove
> that it actually does anything useful for us.  (As best I recall, I only
> tested LRU-2 with pgbench.  Perhaps Josh's benchmarking project will
> offer a wider variety of interesting scenarios.)
> 
>                         regards, tom lane
> 
> ---------------------------(end of broadcast)---------------------------
> TIP 1: subscribe and unsubscribe commands go to majordomo@postgresql.org




view thread (14+ messages)  latest in thread

Message-ID: <3E95BF2B.B93FD0EF@nsd.ca>
Permalink:  ../3E95BF2B.B93FD0EF@nsd.ca/
Also on:    postgresql.org/message-id/3E95BF2B.B93FD0EF@nsd.ca

 · 

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 from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-performance@postgresql.org
  Cc: jllachan@nsd.ca, tgl@sss.pgh.pa.us, scott.marlowe@ihs.com, cobalt@bearfruit.org, josh@agliodbs.com
  Subject: Re: Caching (was Re: choosing the right platform)
  In-Reply-To: <3E95BF2B.B93FD0EF@nsd.ca>
  References: <00a001c2febb$631141d0$6900a8c0@mattspc> <Pine.LNX.4.33.0304091152550.22442-100000@css120.ihs.com> <20030409184744.W31861@flake.decibel.org> <11732.1049934037@sss.pgh.pa.us> <3E957F44.A1106F6A@nsd.ca> <4072.1049985615@sss.pgh.pa.us> <3E95BF2B.B93FD0EF@nsd.ca>

* 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