Skip site navigation (1) Skip section navigation (2)

Re: User concurrency thresholding: where do I look?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Simon Riggs" <simon(at)2ndquadrant(dot)com>
Cc: "Jignesh K(dot) Shah" <J(dot)K(dot)Shah(at)Sun(dot)COM>, "Josh Berkus" <josh(at)agliodbs(dot)com>, pgsql-performance(at)postgresql(dot)org, "Alvaro Herrera" <alvherre(at)commandprompt(dot)com>
Subject: Re: User concurrency thresholding: where do I look?
Date: 2007-07-23 14:54:58
Message-ID: 25095.1185202498@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-performance
"Simon Riggs" <simon(at)2ndquadrant(dot)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

In response to

Responses

pgsql-performance by date

Next:From: Simon RiggsDate: 2007-07-23 15:47:43
Subject: Re: User concurrency thresholding: where do I look?
Previous:From: Simon RiggsDate: 2007-07-23 14:39:16
Subject: Re: User concurrency thresholding: where do I look?

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group