2010/12/7 Robert Haas <robertmhaas@xxxxxxxxx>: > 2010/12/7 Віталій Тимчишин <tivv00@xxxxxxxxx>: >> As far as I can see from the source, there is a lot of code executed under >> the partition lock protection, like two hash searches (and possibly >> allocations). > > Yeah, that was my concern, too, though Tom seems skeptical (perhaps > rightly). And I'm not really sure why the PROCLOCKs need to be in a > hash table anyway - if we know the PROC and LOCK we can surely look up > the PROCLOCK pretty expensively by following the PROC SHM_QUEUE. Err, pretty INexpensively. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-performance mailing list (pgsql-performance@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-performance
