Re: update functions locking tables

On Tue, Aug 30, 2005 at 10:18:20AM -0300, Clodoaldo Pinto wrote:
> 30 Aug 2005 09:10:51 -0400, Greg Stark <gsstark@mit.edu>:

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

Even if you cluster/vacuum only the just-loaded table?

> The biggest table is 170 million rows long.

I hope this is not the one you are loading daily ...

--
Alvaro Herrera <alvherre[]alvh.no-ip.org>      Architect, www.EnterpriseDB.com
"El destino baraja y nosotros jugamos" (A. Schopenhauer)