Skip site navigation (1) Skip section navigation (2)

Re: Vacuum and Transactions

From: "Richard Huxton" <dev(at)archonet(dot)com>
To: "Trewern, Ben" <Ben(dot)Trewern(at)mowlem(dot)com>, <pgsql-general(at)postgresql(dot)org>
Subject: Re: Vacuum and Transactions
Date: 2001-07-06 16:42:23
Message-ID: 003501c1063a$ea62d520$1001a8c0@archonet.com (view raw or flat)
Thread:
Lists: pgsql-generalpgsql-hackers
From: "Trewern, Ben" <Ben(dot)Trewern(at)mowlem(dot)com>

> If there is a transaction running when 'vacuumdb -a -z' is run (as a cron
> job) it stops running at that database till the transaction completes.
That
> is not so much of a problem until a new client tries to connect to the
> database.  This new connection hangs, waiting for the vacuum to complete.
> This situation is not all that helpful and means I have to be careful at
> what time I run vacuum so it does not interfere with new clients.  Is this
a
> bug or the standard way in which postgres works and are there any plans
> change this?

Would vacuuming the tables one at a time not help here? It'd mean a small
script to read a list of databases/tables out of PG but should reduce the
impact on your clients (if I'm thinking straight here)

- Richard Huxton


In response to

pgsql-hackers by date

Next:From: Jean-Francois LevequeDate: 2001-07-06 17:11:13
Subject: Re: Database Users Management and Privileges
Previous:From: J-P GuguyDate: 2001-07-06 16:16:47
Subject: amiint

pgsql-general by date

Next:From: Ed LoehrDate: 2001-07-06 16:59:22
Subject: query syntax change?
Previous:From: Steve WamplerDate: 2001-07-06 16:29:57
Subject: Too much data received?

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group