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

Re: Dead Space Map

From: Greg Stark <gsstark(at)mit(dot)edu>
To: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
Cc: Greg Stark <gsstark(at)mit(dot)edu>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Jim C(dot) Nasby" <jnasby(at)pervasive(dot)com>, Heikki Linnakangas <hlinnaka(at)iki(dot)fi>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Dead Space Map
Date: 2006-02-28 19:25:12
Message-ID: 87hd6jwajr.fsf@stark.xeocode.com (view raw or flat)
Thread:
Lists: pgsql-hackers
Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:

> Greg Stark wrote:
> > 
> > If you commit each update then your tuple might well be visible to other
> > transactions, how would you check that?
> 
> You check the xmin/xmax using standard visibility rules.

Would that really find anything? Even putting aside your own transaction
wouldn't it pick up any older transaction that started before yours and is
still running? They can't really see it but short of actually looking at their
snapshots I don't think you can determine that.

-- 
greg


In response to

pgsql-hackers by date

Next:From: Tom LaneDate: 2006-02-28 19:45:05
Subject: Re: Zeroing damaged pages
Previous:From: John DeSoiDate: 2006-02-28 18:52:48
Subject: Re: character encoding in StartupMessage

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