Re: Recalculating OldestXmin in a long-running vacuum - Mailing list pgsql-patches

From NikhilS
Subject Re: Recalculating OldestXmin in a long-running vacuum
Date
Msg-id d3c4af540702260536n4d689b2bw3326515c1eca52aa@mail.gmail.com
Whole thread Raw
In response to Re: Recalculating OldestXmin in a long-running vacuum  (Heikki Linnakangas <heikki@enterprisedb.com>)
List 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

pgsql-patches by date:

Previous
From: Heikki Linnakangas
Date:
Subject: Split _bt_insertonpg to two functions
Next
From: Bruce Momjian
Date:
Subject: Re: [BUGS] BUG #2969: Inaccuracies in Solaris FAQ