Horton

Re: Sync Rep and shutdown Re: Sync Rep v19

Yeb Havinga <yebhavinga@gmail.com>

View thread
From: Yeb Havinga <yebhavinga@gmail.com>
To: Robert Haas <robertmhaas@gmail.com>
Cc: Simon Riggs <simon@2ndquadrant.com>, Fujii Masao <masao.fujii@gmail.com>, Jaime Casanova <jaime@2ndquadrant.com>, PostgreSQL-development <pgsql-hackers@postgresql.org>
Date: 2011-03-20T15:03:04Z
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. Document guc context values, and reference them from the config doc section.

On 2011-03-20 05:44, Robert Haas wrote:
>
> Hmm, I'm not going to be able to reproduce this here, and my test
> setup didn't show a clear regression.  I can try beating on it some
> more, but...  Any chance you could rerun your test with the latest
> master-branch code, and perhaps also with the patch I proposed
> upthread to remove a branch from the section protection by
> SyncRepLock?  I can't really tell from reading the emails you linked
> what was responsible for the slowdowns and speedups, and it is unclear
> to me how much impact my recent changes actually had.
No problem. Could you tell me the name of the "remove a branch from the 
section protection by SyncRepLock" ? patch, or perhaps a message-link? 
Upthread I see sync-standbys-defined-rearrangement.patch but also two 
sync-rep-wait-fixes.

regards,
Yeb Havinga