I think this patch needs to be revisited in the light of the work I just
did to make pgstats correctly track the effects of aborted transactions.
It seems fairly likely to me that most of the problem you were seeing
was actually due to that stupidity, and not to race conditions between
VACUUM and concurrent transactions. So maybe we no longer need to do
It might be worth fixing things so that a VACUUM sets n_dead_tuples to
the number of deleted-but-not-removable tuples it saw, rather than
always setting to zero as is presently done.
regards, tom lane
In response to
pgsql-hackers by date
|Next:||From: Matthew O'Connor||Date: 2007-05-27 04:44:15|
|Subject: Re: Autovacuum versus rolled-back transactions|
|Previous:||From: Jaime Casanova||Date: 2007-05-26 23:34:29|
|Subject: Re: Reviewing temp_tablespaces GUC patch|