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

Re: One source of constant annoyance identified

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Curt Sampson <cjs(at)cynic(dot)net>
Cc: Markus Wollny <Markus(dot)Wollny(at)computec(dot)de>,pgsql-general(at)postgresql(dot)org
Subject: Re: One source of constant annoyance identified
Date: 2002-06-28 13:37:16
Message-ID: 3399.1025271436@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-general
Curt Sampson <cjs(at)cynic(dot)net> writes:
> On Thu, 27 Jun 2002, Tom Lane wrote:
>> So you haven't really solved the problem --- somewhere there is a query
>> being issued that ramps the backend up to a lot of memory.  All you've
>> done is ensured that the backend won't hang around very long.  The
>> persistent connection isn't really at fault, except in that it causes
>> backends to keep being used after their memory usage has become bloated.

> Yeah, but if the queries after that are not using all of the mapped
> memory, that should be swapped out fairly quickly because the
> machine is short on memory.

And the swapping activity is exactly the problem, isn't it?

In any case, we can't make much progress until we identify the query
that is making the backend's address space grow.

(Markus, you don't happen to have SORT_MEM set to a large value,
do you?)

			regards, tom lane



In response to

Responses

pgsql-general by date

Next:From: Oleg BartunovDate: 2002-06-28 13:40:24
Subject: Re: recursing down a tree
Previous:From: Steve BrettDate: 2002-06-28 13:27:07
Subject: Re: What is a tuple?

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