Hello,
thanks for comments. But what is a conclusion? Using manual vacuum is
considered as dangerous (with respect to locking) and the best is to
avoid using it? What does it mean "kick off autovacuum"? Only "cleaning
part" that needs lock will be omitted but dead tuples are freed, or
whole table
Tom Lane wrote:
> Alvaro Herrera writes:
> > An alternative solution would be to lower the vacuum delay settings before
> > starting the truncating phase, but this doesn't work very well in autovacuum
> > due to the autobalancing code (which can cause other processes to change our
> > cost delay s
Alvaro Herrera writes:
> An alternative solution would be to lower the vacuum delay settings before
> starting the truncating phase, but this doesn't work very well in autovacuum
> due to the autobalancing code (which can cause other processes to change our
> cost delay settings). This case could
Jaromír Talíř wrote:
> Alvaro Herrera píše v Čt 24. 09. 2009 v 14:41 -0400:
> > Jaromír Talíř wrote:
> >
> > > we are facing strange situation with exclusively locked table during
> > > normal lazy vacuum. There is one big table (66GB) that is heavily
> > > inserted and updated in our database. Su
Alvaro Herrera píše v Čt 24. 09. 2009 v 14:41 -0400:
> Jaromír Talíř wrote:
>
> > we are facing strange situation with exclusively locked table during
> > normal lazy vacuum. There is one big table (66GB) that is heavily
> > inserted and updated in our database. Suddenly (after backup and delete
>
Jaromír Talíř wrote:
> we are facing strange situation with exclusively locked table during
> normal lazy vacuum. There is one big table (66GB) that is heavily
> inserted and updated in our database. Suddenly (after backup and delete
> of almost all records) we are not able to run VACUUM over this
Hello,
we are facing strange situation with exclusively locked table during
normal lazy vacuum. There is one big table (66GB) that is heavily
inserted and updated in our database. Suddenly (after backup and delete
of almost all records) we are not able to run VACUUM over this table
because after 5
