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

Re: Vacuum and Transactions

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: "Trewern, Ben" <Ben(dot)Trewern(at)mowlem(dot)com>
Cc: "'pgsql-general(at)postgresql(dot)org'" <pgsql-general(at)postgresql(dot)org>
Subject: Re: Vacuum and Transactions
Date: 2001-07-06 15:45:17
Message-ID: Pine.LNX.4.30.0107061742280.679-100000@peter.localdomain (view raw or flat)
Thread:
Lists: pgsql-generalpgsql-hackers
Trewern, Ben writes:

> 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.

There are plans to make vacuum less intrusive in the next major release,
but until then this is what you have to deal with.  Unless you really need
to run vacuum all the time you should schedule it for low activity times.
Yes, that means 24/7 100% uptime is not *really* feasible with PostgreSQL.

> This email and any attachments transmitted with it are confidential

If the email is confidential you shouldn't send it to public mailing
lists.

-- 
Peter Eisentraut   peter_e(at)gmx(dot)net   http://funkturm.homeip.net/~peter


In response to

pgsql-hackers by date

Next:From: Mikheev, VadimDate: 2001-07-06 15:54:27
Subject: RE: AW: AW: Re: Backup and Recovery
Previous:From: Doug McNaughtDate: 2001-07-06 15:42:08
Subject: Re: Proper use of select() parameter nfds?

pgsql-general by date

Next:From: Tom LaneDate: 2001-07-06 16:02:04
Subject: Re: Vacuum and Transactions
Previous:From: Philip MolterDate: 2001-07-06 15:12:31
Subject: HUPing a database

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