Re: Vacuum improvement - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Vacuum improvement
Date
Msg-id 24055.1034777854@sss.pgh.pa.us
Whole thread Raw
In response to Re: Vacuum improvement  (Hannu Krosing <hannu@tm.ee>)
List pgsql-hackers
Hannu Krosing <hannu@tm.ee> writes:
> meaning to VACUUM FULL the whole table, but to work in small chunks and
> relaese all locks and let others access the tables between these ?

AFAICS this is impossible for VACUUM FULL.  You can't let other accesses
in and then resume processing, because that invalidates all the state
you have about where to put moved tuples.

But the whole point of developing non-FULL vacuuming was to make
something that could be run concurrently with other stuff.  I fail
to see the point of insisting that frequent vacuums be FULL.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: droped out precise time calculations in src/interfaces/libpq/fe-connect.c
Next
From: Greg Copeland
Date:
Subject: Re: Postgresql and multithreading