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

Optimizing GetRunningTransactionLocks()

From: Simon Riggs <simon(at)2ndQuadrant(dot)com>
To: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Optimizing GetRunningTransactionLocks()
Date: 2011-10-31 20:15:54
Message-ID: CA+U5nM+rg30qEhkf2=rDXt42X7onYSRcfh3Qvu5gpkb0pv1meQ@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-hackers
My list of things to do included optimising
GetRunningTransactionLocks(), run once per checkpoint.

I was thinking I needed to try harder to avoid acquiring LWlocks on
all the lock partitions.

ISTM that I don't need to do this - lwlocks on lock partitions are
almost never contended now, so this should go much faster than before.

Any thoughts? Do we think it would benefit from further tweaking?

I'll assume not unless I hear from somebody with a different idea.

-- 
 Simon Riggs                   http://www.2ndQuadrant.com/
 PostgreSQL Development, 24x7 Support, Training & Services

Responses

pgsql-hackers by date

Next:From: Simon RiggsDate: 2011-10-31 20:18:26
Subject: Re: myProcLocks initialization
Previous:From: Tom LaneDate: 2011-10-31 20:03:47
Subject: Re: myProcLocks initialization

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