From: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
---|---|
To: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Streaming replication and non-blocking I/O |
Date: | 2009-12-21 17:26:16 |
Message-ID: | 4B2FAFB8.3060603@enterprisedb.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Fujii Masao wrote:
> On Fri, Dec 18, 2009 at 11:42 AM, Fujii Masao <masao(dot)fujii(at)gmail(dot)com> wrote:
>> Okey. Design clarification again;
>>
>> 0. Begin by connecting to the master using PQconnectdb() with new conninfo
>> option specifying the request of replication. The startup packet with the
>> request is sent to the master, then the backend switches to the walsender
>> mode. The walsender goes into the main loop and wait for the request from
>> the walreceiver.
> <snip>
>> 4. Start replication
>>
>> Slave -> Master: Query message, with query string "START REPLICATION:
>> XXXX", where XXXX is the RecPtr of the starting point.
>>
>> Master -> Slave: CopyOutResponse followed by a continuous stream of
>> CopyData messages with WAL contents.
>
> Done. Currently there is no new libpq function for replication. The
> walreceiver uses only existing functions like PQconnectdb, PQexec,
> PQgetCopyData, etc.
Ok thanks, sounds good, I'll take a look.
--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com
From | Date | Subject | |
---|---|---|---|
Next Message | Heikki Linnakangas | 2009-12-21 17:31:01 | Re: Streaming replication and non-blocking I/O |
Previous Message | Greg Smith | 2009-12-21 17:02:02 | Re: Table size does not include toast size |