From: Tom Lane <tgl@sss.pgh.pa.us>
To: josh@agliodbs.com
Cc: Gary Doades <gpd@gpdnet.co.uk>
Cc: pgsql-performance@postgresql.org
Subject: Re: planner/optimizer question
Date: Thu, 29 Apr 2004 19:17:49 -0400
Message-ID: <17898.1083280669@sss.pgh.pa.us> (raw)
In-Reply-To: <200404291354.33304.josh@agliodbs.com>
References: <409153EF.24647.144E9BF7@localhost>
<409172FA.1509.14C7E00E@localhost>
<200404291354.33304.josh@agliodbs.com>
Josh Berkus <josh@agliodbs.com> writes:
> Certainly the fact that MSSQL is essentially a single-user database makes
> things easier for them.
Our recent testing (cf the "Xeon" thread) says that the interlocking we
do to make the world safe for multiple backends has a fairly high cost
(at least on some hardware) compared to the rest of the work in
scenarios where you are doing zero-I/O scans of data already in memory.
Especially so for index scans. I'm not sure this completely explains
the differential that Gary is complaining about, but it could be part of
it. Is it really true that MSSQL doesn't support concurrent operations?
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, gpd@gpdnet.co.uk
Subject: Re: planner/optimizer question
In-Reply-To: <17898.1083280669@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