Remaining VACUUM patches

From: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
To: Hackers <pgsql-hackers(at)postgresql(dot)org>
Cc: heikki(at)enterprisedb(dot)com, itagaki(dot)takahiro(at)oss(dot)ntt(dot)co(dot)jp
Subject: Remaining VACUUM patches
Date: 2007-04-18 21:46:56
Message-ID: 20070418214655.GI19598@alvh.no-ip.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

There are two additional patches in the VACUUM code. One is Heikki's
patch to recalculate OldestXmin in the vacuum run.

http://groups.google.es/group/pgsql.patches/browse_thread/thread/b2cfc901534d8990/40ba5b2fbb8f5b91
(much nicer than our archives because the whole thread is there, not
just month-sized pieces).

That thread ended without any conclusion; it is said that the patch will
be reconsidered when Simon Riggs' patch about the WAL flushing bug
lands, but I don't know what patch is that. Is it in the patch queue?
Was it already applied?

The problem with the patch is that the DBT-2 test showed decreased
performance, but that was still under investigation.

What is the status of this?

The other patch was ITAGAKI Takahiro's patch to fix n_dead_tuples in
pgstats after VACUUM when there is concurrent update activity. This
patch is still on hold largely because the above patch would cause it to
be a bit obsolete. So I think if we're not going to apply the former,
we should apply this one.

http://archives.postgresql.org/pgsql-hackers/2007-02/msg00051.php

http://archives.postgresql.org/pgsql-patches/2007-02/msg00021.php

Comments?

--
Alvaro Herrera http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Islam Hegazy 2007-04-18 22:01:46 Re: modifying the table function
Previous Message Alvaro Herrera 2007-04-18 19:22:44 Re: Hacking on PostgreSQL via GIT