| From: | otheus uibk <otheus(dot)uibk(at)gmail(dot)com> |
|---|---|
| To: | pgsql-hackers(at)postgresql(dot)org, Stas Kelvich <s(dot)kelvich(at)postgrespro(dot)ru> |
| Subject: | Re: async replication code |
| Date: | 2016-03-16 19:43:16 |
| Message-ID: | CALbQNd1nJrBqHcX70VpAFC3GeWA1ENQ_Qu3QDCUS93wuDY16Uw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Mar 16, 2016 at 8:30 PM, otheus uibk <otheus(dot)uibk(at)gmail(dot)com> wrote:
> I will ask again: where in the code is the asynchronous replication code?
> The docs are not detailed/exact enough.
>
>
Nevermind. Thomas Munro answered my question in the General list. Quoting:
> Look for WalSndWakeupRequest() in xlog.c, which expands to a call to
> WalSndWakeup in walsender.c which sets latches (= a mechanism for
> waking processes) on all walsenders, and see the WaitLatchOrSocket
> calls in walsender.c which wait for that to happen.
--
Otheus
otheus(dot)uibk(at)gmail(dot)com
otheus(dot)shelling(at)uibk(dot)ac(dot)at
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jim Nasby | 2016-03-16 19:53:40 | Re: plpgsql - DECLARE - cannot to use %TYPE or %ROWTYPE for composite types |
| Previous Message | Robert Haas | 2016-03-16 19:41:28 | Re: Performance degradation in commit ac1d794 |