Received: from localhost (maia-4.hub.org [200.46.204.183])
	by postgresql.org (Postfix) with ESMTP id 22F829FB28C
	for <pgsql-performance-postgresql.org@postgresql.org>;
	Mon, 23 Jul 2007 11:55:09 -0300 (ADT)
Received: from postgresql.org ([200.46.204.71])
	by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024)
	with ESMTP id 03005-02 for
	<pgsql-performance-postgresql.org@postgresql.org>;
	Mon, 23 Jul 2007 11:55:06 -0300 (ADT)
X-Greylist: from auto-whitelisted by SQLgrey-1.7.5
Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130])
	by postgresql.org (Postfix) with ESMTP id 72A539FB1BB
	for <pgsql-performance@postgresql.org>;
	Mon, 23 Jul 2007 11:55:06 -0300 (ADT)
Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1])
	by sss.pgh.pa.us (8.14.1/8.14.1) with ESMTP id l6NEswG1025096;
	Mon, 23 Jul 2007 10:54:58 -0400 (EDT)
To: "Simon Riggs" <simon@2ndquadrant.com>
cc: "Jignesh K. Shah" <J.K.Shah@Sun.COM>, "Josh Berkus" <josh@agliodbs.com>,
	pgsql-performance@postgresql.org,
	"Alvaro Herrera" <alvherre@commandprompt.com>
Subject: Re: User concurrency thresholding: where do I look? 
In-reply-to: <1185201556.4284.243.camel@ebony.site> 
References: <200707190828.59088.josh@agliodbs.com>
	<200707191819.13899.josh@agliodbs.com>
	<15685.1184895926@sss.pgh.pa.us>
	<200707192138.39679.josh@agliodbs.com>
	<46A0FA31.2080208@sun.com> <12002.1184955831@sss.pgh.pa.us>
	<46A1055F.9010304@sun.com> <12445.1184958793@sss.pgh.pa.us>
	<46A11116.5030905@sun.com> <14909.1184962561@sss.pgh.pa.us>
	<46A1205B.8010205@sun.com> <15343.1184965054@sss.pgh.pa.us>
	<1185180668.4284.149.camel@ebony.site>
	<23848.1185199901@sss.pgh.pa.us>
	<1185201556.4284.243.camel@ebony.site>
Comments: In-reply-to "Simon Riggs" <simon@2ndquadrant.com>
	message dated "Mon, 23 Jul 2007 15:39:16 +0100"
Date: Mon, 23 Jul 2007 10:54:58 -0400
Message-ID: <25095.1185202498@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
X-Virus-Scanned: Maia Mailguard 1.0.1
X-Archive-Number: 200707/291
X-Sequence-Number: 25975

"Simon Riggs" <simon@2ndquadrant.com> writes:
> I looked at this last May and my notes say "ExecutorState". I guess that
> was wrong, but my analysis showed there was a single malloc of 8228
> bytes happening once per query during my tests. 

Well, if you can track down where it's coming from, we could certainly
hack the containing context's parameters.  But EState's not it.

			regards, tom lane