Re: proposal: be smarter about i/o patterns in index scan - Mailing list pgsql-hackers

From Jeffrey W. Baker
Subject Re: proposal: be smarter about i/o patterns in index scan
Date
Msg-id 1084989749.19249.1.camel@heat
Whole thread Raw
In response to Re: proposal: be smarter about i/o patterns in index scan  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses search engine down (again)
Re: proposal: be smarter about i/o patterns in index scan
List pgsql-hackers
On Wed, 2004-05-19 at 07:58, Tom Lane wrote:
> "Jeffrey W. Baker" <jwbaker@acm.org> writes:
> > We have noticed a way to make a major improvement in Pg's performance on
> > our workload, and I would like to get your thoughts before I go off to
> > work up a patch.
> 
> For starters, read the previous discussions of this in the archives.

If you are referring to archives.postgresql.org, all I have to say is: 

"An error occured!  Can not connect to search daemon"

And as far as I have seen, it's been like that for years.

> Two questions you should have answers to before starting to implement,
> rather than after, are how to deal with locking considerations and
> what will be the implications of giving up the property that indexscans
> deliver sorted output.

Are you saying that index scan results are sorted by something other
than the index key?  Because in my scheme they would still be sorted by
index key.

-jwb



pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: Call for 7.5 feature completion
Next
From: "Magnus Hagander"
Date:
Subject: Re: Call for 7.5 feature completion