On Tue, Jul 19, 2005 at 02:32:23PM +0200, Martin Pitt wrote:
> Uh, that must be a big one. How long does "VACUUM" run?
Well, it's not that big (usually between 800-900M) rather than the disk
is really slow. It's not a problem for normal operation, but "VACUUM
FULL" is a killer. Even a simple "VACUUM" takes 14.5 minutes.
> It is mentioned:
Ah, I didn't read hard anough...
> At the time when the script runs all clusters are already started
> again, so it's not really a downtime.
Well, I have only one important database, and "VACUUM FULL" takes the
"ACCESS EXCLUSIVE" lock so the database _is_ down for all practical
purposes.
> This was mainly added by me to
> test upgrading scripts, and it will be removed again soon. I don't
> want the first security update for a stable release to be the first
> time the upgrading scripts mechanism is tested.
Can't you use some more lightweight command that does not want to modify
the database?
Gabor
--
---------------------------------------------------------
MTA SZTAKI Computer and Automation Research Institute
Hungarian Academy of Sciences,
Laboratory of Parallel and Distributed Systems
Address : H-1132 Budapest Victor Hugo u. 18-22. Hungary
Phone/Fax : +36 1 329-78-64 (secretary)
W3 : http://www.lpds.sztaki.hu
---------------------------------------------------------
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
