Re: More vacuum.c refactoring - Mailing list pgsql-hackers

From Tom Lane
Subject Re: More vacuum.c refactoring
Date
Msg-id 19783.1086931715@sss.pgh.pa.us
Whole thread Raw
In response to Re: More vacuum.c refactoring  (Alvaro Herrera <alvherre@dcc.uchile.cl>)
List pgsql-hackers
Alvaro Herrera <alvherre@dcc.uchile.cl> writes:
> Maybe we could establish heavier testing for this kind of change so
> potential patches can be tested extensively.  Concurrent vacuums with
> all kinds of imaginable operations (insert, updates, deletes), in tight
> loops, could be a start.

VACUUM FULL takes an exclusive lock, so it should not have to worry
about concurrent operations on the table.  What we have to think about
is the initial states it can see.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: More vacuum.c refactoring
Next
From: Michael Glaesemann
Date:
Subject: Re: [COMMITTERS] pgsql-server: Clean up generation of default