Skip site navigation (1) Skip section navigation (2)

Re: Sync Rep and shutdown Re: Sync Rep v19

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Yeb Havinga <yebhavinga(at)gmail(dot)com>
Cc: Simon Riggs <simon(at)2ndquadrant(dot)com>, Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, Jaime Casanova <jaime(at)2ndquadrant(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Sync Rep and shutdown Re: Sync Rep v19
Date: 2011-03-21 01:05:48
Message-ID: AANLkTi=sv3xF=nBWAM6DfcM3f86ZVhC_cJQC_CJ8+2ak@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-hackers
On Sun, Mar 20, 2011 at 11:03 AM, Yeb Havinga <yebhavinga(at)gmail(dot)com> wrote:
> 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.

Thanks!  The things I'd like to see compared are:

- performance as of commit e148443ddd95cd29edf4cc1de6188eb9cee029c5
- performance as of current git master
- performance as of current git master with
sync-standbys-defined-rearrangement applied

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Responses

pgsql-hackers by date

Next:From: Peter GeogheganDate: 2011-03-21 01:47:18
Subject: Re: pl/python tracebacks v2
Previous:From: Noah MischDate: 2011-03-21 00:14:21
Subject: Re: maximum digits for NUMERIC

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group