Re: GSoC 2018 - Mailing list pgsql-hackers

From Arseny Sher
Subject Re: GSoC 2018
Date
Msg-id 878te4gkjk.fsf@ars-thinkpad
Whole thread Raw
In response to Re: GSoC 2018  (Aleksander Alekseev <a.alekseev@postgrespro.ru>)
List pgsql-hackers
Aleksander Alekseev <a.alekseev@postgrespro.ru> writes:

> Hi Stephen,
>
>> synchronous_commit isn't the same as synchronous_standby_names ...
>
> What about synchronous_standby_names? Logical replication ignores it and
> doesn't wait for ack's from replicas or something?

It actually works, see [1]:

The name of a standby server for this purpose is the application_name
setting of the standby, as set in the standby's connection
information. In case of a physical replication standby, this should be
set in the primary_conninfo setting in recovery.conf; the default is
walreceiver. For logical replication, this can be set in the connection
information of the subscription, and it defaults to the subscription
name.

[1] https://www.postgresql.org/docs/current/static/runtime-config-replication.html

--
Arseny Sher
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Company 


pgsql-hackers by date:

Previous
From: Maksim Milyutin
Date:
Subject: [HACKERS] wrong t_bits alignment in pageinspect
Next
From: Alex Kliukin
Date:
Subject: Re: GSoC 2018