On Fri, 2008-03-28 at 11:26 -0300, Alvaro Herrera wrote:
> Simon Riggs wrote:
> > On Fri, 2008-03-28 at 10:35 -0300, Alvaro Herrera wrote:
> > 
> > > The problem is that we always consider every transaction's PGPROC->xid
> > > in calculating MyProc->xmin.  So if you have a long running
> > > transaction, it doesn't matter how far beyond the snapshots are -- the
> > > value returned by GetOldestXmin will always be at most the old
> > > transaction's Xid.  Even if that transaction cannot see the old rows
> > > because all of its snapshots are way in the future.
> > 
> > It may not have a TransactionId yet.
> 
> How is this a problen?  If it ever gets one, it will be in the future.

Yeh, that was my point. So the problem you mention mostly goes away.

-- 
  Simon Riggs
  2ndQuadrant  http://www.2ndQuadrant.com 

  PostgreSQL UK 2008 Conference: http://www.postgresql.org.uk

In response to

• Re: advancing snapshot's xmin at 2008-03-28 14:26:34 from Alvaro Herrera

pgsql-hackers by date

Next:	From: Suresh	Date: 2008-03-28 14:54:03
	Subject: segfault in locking code
Previous:	From: Aidan Van Dyk	Date: 2008-03-28 14:44:57
	Subject: Re: Status of GIT mirror (Was having problem in rsync'ing cvs)