Re: Select performance vs. mssql

From: Josh Berkus <josh(at)agliodbs(dot)com>
To: mark durrant <markd89(at)yahoo(dot)com>
Cc: Bruno Wolff III <bruno(at)wolff(dot)to>, pgsql-performance(at)postgresql(dot)org
Subject: Re: Select performance vs. mssql
Date: 2005-05-24 23:35:14
Message-ID: 200505241635.14558.josh@agliodbs.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

Folks,

> > 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.

Pretty much. There has been discussion about allowing index-only access to
"frozen" tables, i.e. archive partitions. But it all sort of hinges on
someone implementing it and testing ....

--
--Josh

Josh Berkus
Aglio Database Solutions
San Francisco

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message PFC 2005-05-25 00:14:01 Re: Select performance vs. mssql
Previous Message Alex Turner 2005-05-24 23:12:14 Re: Select performance vs. mssql