Re: Teaching pg_receivexlog to follow timeline switches - Mailing list pgsql-hackers

From Phil Sorber
Subject Re: Teaching pg_receivexlog to follow timeline switches
Date
Msg-id CADAkt-j2pm3bq5+EjreihE06B6gGpv_jqn3nRNvHnGScfDCjvA@mail.gmail.com
Whole thread Raw
In response to Re: Teaching pg_receivexlog to follow timeline switches  (Heikki Linnakangas <hlinnakangas@vmware.com>)
Responses Re: Teaching pg_receivexlog to follow timeline switches
List pgsql-hackers
On Fri, Jan 18, 2013 at 7:55 AM, Heikki Linnakangas
<hlinnakangas@vmware.com> wrote:
> On 18.01.2013 06:38, Phil Sorber wrote:
>> Is it possible to re-use walreceiver code from the backend?
>>
>> I was thinking that it would actually be very useful to have the whole
>> replication functionality modularized and in a standalone binary that
>> could act as a replication proxy and WAL archiver that could run
>> without all the overhead of an entire PG instance
>
>
> There's much sense in trying to extract that into a stand-along module.
> src/bin/pg_basebackup/receivelog.c is about 1000 lines of code at the
> moment, and it looks quite different from the corresponding code in the
> backend, because it doesn't have all the backend infrastructure available.
>
> - Heikki

That's fair.

What do you think about the idea of a full WAL proxy? Probably not for
9.3 at this point though.



pgsql-hackers by date:

Previous
From: Phil Sorber
Date:
Subject: Re: pg_ctl idempotent option
Next
From: Amit kapila
Date:
Subject: Re: Performance Improvement by reducing WAL for Update Operation