From: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
---|---|
To: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Streaming Replication patch for CommitFest 2009-09 |
Date: | 2009-09-18 10:09:00 |
Message-ID: | 4AB35C3C.9010301@enterprisedb.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Fujii Masao wrote:
> Hi,
>
> On Fri, Sep 18, 2009 at 2:47 PM, Heikki Linnakangas
> <heikki(dot)linnakangas(at)enterprisedb(dot)com> wrote:
>> Heikki Linnakangas wrote:
>>> I'm thinking that walreceiver should be a stand-alone program that the
>>> startup process launches, similar to how it invokes restore_command in
>>> PITR recovery. Instead of using system(), though, it would use
>>> fork+exec, and a pipe to communicate.
>> Here's a WIP patch to do that, over your latest posted patch. I've also
>> pushed this to my git repository at
>> git://git.postgresql.org/git/users/heikki/postgres.git, "replication"
>> branch.
>
> In my environment, I cannot use git protocol for some reason.
> Could you export your repository so that it can be accessed also via http?
Sure, it should be accessible via HTTP as well:
http://git.postgresql.org/git/users/heikki/postgres.git
> How should we advance development of SR?
> Should I be concentrated on the primary side, and leave the standby side to you?
> When I change something, should I make a patch for the latest SR source in your
> git repo, and submit it?
Hmm, yeah, let's do that.
Right now, I'm trying to understand the page boundary stuff and partial
page handling in ReadRecord and walsender.
--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com
From | Date | Subject | |
---|---|---|---|
Next Message | Fujii Masao | 2009-09-18 10:34:07 | Re: Streaming Replication patch for CommitFest 2009-09 |
Previous Message | Fujii Masao | 2009-09-18 09:51:51 | Re: Streaming Replication patch for CommitFest 2009-09 |