From: Tom Lane <tgl@sss.pgh.pa.us>
To: Josh Berkus <josh@agliodbs.com>
Cc: Greg Stark <gsstark@mit.edu>
Cc: Mark Aufflick <mark@pumptheory.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: seq scan cache vs. index cache smackdown
Date: Tue, 15 Feb 2005 12:55:19 -0500
Message-ID: <14042.1108490119@sss.pgh.pa.us> (raw)
In-Reply-To: <200502150922.59176.josh@agliodbs.com>
References: <FC8ED065-7EE0-11D9-904E-003065D62456@pumptheory.com>
<9326.1108452962@sss.pgh.pa.us>
<87vf8u2qgw.fsf@stark.xeocode.com>
<200502150922.59176.josh@agliodbs.com>
Josh Berkus <josh@agliodbs.com> writes:
> Why is mmap not workable?
We can't control write order. There are other equally bad problems,
but that one alone eliminates it from consideration. See past discussions.
regards, tom lane
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, josh@agliodbs.com, gsstark@mit.edu, mark@pumptheory.com
Subject: Re: seq scan cache vs. index cache smackdown
In-Reply-To: <14042.1108490119@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