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-17 12:02:29 |
Message-ID: | 4B2A1DD5.1050506@enterprisedb.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Fujii Masao wrote:
> On Wed, Dec 16, 2009 at 6:53 PM, Heikki Linnakangas
> <heikki(dot)linnakangas(at)enterprisedb(dot)com> wrote:
>> 0. Begin by connecting to the master just like a normal backend does. We
>> don't necessarily need the new ProtocolVersion code either, though it's
>> probably still a good idea to reject connections to older server versions.
>
> And, I think that such backend should switch to walsender mode when the startup
> packet arrives. Otherwise, we would have to authenticate such backend twice
> on different context, i.e., a normal backend and walsender. So the settings for
> each context would be required in pg_hba.conf. This is odd, I think. Thought?
True.
>> This is identical to what happens when a query is executed against a
>> normal backend using the simple query protocol, so walsender can use
>> PQexec() for this.
>
> s/walsender/walreceiver ?
Right.
--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com
From | Date | Subject | |
---|---|---|---|
Next Message | Fujii Masao | 2009-12-17 13:00:55 | Re: Streaming replication and non-blocking I/O |
Previous Message | Simon Riggs | 2009-12-17 11:36:21 | Re: Hot Standby and prepared transactions |