Re: testing ProcArrayLock patches

Kevin Grittner <kevin.grittner@wicourts.gov>

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

To: "Pavan Deolasee" <pavan.deolasee@gmail.com>

Cc: "Robert Haas" <robertmhaas@gmail.com>, <pgsql-hackers@postgresql.org>

Date: 2011-11-21T17:31:11Z

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 →

Don't elide blank lines when accumulating psql command history.
- ff4fd4bf53c5 9.2.0 cited

Pavan Deolasee <pavan.deolasee@gmail.com> wrote:

> It will be a great help if you could spare few minutes to also
> test the patch to take out the frequently accessed PGPROC members
> to a different array. We are seeing good improvements on HPUX IA
> platform and the AMD Opteron and it will be interesting to know
> what happens on the Intel platform too.
> 
>
http://archives.postgresql.org/message-id/4EB7C4C9.9070309@enterprisedb.com

It's going to be hard to arrange more of the 20-hours runs I've been
doing, but I can work in some more abbreviated tests.  What would be
the best test for this?  (I would hate to try and find out I didn't
exercise the right code path.)

-Kevin