Re: Recalculating OldestXmin in a long-running vacuum

From: Heikki Linnakangas <heikki(at)enterprisedb(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Bruce Momjian <bruce(at)momjian(dot)us>, pgsql-patches(at)postgresql(dot)org, Gregory Stark <gsstark(at)mit(dot)edu>, ITAGAKI Takahiro <itagaki(dot)takahiro(at)oss(dot)ntt(dot)co(dot)jp>
Subject: Re: Recalculating OldestXmin in a long-running vacuum
Date: 2007-03-27 17:26:38
Message-ID: 460953CE.6010504@enterprisedb.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-patches

Tom Lane wrote:
> Heikki Linnakangas <heikki(at)enterprisedb(dot)com> writes:
>> Maybe we should keep this issue open until we resolve the vacuum WAL
>> flush issue? I can then rerun the same tests to see if this patch is a
>> win after that.
>
> Sounds like a plan, if you are willing to do that.

Sure, just rerunning the same tests isn't much work.

Bruce Momjian wrote:
> Would you like to add a TODO item?

I don't know how we track things like this. Maybe add to the end of the
patch queue, with link to this discussion so that we remember that it
needs more testing?

--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com

In response to

Responses

Browse pgsql-patches by date

  From Date Subject
Next Message Bruce Momjian 2007-03-27 17:27:42 Re: [pgsql-patches] pg_get_domaindef
Previous Message Tom Lane 2007-03-27 17:19:25 Re: Recalculating OldestXmin in a long-running vacuum