From: imad <immaad@gmail.com>
To: Campbell, Lance <lance@uiuc.edu>
Cc: pgsql-performance@postgresql.org
Subject: Re: work-mem
Date: Mon, 29 Jan 2007 01:26:21 +0500
Message-ID: <1f30b80c0701281226k69f0d455qdd2a5b2dc85b80c5@mail.gmail.com> (raw)
In-Reply-To: <A3AC4FA47DC0B1458C3E5396E685E63302395C68@SAB-DC1.sab.uiuc.edu>
References: <A3AC4FA47DC0B1458C3E5396E685E63302395C68@SAB-DC1.sab.uiuc.edu>
work-mem tells the size of physical memory only, virtual memory is
always there off course in case you run out of available memory.
I recommend you reading PostgreSQL internals for all this stuff:
http://www.postgresql.org/docs/8.0/static/internals.html
--Imad
www.EnterpriseDB.com
On 1/29/07, Campbell, Lance <lance@uiuc.edu> wrote:
>
>
>
>
> I have been researching how to improve my overall performance of postgres.
> I am a little confused on the reasoning for how work-mem is used in the
> postgresql.conf file. The way I understand the documentation is you define
> with work-mem how much memory you want to allocate per search. Couldn't you
> run out of memory? This approach seems kind of odd to me. How do you tell
> the system not to allocate too much memory if you all of the sudden got hit
> with a heavier number of queries?
>
>
>
>
>
> Thanks,
>
>
>
> Lance Campbell
>
> Project Manager/Software Architect
>
> Web Services at Public Affairs
>
> University of Illinois
>
> 217.333.0382
>
> http://webservices.uiuc.edu
>
>
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-performance@postgresql.org
Cc: immaad@gmail.com, lance@uiuc.edu
Subject: Re: work-mem
In-Reply-To: <1f30b80c0701281226k69f0d455qdd2a5b2dc85b80c5@mail.gmail.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