Date: Fri, 06 Jun 2008 15:41:36 -0400
From: Robert Treat <xzilla@users.sourceforge.net>
Subject: Re: Overhauling GUCS
In-reply-to: <Pine.GSO.4.64.0806042134090.3874@westnet.com>
To: pgsql-hackers@postgresql.org
Cc: Greg Smith <gsmith@gregsmith.com>, Aidan Van Dyk <aidan@highrise.ca>
Message-id: <200806061541.36984.xzilla@users.sourceforge.net>
MIME-version: 1.0
Content-type: text/plain; charset=iso-8859-1
Content-transfer-encoding: 7bit
Content-disposition: inline
References: <48409D1E.3070208@agliodbs.com>
	<20080605011455.GF14498@yugib.highrise.ca>
	<Pine.GSO.4.64.0806042134090.3874@westnet.com>
User-Agent: KMail/1.9.9

On Wednesday 04 June 2008 22:04:54 Greg Smith wrote:
> On Wed, 4 Jun 2008, Aidan Van Dyk wrote:
> > * Are we always spilling small amounts of data to disk for sorting?  A
> >  a small work_mem increase might help...
>
> I was just talking to someone today about building a monitoring tool for
> this.  Not having a clear way to recommend people monitor use of work_mem
> and its brother spilled to disk sorts is an issue right now, I'll whack
> that one myself if someone doesn't beat me to it before I get time.
>

I remember *years* ago, someone wrote a perl script to poll pgsql_tmp and 
print out anytime something showed up... you could probably find that in the 
archives if you look around. 

of course to me this sounds like an excellent idea for a dtrace probe ;-)

-- 
Robert Treat
Build A Brighter LAMP :: Linux Apache {middleware} PostgreSQL