From: Tom Lane <tgl@sss.pgh.pa.us>
To: Alexander Stanier <alexander.stanier@egsgroup.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Heavy virtual memory usage on production system
Date: Wed, 06 Jul 2005 11:06:02 -0400
Message-ID: <26526.1120662362@sss.pgh.pa.us> (raw)
In-Reply-To: <42CBEF84.8080007@egsgroup.com>
References: <42CAB1B6.50201@egsgroup.com>
<23889.1120582516@sss.pgh.pa.us>
<42CBC8A0.4070901@egsgroup.com>
<25886.1120659333@sss.pgh.pa.us>
<42CBEF84.8080007@egsgroup.com>
Alexander Stanier <alexander.stanier@egsgroup.com> writes:
> Looks as though there are several processes which are acquiring a load
> of locks:
13 locks isn't "a load". I was worried about scenarios in which a
single process might take hundreds or thousands of locks; it doesn't
look like you have that.
regards, tom lane
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: tgl@sss.pgh.pa.us, alexander.stanier@egsgroup.com
Subject: Re: Heavy virtual memory usage on production system
In-Reply-To: <26526.1120662362@sss.pgh.pa.us>
* 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