From: Josh Berkus <josh@agliodbs.com>
Reply-To: josh@agliodbs.com
Organization: Aglio Database Solutions
To: pgsql-performance@postgresql.org
Subject: Re: Read/Write block sizes
Date: Thu, 25 Aug 2005 12:45:03 -0700
User-Agent: KMail/1.8
Cc: "Jeffrey W. Baker" <jwbaker@acm.org>,
	Tom Lane <tgl@sss.pgh.pa.us>, Guy Thornley <guy@esphion.com>,
	Steve Poe <spoe@sfnet.cc>, Chris Browne <cbbrowne@acm.org>
References: <d4b67d7c2b.d7c2bd4b67@bur-mail1.east.sun.com>
	<21700.1124863004@sss.pgh.pa.us>
	<1124864572.11270.16.camel@noodles>
In-Reply-To: <1124864572.11270.16.camel@noodles>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
Message-Id: <200508251245.03473.josh@agliodbs.com>

Jeff,

> Ask me sometime about my replacement for GNU sort. =C2=A0It uses the same
> sorting algorithm, but it's an order of magnitude faster due to better
> I/O strategy. =C2=A0Someday, in my infinite spare time, I hope to demonst=
rate
> that kind of improvement with a patch to pg.

Since we desperately need some improvements in sort performance, I do hope=
=20
you follow up on this.

=2D-=20
=2D-Josh

Josh Berkus
Aglio Database Solutions
San Francisco