Horton

Re: testing ProcArrayLock patches

Kevin Grittner <kevin.grittner@wicourts.gov>

View thread
From: "Kevin Grittner" <Kevin.Grittner@wicourts.gov>
To: "Robert Haas" <robertmhaas@gmail.com>
Cc: <pgsql-hackers@postgresql.org>
Date: 2011-11-18T18:14:56Z
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.

Robert Haas <robertmhaas@gmail.com> wrote:
 
> Yeah, I'd just drop -S.
 
Easily done.
 
> Make sure to use -c N -j N with pgbench, or you'll probably not be
> able to saturate it.
 
Yeah, that's part of the script I copied from you.
 
> I've also had good luck with wal_writer_delay=20ms, although if
> you have synchronous_commit=on that might not matter, and it's
> much less important since Simon's recent patch in that area went
> in.
 
What the heck; will do.
 
> What scale factor are you testing at?
 
100.  Perhaps I should boost that since I'm going as far as 128
clients?
 
-Kevin