From: Christopher Kings-Lynne <chriskl@familyhealth.com.au>
To: Shea,Dan [CIS] <Dan.Shea@ec.gc.ca>
Cc: pgsql-performance@postgresql.org
Subject: Re: Why will vacuum not end?
Date: Wed, 21 Apr 2004 09:26:27 +0800
Message-ID: <4085CDC3.4090201@familyhealth.com.au> (raw)
In-Reply-To: <F2D63B916C88C14D9B59F93C2A5DD33F0B923F@cisxa.cmc.int.ec.gc.ca>
References: <F2D63B916C88C14D9B59F93C2A5DD33F0B923F@cisxa.cmc.int.ec.gc.ca>
> No, but data is constantly being inserted by userid scores. It is postgres
> runnimg the vacuum.
> Dan.
Well, inserts create some locks - perhaps that's the problem...
Otherwise, check the pg_locks view to see if you can figure it out.
Chris
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: chriskl@familyhealth.com.au, Dan.Shea@ec.gc.ca
Subject: Re: Why will vacuum not end?
In-Reply-To: <4085CDC3.4090201@familyhealth.com.au>
* 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