Alexander Korotkov deals with hot page issues:
When many sessions try to insert into the same B-tree leaf page, classic exclusive page locking serializes progress and wastes time on sleep/wake cycles. We’re introducing a batch page insertion path that lets the session holding the page lock insert for itself and its neighbors. The result: dramatically reduced lock waits, and big gains at high client counts (2X throughput boost starting from 64 clients in our benchmark).
Click through to see how it differs from normal PostgreSQL behavior on what is one of the more common performance problems on busy OLTP systems.