From: Robert Lor <Robert.Lor@Sun.COM>
To: Robert Treat <xzilla@users.sourceforge.net>
Cc: pgsql-hackers@postgresql.org, Greg Smith <gsmith@gregsmith.com>
Cc: Aidan Van Dyk <aidan@highrise.ca>
Subject: Re: Overhauling GUCS
Date: Fri, 06 Jun 2008 16:29:12 -0500
Message-ID: <4849AC28.4060801@sun.com> (raw)
In-Reply-To: <200806061541.36984.xzilla@users.sourceforge.net>
References: <48409D1E.3070208@agliodbs.com>
<20080605011455.GF14498@yugib.highrise.ca>
<Pine.GSO.4.64.0806042134090.3874@westnet.com>
<200806061541.36984.xzilla@users.sourceforge.net>
Robert Treat wrote:
> On Wednesday 04 June 2008 22:04:54 Greg Smith wrote:
>
>> 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 ;-)
>
>
Actually, you can find out from the sort-end probe now whether or not
the sort spilled to disk and number of disk blocks used. This is one of
the probes from Simon.
TRACE_POSTGRESQL_SORT_END(state->tapeset,
(state->tapeset ?
LogicalTapeSetBlocks(state->tapeset) :
(state->allowedMem - state->availMem + 1023) /
1024));
-Robert
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: Robert.Lor@Sun.COM, xzilla@users.sourceforge.net, gsmith@gregsmith.com, aidan@highrise.ca
Subject: Re: Overhauling GUCS
In-Reply-To: <4849AC28.4060801@sun.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox