| From: | Josh Berkus <josh(at)agliodbs(dot)com> |
|---|---|
| To: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
| Cc: | Greg Smith <greg(at)2ndquadrant(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: standby registration (was: is sync rep stalled?) |
| Date: | 2010-10-07 17:45:29 |
| Message-ID: | 4CAE0739.9030904@agliodbs.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 10/7/10 10:27 AM, Heikki Linnakangas wrote:
> The standby name is a GUC in the standby's configuration file:
>
> standby_name='bostonserver'
>
> The list of important nodes is also a GUC, in the master's configuration
> file:
>
> synchronous_standbys='bostonserver, oxfordserver'
This seems to abandon Simon's concept of per-transaction synchronization
control. That seems like such a potentially useful feature that I'm
reluctant to abandon it just for administrative elegance.
Does this work together with that in some way I can't see?
--
-- Josh Berkus
PostgreSQL Experts Inc.
http://www.pgexperts.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Josh Berkus | 2010-10-07 17:48:21 | Re: Issues with Quorum Commit |
| Previous Message | Aidan Van Dyk | 2010-10-07 17:44:43 | Re: Issues with Quorum Commit |