Dimitri Fontaine wrote:
Hi,
Le 25 juin 09 à 11:26, Jasen Betts a écrit :
On 2009-06-23, Mike Christensen wrote:
Does anyone actually have that (any node
can go down and the others still replicate amongst themselves?)
you are describing usenet. (it was not designed for relational database
r
Craig Ringer wrote:
On Mon, 2009-06-22 at 22:20 -0400, Gerry Reno wrote:
Here is a link that describes the technique:
http://www.onlamp.com/pub/a/onlamp/2006/04/20/advanced-mysql-replication.html?page=1
Ah. You were referring to multiple-master replication, and your
reference to
Craig Ringer wrote:
On Mon, 2009-06-22 at 21:29 -0400, Gerry Reno wrote:
I don't know how it could guarantee that. That's really why row-based
is better.
Yep, especially in the face of things like user PL functions, C
functions, etc.
This page:
http://dev.mysql.com/doc/
Craig Ringer wrote:
On Mon, 2009-06-22 at 20:48 -0400, Gerry Reno wrote:
Anyway, you seem to be unaware that built-in replication for
PostgreSQL already is moving along, with an implementation that's just
not quite production quality yet, and might make into the next version
after 8
Greg Smith wrote:
On Mon, 22 Jun 2009, Gerry Reno wrote:
We need something as good as MySQL Replication.
I certainly hope not, I was hoping for a reliable replication solution
instead. Wow is the information you get searching for something like
"mysql replication corruption [replay lo
Joshua D. Drake wrote:
On Mon, 2009-06-22 at 18:35 -0400, Gerry Reno wrote:
Joshua D. Drake wrote:
It is true. Otherwise show me a viable replication offering for
postgresql that I can put into production and obtain support for it.
Well, you can get support for Slony
Joshua D. Drake wrote:
On Mon, 2009-06-22 at 18:28 -0400, Gerry Reno wrote:
Kevin Barnard wrote:
Have you ever tried any of the postgresql replication offerings? The
only one that is remotely viable is slony and it is so quirky you may as
well forget it. The rest are in some
Kevin Barnard wrote:
On Jun 22, 2009, at 4:53 PM, Gerry Reno wrote:
I noticed that the user survey on the community page does not list
replication among the choices for development priority. For me,
replication is the most important thing that is critically missing
from postgresql. We need
I noticed that the user survey on the community page does not list
replication among the choices for development priority. For me,
replication is the most important thing that is critically missing from
postgresql. We need something as good as MySQL Replication. Both
statement-based and row-
