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
Peter Eisentraut peter_e(at)gmx(dot)net http://funkturm.homeip.net/~peter
In response to
pgsql-hackers by date
|Next:||From: Mikheev, Vadim||Date: 2001-07-06 15:54:27|
|Subject: RE: AW: AW: Re: Backup and Recovery |
|Previous:||From: Doug McNaught||Date: 2001-07-06 15:42:08|
|Subject: Re: Proper use of select() parameter nfds?|
pgsql-general by date
|Next:||From: Tom Lane||Date: 2001-07-06 16:02:04|
|Subject: Re: Vacuum and Transactions |
|Previous:||From: Philip Molter||Date: 2001-07-06 15:12:31|
|Subject: HUPing a database|