Horton

Re: testing ProcArrayLock patches

Kevin Grittner <kevin.grittner@wicourts.gov>

View thread
From: "Kevin Grittner" <Kevin.Grittner@wicourts.gov>
To: "anarazel@anarazel.de" <andres@anarazel.de>, "Robert Haas" <robertmhaas@gmail.com>, "Kevin Grittner" <Kevin.Grittner@wicourts.gov>
Cc: <pgsql-hackers@postgresql.org>
Date: 2011-11-18T19:36:59Z
Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

  1. Don't elide blank lines when accumulating psql command history.

"Kevin Grittner" <Kevin.Grittner@wicourts.gov> wrote:

> samples  %        image name      symbol name
> 495463    3.6718  postgres        hash_search_with_hash_value
 
When lines like these show up in the annotated version, I'm
impressed that we're still finding gains as big as we are:
 
 44613  0.3306 :        if (segp == NULL)
               :                hash_corrupted(hashp);
 
101910  0.7552 :        keysize = hashp->keysize;       /* ditto */
 
There goes over 1% of my server run time, right there!
 
Of course, these make no sense unless there is cache line
contention, which is why that area is bearing fruit.
 
-Kevin