Skip site navigation (1) Skip section navigation (2)

Re: Select performance vs. mssql

From: Bruno Wolff III <bruno(at)wolff(dot)to>
To: mark durrant <markd89(at)yahoo(dot)com>
Cc: pgsql-performance(at)postgresql(dot)org
Subject: Re: Select performance vs. mssql
Date: 2005-05-24 17:27:13
Message-ID: 20050524172713.GC8129@wolff.to (view raw or flat)
Thread:
Lists: pgsql-performance
On Tue, May 24, 2005 at 08:36:36 -0700,
  mark durrant <markd89(at)yahoo(dot)com> wrote:
> 
> --MSSQL's ability to hit the index only and not having
> to go to the table itself results in a _big_
> performance/efficiency gain. If someone who's in
> development wants to pass this along, it would be a
> nice addition to PostgreSQL sometime in the future.
> I'd suspect that as well as making one query faster,
> it would make everything else faster/more scalable as
> the server load is so much less.

This gets brought up a lot. The problem is that the index doesn't include
information about whether the current transaction can see the referenced
row. Putting this information in the index will add significant overhead
to every update and the opinion of the developers is that this would be
a net loss overall.

In response to

Responses

pgsql-performance by date

Next:From: Josh BerkusDate: 2005-05-24 17:37:48
Subject: Re: Need help to decide Mysql vs Postgres
Previous:From: Amit V ShahDate: 2005-05-24 17:22:08
Subject: Re: Need help to decide Mysql vs Postgres

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group