pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Andrew Sullivan <andrew@libertyrms.info>
Cc: pgsql-performance@postgresql.org
Subject: Re: vacuum locking
Date: Thu, 23 Oct 2003 09:17:41 -0400
Message-ID: <29064.1066915061@sss.pgh.pa.us> (raw)
In-Reply-To: <20031023101425.GC16878@libertyrms.info>
References: <16272.318.870000.93584@gargle.gargle.HOWL>
	<3F9006BF.40906@persistent.co.in>
	<16272.4154.489000.227676@gargle.gargle.HOWL>
	<200310170936.25997.josh@agliodbs.com>
	<16272.32044.80671.948532@jump.bivio.com>
	<x7d6cpcdsr.fsf@yertle.int.kciLink.com>
	<16279.4988.496000.539525@gargle.gargle.HOWL>
	<25480.1066872467@sss.pgh.pa.us>
	<20031023101425.GC16878@libertyrms.info>

Andrew Sullivan <andrew@libertyrms.info> writes:
> On Wed, Oct 22, 2003 at 09:27:47PM -0400, Tom Lane wrote:
>> trace.  What is causing that?  Not VACUUM I don't think.  It doesn't have
>> any huge memory demand.  But swapping out processes could account for

> What about if you've set vacuum_mem too high?

Maybe, but only if it actually had reason to use a ton of memory ---
that is, it were recycling a very large number of tuples in a single
table.  IIRC that didn't seem to be the case here.

			regards, tom lane



view thread (45+ messages)  latest in thread

Message-ID: <29064.1066915061@sss.pgh.pa.us>
Permalink:  ../29064.1066915061@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/29064.1066915061@sss.pgh.pa.us

 · 

reply

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, andrew@libertyrms.info
  Subject: Re: vacuum locking
  In-Reply-To: <29064.1066915061@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