Horton

Re: testing ProcArrayLock patches

Kevin Grittner <kevin.grittner@wicourts.gov>

View thread
From: "Kevin Grittner" <Kevin.Grittner@wicourts.gov>
To: "Andres Freund" <andres@anarazel.de>
Cc: "Robert Haas" <robertmhaas@gmail.com>, <pgsql-hackers@postgresql.org>
Date: 2011-11-18T23:18:07Z
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.

Attachments

Andres Freund <andres@anarazel.de> wrote:
 
> I think opannotate -a -s produces output with instructions/code
> intermingled.
 
Thanks.  I'll check out perf later (thanks for the tips!), but for
now, here's the function which was at the top of my oprofile
results, annotated with those options.  I'm afraid it's a bit
intimidating to me -- the last time I did much with X86 assembly
language was in the mid-80s, on an 80286.  :-/  Hopefully, since
this is at the top of the oprofile results when running with
prepared statements, it will be of use to somebody.
 
The instructions which are shown as having that 1% still seem odd to
me, but as you say, they were probably actually waiting for some
previous operation to finish:
 
 43329  0.3211 :  70b56a:	test   %rbp,%rbp
 
 99903  0.7404 :  70b58a:	mov    %rax,0x18(%rsp)
 
If anyone wants any other detail from what I captured, let me know.
 
-Kevin