Re: Fix of doc for synchronous_standby_names. - Mailing list pgsql-hackers

From Robert Haas
Subject Re: Fix of doc for synchronous_standby_names.
Date
Msg-id CA+TgmoZLgs7_Lex4R3Q23Geo6BTfVEM-0Hm1HKhJzM1gxBFUJA@mail.gmail.com
Whole thread Raw
In response to Re: Fix of doc for synchronous_standby_names.  (Amit Langote <Langote_Amit_f8@lab.ntt.co.jp>)
Responses Re: Fix of doc for synchronous_standby_names.  (Kyotaro HORIGUCHI <horiguchi.kyotaro@lab.ntt.co.jp>)
List pgsql-hackers
On Thu, Apr 21, 2016 at 1:01 AM, Amit Langote
<Langote_Amit_f8@lab.ntt.co.jp> wrote:
> ISTM, the sentence describes what happens in a *single instance* of
> encountering duplicate (same name found in primary_conninfo of 2 or more
> standbys).  It's still one name but which of the standbys claims the spot
> (for that name) of being a synchronous standby with given priority is
> indeterminate.
>
> Now, there can be multiple instances of encountering duplicates, each for
> a different sync slot.  But this particular sentence seems to be talking
> about what's the case for any given slot.

Right, that's my reading also.

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



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: Description of ForeignPath
Next
From: Robert Haas
Date:
Subject: Re: max_parallel_degree > 0 for 9.6 beta