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

Re: advancing snapshot's xmin

From: Neil Conway <neilc(at)samurai(dot)com>
To: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
Cc: Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: advancing snapshot's xmin
Date: 2008-03-25 22:40:13
Message-ID: 1206484813.32670.7.camel@goldbach (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
On Tue, 2008-03-25 at 17:26 -0300, Alvaro Herrera wrote:
> There is one hole here: contention on ProcArrayLock.  Basically, for
> simple transactions we will need to update MyProc after every command.

If we're just updating MyProc->xmin, we only need to acquire
ProcArrayLock in shared mode, right?

> Another idea is to throttle the updating of Xmin so it only happens once
> in a while, but it's difficult to find a useful criterion and avoid
> falling into the trap that we just neglected to update it before a large
> command.

Using LWLockConditionalAcquire() might help also.


In response to


pgsql-hackers by date

Next:From: Tom LaneDate: 2008-03-25 22:48:04
Subject: Re: [PATCHES] Text <-> C string
Previous:From: Richard BroersmaDate: 2008-03-25 22:32:57
Subject: Re: PostgreSQL Replication with read-only access to standby DB

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