Message-ID: <4562B9A4.4000909@bluegap.ch>
Date: Tue, 21 Nov 2006 09:32:36 +0100
From: Markus Schiltknecht <markus@bluegap.ch>
User-Agent: Icedove 1.5.0.8 (X11/20061116)
MIME-Version: 1.0
To: Bruce Momjian <bruce@momjian.us>
CC: Josh Berkus <josh@agliodbs.com>, pgsql-docs@postgresql.org,
	Jim Nasby <decibel@decibel.org>, Jeff Frost <jeff@frostconsultingllc.com>,
	Chris Browne <cbbrowne@acm.org>, sequoia@lists.forge.continuent.org
Subject: Re: [HACKERS] Replication documentation addition
References: <200611202210.kAKMA4e15035@momjian.us>
In-Reply-To: <200611202210.kAKMA4e15035@momjian.us>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Bruce Momjian wrote:
> OK, I have updated the title to be "Statement-Based Replication Using
> Middleware".  I personally think statement-based replication only makes
> sense in middleware because when you are in the backend, 

I completely agree.

> you have more
> information and can do things better, either by modifying the statement
> or passing actual data rows, like Slony does, so I want to restrict this
> to middleware like pgpool, and Usogres, which was an early
> implementation of this idea.

That's fine and reasonable.

> Am I OK now?

The title and first paragraph are fine.

I'd still say that the second paragraph, about limitations is too pgpool 
specific. How's that for sequoia?

And I'm unsure what you mean by mentioning 2PC there. Do you have to 
'make sure every transaction commits or aborts' yourself with pgpool? Or 
did you just want to mention that pgpool does (and has to do) that for you?

Regards

Markus