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

Re: Streaming replication, loose ends

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>
Cc: jd(at)commandprompt(dot)com, Bruce Momjian <bruce(at)momjian(dot)us>, Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Streaming replication, loose ends
Date: 2010-01-15 17:37:57
Message-ID: 603c8f071001150937k4dd629co6e21e5bc26afce6f@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-hackers
On Fri, Jan 15, 2010 at 12:30 PM, Heikki Linnakangas
<heikki(dot)linnakangas(at)enterprisedb(dot)com> wrote:
> Robert Haas wrote:
>> On Fri, Jan 15, 2010 at 12:17 PM, Joshua D. Drake <jd(at)commandprompt(dot)com> wrote:
>>>> Uh, do we really want to call this "replication" rather than archive log
>>>> streaming or something.  It seems "replication" is a generic term and
>>>> will confuse people who are using other replication solutions like
>>>> Slony.
>>> +1, it is not replication. I would call it something like continuous
>>> archiving or streaming pitr
>>
>> Of course "PITR" does stand for "point-in-time replication"...
>
> I'm not sure if you're joking, but PITR actually stands for
> Point-In-Time *Recovery*.

Oops.  No, not joking, just wrong.

But I'm still wondering why this isn't replication.

...Robert

In response to

Responses

pgsql-hackers by date

Next:From: David E. WheelerDate: 2010-01-15 17:43:22
Subject: Re: Streaming replication, loose ends
Previous:From: Joshua D. DrakeDate: 2010-01-15 17:34:26
Subject: Re: Streaming replication, loose ends

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