Re: Recalculating OldestXmin in a long-running vacuum

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

Hi,

I was wondering if we can apply the same logic of recalculating OldestXmin
within IndexBuildHeapScan which occurs as part of create index operation?

Having to index lesser number of tuples should be a good save in the "CREATE
INDEX CONCURRENTLY" case, if the above is possible?

Regards,
Nikhils
--
EnterpriseDB http://www.enterprisedb.com

In response to

Browse pgsql-patches by date

  From Date Subject
Next Message Bruce Momjian 2007-02-26 15:21:23 Re: BUG #2969: Inaccuracies in Solaris FAQ
Previous Message Heikki Linnakangas 2007-02-26 10:13:20 Split _bt_insertonpg to two functions