From: Bill Moran <wmoran@potentialtech.com>
To: Shea,Dan [CIS] <Dan.Shea@ec.gc.ca>
Cc: Christopher Kings-Lynne <chriskl@familyhealth.com.au>
Cc: pgsql-performance@postgresql.org
Subject: Re: Why will vacuum not end?
Date: Tue, 20 Apr 2004 09:14:00 -0400
Message-ID: <40852218.2050204@potentialtech.com> (raw)
In-Reply-To: <F2D63B916C88C14D9B59F93C2A5DD33F0B923F@cisxa.cmc.int.ec.gc.ca>
References: <F2D63B916C88C14D9B59F93C2A5DD33F0B923F@cisxa.cmc.int.ec.gc.ca>
Shea,Dan [CIS] wrote:
> No, but data is constantly being inserted by userid scores. It is postgres
> runnimg the vacuum.
> Dan.
>
> -----Original Message-----
> From: Christopher Kings-Lynne [mailto:chriskl@familyhealth.com.au]
> Sent: Tuesday, April 20, 2004 12:02 AM
> To: Shea,Dan [CIS]
> Cc: pgsql-performance@postgresql.org
> Subject: Re: [PERFORM] Why will vacuum not end?
>
>>This vacuum is running a marathon. Why will it not end and show me free
>>space map INFO? We have deleted a lot of data and I would like to be
>>confident that these deletions will be used as free space, rather than
>>creating more table files.
>
> Does another postgres query running have a lock on that table?
This may be a dumb question (but only because I don't know the answer)
Doesn't/shouldn't vacuum have some kind of timeout so if a table is locked
it will give up eventually (loudly complaining when it does so)?
--
Bill Moran
Potential Technologies
http://www.potentialtech.com
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: wmoran@potentialtech.com, Dan.Shea@ec.gc.ca, chriskl@familyhealth.com.au
Subject: Re: Why will vacuum not end?
In-Reply-To: <40852218.2050204@potentialtech.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