Skip site navigation (1) Skip section navigation (2)

Re: Teaching pg_receivexlog to follow timeline switches

From: Phil Sorber <phil(at)omniti(dot)com>
To: Heikki Linnakangas <hlinnakangas(at)vmware(dot)com>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Teaching pg_receivexlog to follow timeline switches
Date: 2013-01-21 15:58:22
Message-ID: CADAkt-j2pm3bq5+EjreihE06B6gGpv_jqn3nRNvHnGScfDCjvA@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-hackers
On Fri, Jan 18, 2013 at 7:55 AM, Heikki Linnakangas
<hlinnakangas(at)vmware(dot)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.


In response to

Responses

pgsql-hackers by date

Next:From: Amit kapilaDate: 2013-01-21 16:02:14
Subject: Re: Performance Improvement by reducing WAL for Update Operation
Previous:From: Phil SorberDate: 2013-01-21 15:54:41
Subject: Re: pg_ctl idempotent option

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group