Re: VACUUM/t_ctid bug (was Re: GiST concurrency commited) - Mailing list pgsql-hackers

From Tom Lane
Subject Re: VACUUM/t_ctid bug (was Re: GiST concurrency commited)
Date
Msg-id 22915.1124547958@sss.pgh.pa.us
Whole thread Raw
In response to Re: VACUUM/t_ctid bug (was Re: GiST concurrency commited)  (Gavin Sherry <swm@linuxworld.com.au>)
Responses Re: VACUUM/t_ctid bug (was Re: GiST concurrency commited)  (Gavin Sherry <swm@linuxworld.com.au>)
List pgsql-hackers
Gavin Sherry <swm@linuxworld.com.au> writes:
> I've written some quick scripts. One just vacuums constantly (999 vacuums
> to 1 vacuum full) while three other scripts three randomly insert
> into, update and delete from 3 tables. There's a mix of small and large
> transactions. The tables have a single int column. It is set up to run 3
> million transactions across the 3 scripts.

Note that since the issues have mainly to do with update chains, it'd be
good to stress cases where a row is updated multiple times before being
deleted.  And use at least one long-running transaction, so that VACUUM
can't just throw away the update chain.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: Why is lock not released?
Next
From: Tom Lane
Date:
Subject: Re: Why is lock not released?