Re: Sync Rep: First Thoughts on Code

From: Aidan Van Dyk <aidan(at)highrise(dot)ca>
To: Simon Riggs <simon(at)2ndQuadrant(dot)com>
Cc: Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Sync Rep: First Thoughts on Code
Date: 2008-12-11 15:09:47
Message-ID: 20081211150947.GY26596@yugib.highrise.ca
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

* Simon Riggs <simon(at)2ndQuadrant(dot)com> [081211 10:03]:

> Sending data twice is not a requirement I ever heard expressed, nor has
> the lack of ability to send it twice been voiced as a criticism for any
> form of replication I'm familiar with. Ask the DRBD guys if sending data
> twice is necessary or required to make replication work.
>
> If multiple people think its a good idea then I respect your choice of
> option.
>
> But I also think that many or perhaps most people will choose not to
> send data twice and I respect that choice of option also.

Well, PostgreSQL has WAL, so we've already accepted the notion of "send
data twice" being useful sometimes...

But I would note that the "archive" and "streaming" are both sending the
data *different* places... or at least, in my case would be...

And, also, I know WAL archiving isn't necessary for replication to work.
but it's necessary for me to sleep comfortably at night ;-)

I'm just suprised that people are willing to throw away their
backup/PITR archiving once they have a singl "live slave" up.

a.

--
Aidan Van Dyk Create like a god,
aidan(at)highrise(dot)ca command like a king,
http://www.highrise.ca/ work like a slave.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Pavel Stehule 2008-12-11 15:11:28 Re: WIP: default values for function parameters
Previous Message Tom Lane 2008-12-11 15:09:25 Re: Updates of SE-PostgreSQL 8.4devel patches (r1268)