pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Neil Conway <neilc@samurai.com>
Cc: Andrew Sullivan <andrew@libertyrms.info>
Cc: PostgreSQL Performance <pgsql-performance@postgresql.org>
Subject: Re: reindex/vacuum locking/performance?
Date: Sun, 05 Oct 2003 19:43:48 -0400
Message-ID: <15813.1065397428@sss.pgh.pa.us> (raw)
In-Reply-To: <1065396767.466.12.camel@tokyo>
References: <60d6de9fah.fsf@dev6.int.libertyrms.info>
	<LFEIJBEOKGPDHCEMDGNFAEOCCFAA.matt@ymogen.net>
	<20031004152241.GL580@libertyrms.info>
	<1065396767.466.12.camel@tokyo>

Neil Conway <neilc@samurai.com> writes:
> ... We could even have the
> VACUUM command inform the bufmgr that the pages it is in the process of
> reading in are part of a seqscan, and so are unlikely to be needed in
> the immediate future.

This would be relatively easy to fix as far as our own buffering is
concerned, but the thing that's needed to make it really useful is
to prevent caching of seqscan-read pages in the kernel disk buffers.
I don't know any portable way to do that :-(

			regards, tom lane



view thread (37+ messages)  latest in thread

Message-ID: <15813.1065397428@sss.pgh.pa.us>
Permalink:  ../15813.1065397428@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/15813.1065397428@sss.pgh.pa.us

 · 

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: tgl@sss.pgh.pa.us, neilc@samurai.com, andrew@libertyrms.info
  Subject: Re: reindex/vacuum locking/performance?
  In-Reply-To: <15813.1065397428@sss.pgh.pa.us>

* 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