Re: reducing the overhead of frequent table locks, v4 - Mailing list pgsql-hackers

From Jeff Davis
Subject Re: reducing the overhead of frequent table locks, v4
Date
Msg-id 1310402735.3012.266.camel@jdavis
Whole thread Raw
In response to reducing the overhead of frequent table locks, v4  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: reducing the overhead of frequent table locks, v4
List pgsql-hackers
* ... It's also possible that* we're acquiring a second or third lock type on a relation we have* already locked using
thefast-path, but for now we don't worry about* that case either.*/
 

How common is that case? There are only 16 entries in the fast path lock
table, so it seems like it would frequently fill up. So, if there are
common code paths that acquire different weak locks on the same
relation, then we might commonly miss a fast-path opportunity.

One path that acquires multiple weak locks is an INSERT INTO foo
SELECT ... FROM foo ...

Is that common enough to worry about?

Regards,Jeff Davis



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Select For Update and Left Outer Join
Next
From: Gurjeet Singh
Date:
Subject: Launching debugger on self on SIGSEGV