Level of replication support?

Hello,

There are two heavily supported and active replication projects.

1. Slony - http://www.slony.info
2. Mammoth Replicator - http://www.commandprompt.com/

Slony is Open Source and uses triggers and a replication schema to
replicate data.

Mammoth Replicator is commercial and uses a transaction log and a master
control process to replicate data.

Slony replicates data every (10?) transactions.
Mammoth Replicator replicates every transaction.

Mammoth is older than Slony and backed by my company Command Prompt, Inc.

Neither is slated to be "integrated" with PostgreSQL as they are both
good products that serve different purposes.

Sincerely,

Joshua D. Drake

nd02tsk@student.hig.se wrote:

Hello

I am going to do a comparison betweem PgSQL and MySQL replication system.

I hear there are some replication projects available for PgSQL. Which are
still active and serious, because I hear that some are not active or
incomplete?

Will any of these projects be merged with PgSQL soon?

I appreciate all information.

Thank you.

Tim

---------------------------(end of broadcast)---------------------------
TIP 5: Have you checked our extensive FAQ?

http://www.postgresql.org/docs/faqs/FAQ.html

-- 
Command Prompt, Inc., home of PostgreSQL Replication, and plPHP.
Postgresql support, programming shared hosting and dedicated hosting.
+1-503-667-4564 - jd@commandprompt.com - http://www.commandprompt.com
Mammoth PostgreSQL Replicator. Integrated Replication for PostgreSQL

Here is a good overview.

http://jeremy.zawodny.com/blog/archives/000846.html

Note that http://pgreplicator.sourceforge.net/ is a
multi-master solution using TCL. Despite the dire
home page, it is "actively" supported. However, our
experience with it was that it was not industrial
strenght. We aren't TCL experts though, so maybe that
would have helped.

--Ted
--- "Joshua D. Drake" <jd@commandprompt.com> wrote:

Hello,

There are two heavily supported and active
replication projects.

1. Slony - http://www.slony.info
2. Mammoth Replicator -
http://www.commandprompt.com/

Slony is Open Source and uses triggers and a
replication schema to
replicate data.

Mammoth Replicator is commercial and uses a
transaction log and a master
control process to replicate data.

Slony replicates data every (10?) transactions.
Mammoth Replicator replicates every transaction.

Mammoth is older than Slony and backed by my company
Command Prompt, Inc.

Neither is slated to be "integrated" with PostgreSQL
as they are both
good products that serve different purposes.

Sincerely,

Joshua D. Drake

nd02tsk@student.hig.se wrote:

Hello

I am going to do a comparison betweem PgSQL and

MySQL replication system.

I hear there are some replication projects

available for PgSQL. Which are

still active and serious, because I hear that some

are not active or

incomplete?

Will any of these projects be merged with PgSQL

soon?

I appreciate all information.

Thank you.

Tim

---------------------------(end of

broadcast)---------------------------

TIP 5: Have you checked our extensive FAQ?

http://www.postgresql.org/docs/faqs/FAQ.html

--
Command Prompt, Inc., home of PostgreSQL
Replication, and plPHP.
Postgresql support, programming shared hosting and
dedicated hosting.
+1-503-667-4564 - jd@commandprompt.com -
http://www.commandprompt.com
Mammoth PostgreSQL Replicator. Integrated
Replication for PostgreSQL

begin:vcard

fn:Joshua D. Drake
n:Drake;Joshua D.
org:Command Prompt, Inc.
adr:;;PO Box 215;Cascade Locks;Oregon;97014;USA
email;internet:jd@commandprompt.com
title:Consultant
tel;work:503-667-4564
tel;fax:503-210-0334
note:Command Prompt, Inc. is the largest and oldest
US based commercial PostgreSQL support provider. We
provide the only commercially viable integrated
PostgreSQL replication solution, but also custom
programming, and support. We authored the book
Practical PostgreSQL, the procedural language plPHP,
and adding trigger capability to plPerl.
x-mozilla-html:FALSE
url:http://www.commandprompt.com/
version:2.1
end:vcard

---------------------------(end of
broadcast)---------------------------
TIP 6: Have you searched our list archives?

http://archives.postgresql.org

_______________________________
Do you Yahoo!?
Declare Yourself - Register online to vote today!
http://vote.yahoo.com

On Wed, 13 Oct 2004, Joshua D. Drake wrote:

Hello,

There are two heavily supported and active replication projects.

1. Slony - http://www.slony.info
2. Mammoth Replicator - http://www.commandprompt.com/

Three, actually ...

3. eRServer - http://www.pgsql.com

We're currently working on the next version ...

----
Marc G. Fournier Hub.Org Networking Services (http://www.hub.org)
Email: scrappy@hub.org Yahoo!: yscrappy ICQ: 7615664

In an attempt to throw the authorities off his trail, jd@commandprompt.com ("Joshua D. Drake") transmitted:

Slony replicates data every (10?) transactions.

No, Slony-I replicates each and every transaction that it processes,
identifying it as a transaction independent of others.

In practice, it is usually preferable to group updates together when
_applying_ them into destination systems; how much or how little
grouping is done is configurable.

Mammoth Replicator replicates every transaction.

Just like Slony-I ;-).

Mammoth is older than Slony and backed by my company Command Prompt,
Inc.

Neither is slated to be "integrated" with PostgreSQL as they are both
good products that serve different purposes.

An excellent reason NOT to integrate these systems tightly is that it
allows them to be used between _different_ versions of PostgreSQL,
between different platforms, and such.

One of the common "use cases" people have been finding finding for
Slony-I hasn't got to do with maintaining replicas, but rather to do
with doing quick upgrades to a new version of PostgreSQL.

Rather than doing a pg_dump, and having to sit in downtime from the
time the dump starts until when it is applied, you set up a
replication target on the newer version of PostgreSQL. If it takes 3
days to bring the target "online" and up to date, that doesn't
"matter" because it isn't downtime for the live system.

Once the target is up to date, it can take seconds to minutes to
merely switch over to the new PG database, rather than the hours
needed by less sophisticated methods. No doubt the same can be done
with Mammoth Replicator.

Tight integration with the database discourages that sort of thing.
--
(reverse (concatenate 'string "gro.mca" "@" "enworbbc"))
http://www3.sympatico.ca/cbbrowne/spreadsheets.html
Signs of a Klingon Programmer - 1. "Defensive programming? Never!
Klingon programs are always on the offense. Yes, offensive programming
is what we do best."