From: | Jaime Casanova <jaime(at)2ndquadrant(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>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Sync Rep v19 |
Date: | 2011-03-05 22:10:29 |
Message-ID: | AANLkTimic_A7nMZ5mS2Au+UqBWWwp-8o+v8nezcW9-if@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Sat, Mar 5, 2011 at 3:11 PM, Yeb Havinga <yebhavinga(at)gmail(dot)com> wrote:
>
> Summary of preliminary testing:
> 1) it is confusing to show messages/ contents of stat_replication that hints
> at syncrep, when synchronous_replication is on.
[for the record, Yeb explain he means OFF not on...]
the thing is that once you put a server name in
synchronous_standby_names that standby is declared to be synchronous
and because synchronous_replication can change at any time for any
given backend we need to know priority of any declared sync standby.
if you want pure async standbys remove their names from
synchronous_standby_names
> 2) should guc settings for synchronous_replication be changed so it can only
> be set in the config file, and hence only change with reload_conf()?
no. the thing is that we can determine for which data we want to pay
the price of synchrony and for which data don't
> 3) speed is comparable to v17 :-)
>
yeah... it's a lot better than before, good work Simon :)
--
Jaime Casanova www.2ndQuadrant.com
Professional PostgreSQL: Soporte y capacitación de PostgreSQL
From | Date | Subject | |
---|---|---|---|
Next Message | David E. Wheeler | 2011-03-05 22:20:37 | Re: Alpha4 release blockers (was Re: wrapping up this CommitFest) |
Previous Message | Peter Eisentraut | 2011-03-05 20:19:39 | Re: Alpha4 release blockers (was Re: wrapping up this CommitFest) |