| From: | Josh Berkus <josh(at)berkus(dot)org> |
|---|---|
| To: | Amit Langote <amitlangote09(at)gmail(dot)com> |
| Cc: | PostgreSQL Advocacy <pgsql-advocacy(at)postgresql(dot)org> |
| Subject: | Re: Assembling "top features" list for beta announcement |
| Date: | 2017-04-07 20:23:04 |
| Message-ID: | 44c77827-bca7-e0bd-3d54-edad65dd4391@berkus.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-advocacy |
On 04/07/2017 12:30 PM, Amit Langote wrote:
> On Sat, Apr 8, 2017 at 1:39 AM, Josh Berkus <josh(at)berkus(dot)org> wrote:
>>
>> It looks like quorum sync rep won't make it, correct?
>>
>
> Quorum sync rep will be there. See:
>
> https://www.postgresql.org/docs/devel/static/runtime-config-replication.html#runtime-config-replication-master
>
> "The keyword ANY, coupled with num_sync, specifies a quorum-based
> synchronous replication and makes transaction commits wait until their
> WAL records are replicated to at least num_sync listed standbys. For
> example,..."
Ah, I misunderstood some of the comments on the patch!
That's good news, that's a 3rd banner feature.
--
Josh Berkus
Containers & Databases Oh My!
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2017-04-07 21:42:32 | Re: Assembling "top features" list for beta announcement |
| Previous Message | Amit Langote | 2017-04-07 19:30:14 | Re: Assembling "top features" list for beta announcement |