Re: reducing the overhead of frequent table locks - now, with WIP patch

From: Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: reducing the overhead of frequent table locks - now, with WIP patch
Date: 2011-06-06 12:18:20
Message-ID: 4DECC58C.3010202@enterprisedb.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 06.06.2011 14:59, Robert Haas wrote:
> BTW, how do you identify from oprofile that *vxid* locks were the
> problem? I didn't think it could produce that level of detail.

It can show the call stack of each call, with --callgraph=n option,
where you can see what percentage of the calls to LockAcquire come from
VirtualXactLockTableInsert.

--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Kohei Kaigai 2011-06-06 12:37:11 [v9.2] Fix leaky-view problem, part 1
Previous Message Alexander Korotkov 2011-06-06 12:16:47 Re: WIP: Fast GiST index build