Skip site navigation (1) Skip section navigation (2)

Re: Re: [COMMITTERS] pgsql: Augment WAL records for btree delete with GetOldestXmin() to

From: Simon Riggs <simon(at)2ndQuadrant(dot)com>
To: Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Re: [COMMITTERS] pgsql: Augment WAL records for btree delete with GetOldestXmin() to
Date: 2010-03-09 13:06:32
Message-ID: 1268139992.3825.6.camel@ebony (view raw or flat)
Thread:
Lists: pgsql-committerspgsql-hackers
On Tue, 2010-03-09 at 11:20 +0200, Heikki Linnakangas wrote:
> Simon Riggs wrote:
> > XLOG_BTREE_DELETE records would not carry latestRemovedXid, this would
> > be calculated by inspection of heap tuples.
> 
> You might still want to keep the conservative latestRemovedXid value in
> the WAL record to avoid the extra work when latestRemovedXid alone allows.

OK will do.

-- 
 Simon Riggs           www.2ndQuadrant.com


In response to

pgsql-hackers by date

Next:From: Pavel StehuleDate: 2010-03-09 14:30:58
Subject: patch (for 9.1) string functions
Previous:From: Michael MeskesDate: 2010-03-09 11:10:26
Subject: Re: ECPG, two varchars with same name on same line

pgsql-committers by date

Next:From: Alvaro HerreraDate: 2010-03-09 14:27:28
Subject: pgsql: Update time zone data files to tzdata release 2010d: DST law
Previous:From: Michael MeskesDate: 2010-03-09 11:09:46
Subject: pgsql: ecpg now adds a unique counter to its varchar struct definitions

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group