Re: Is vacuum full lock like old's vacuum's lock?

> Do sequential scans go over the entire space, including the space not in
> use? It would be great if there was some kind of optimization that could
> move the empty space towards the end. It would probably be an expensive
> operation, but it may be very helpfull on databases with a big turnaround.

The only difference between doing that and doing a VACUUM FULL would be that
the disk usage would remain the same.

> Does vacuum full locks only a table or the entire DB?

I'm sure someone will correct me if I'm wrong (as Tom Lane has had to do on
many an occassion <g>), but I think it just locks the table that's being
vacuumed.

> Specially if I did VACUUM FULL <table>.
> I am thinking maybe scatter the VACUUM FULLs accross the week and doing
> one table daily instead of trying the whole DB.

Personally, I would continue do the entire database once a week, and select
a few key tables that have a lot of UPDATEs/DELETEs to do daily (or however
frequently is necessary). That way the tables that need it get more frequent
attention, but you don't have to go over the entire database frequently. Of
course, I haven't been following the thread carefully enough to understand
your specific needs...

Greg