From: | otheus uibk <otheus(dot)uibk(at)gmail(dot)com> |
---|---|
To: | Stas Kelvich <s(dot)kelvich(at)postgrespro(dot)ru> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: async replication code |
Date: | 2016-03-16 19:30:57 |
Message-ID: | CALbQNd2JOMsyE1HUsfYbN8Nt_cz0_ENByQxGzW625RdQCYo-4Q@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
I will ask again: where in the code is the asynchronous replication code?
The docs are not detailed/exact enough.
> > Main question: I want to understand very precisely the exact algirithm
> used in PG to do asynchronous streaming replication. Eg, I want to know how
> the record is written and flushed to the socket and how that happens in
> time w.r.t WAL-to-disk and response to client. Will someone please give me
> a head start as to where to begin my code-spelunking?
> >
>
> WAL synced to disc, then everything else is happening.
>
>
> http://www.postgresql.org/docs/9.5/static/warm-standby.html#STREAMING-REPLICATION
>
> ---
> Stas Kelvich
> Postgres Professional: http://www.postgrespro.com
> Russian Postgres Company
>
>
--
Otheus
otheus(dot)uibk(at)gmail(dot)com
otheus(dot)shelling(at)uibk(dot)ac(dot)at
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2016-03-16 19:39:47 | Re: [PATCH] Integer overflow in timestamp[tz]_part() and date/time boundaries check |
Previous Message | Andres Freund | 2016-03-16 19:25:37 | Re: Performance degradation in commit ac1d794 |