Re: update functions locking tables

30 Aug 2005 09:10:51 -0400, Greg Stark <gsstark@mit.edu>:
>
> I think truncate takes a table lock.
> Just change it to "delete from times_producao".

Thanks, i will try it.

>
> Also, if consider doing a "vacuum full" or "cluster" after the batch job to
> clear up the free space (not in a large transaction). That will still take a
> table lock but it may be a small enough downtime to be worth the speed
> increase the rest of the day.
>

I'm already doing a vacuum (not full) once a day.

A vacuum full or a cluster is totally out of reach since each take
about one hour. The biggest table is 170 million rows long.

Regards, Clodoaldo Pinto