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

Re: Deadlock condition in current sources

From: "Mikheev, Vadim" <vmikheev(at)SECTORBASE(dot)COM>
To: "'Tom Lane'" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Deadlock condition in current sources
Date: 2001-12-18 19:11:55
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
> > Checkpoint' undo is not used currently so just comment out 
> > GetUndoRecPtr call in CreateCheckPoint - we'll find solution later.
> I thought about that, but figured you'd object ;-)
> One possibility is to do something you had recommended awhile back for
> other reasons: add a spinlock to each PROC structure and use the
> spinlock, rather than SInvalLock, to protect setting and reading of
> xmin, logRec, and related fields.  I haven't finished working out all
> the details, though, and this seems like a rather large change to make
> at this late stage of beta.  Comments?

Sure - *comment* out GetUndoRecPtr -:)


pgsql-hackers by date

Next:From: Mike MascariDate: 2001-12-18 19:13:15
Subject: Re: Concerns about this release
Previous:From: Tom LaneDate: 2001-12-18 19:05:43
Subject: Re: Deadlock condition in current sources

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