pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Joshua D. Drake <jd@commandprompt.com>
To: David B <davidb999@gmail.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: Replication solutions high volume db
Date: Tue, 29 Mar 2005 15:50:56 -0800
Message-ID: <1112140257.27795.67.camel@jd2.commandprompt.com> (raw)
In-Reply-To: <c76ea21c05032915342c89504e@mail.gmail.com>
References: <c76ea21c05032915342c89504e@mail.gmail.com>


> 
> I think I've narrowed it down to Slony and Mammoth.
> Any pro's or con's on one vs the other?

Slony is more complicated to setup.
Slony requires triggers and cron.
Slony is asynchronous
Slony is Open Source
If Slony breaks you can call Command Prompt
It used to be that Slony was timed replication. I do not know if that is
still the case.

Mammoth is about as easy as it can be to setup.
Mammoth does not require triggers or cron
Mammoth is asynchronous
Mammoth costs $$$
Mammoth is set to be optionally synchronous in June.
Mammoth replicates on a per comitted transaction basis.
Mammoth Replicator is PostgreSQL with integrated replication.
If Mammoth breaks you can call Command Prompt ;)

> 
> Some area where our environement might stretch a solution.
> Some records can be large. Limitied to one table but they can be 40K+
> of chraracters in a column.

As long as that is not the primary key, there wouldn't be a problem.
The length of the primary key can not be greater than 8k with Mammoth.

> 
> High volume of inserts coming during nightly load (millions of rows).
> These loads are coming in commited blocks of 100.

No problem.

> 
> That cannot slow down the replication.
> Our call center agents needs access to them asap.
> 
> Any locking issues on the master during the replication process?

Neither Mammoth or Slony require any exclusive locks to replicate the
data.


Sincerely,

Joshua D. Drake



> Anything else I should be concerned about or things I need to consider?
> Personal experiences you have had running either.
> 
> tia
> David
> 
> ---------------------------(end of broadcast)---------------------------
> TIP 7: don't forget to increase your free space map settings
-- 
Command Prompt, Inc., Your PostgreSQL solutions company. 503-667-4564
Custom programming, 24x7 support, managed services, and hosting
Open Source Authors: plPHP, pgManage, Co-Authors: plPerlNG
Reliable replication, Mammoth Replicator - http://www.commandprompt.com/




view thread (7+ messages)  latest in thread

Message-ID: <1112140257.27795.67.camel@jd2.commandprompt.com>
Permalink:  ../1112140257.27795.67.camel@jd2.commandprompt.com/
Also on:    postgresql.org/message-id/1112140257.27795.67.camel@jd2.commandprompt.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-admin@postgresql.org
  Cc: jd@commandprompt.com, davidb999@gmail.com
  Subject: Re: Replication solutions high volume db
  In-Reply-To: <1112140257.27795.67.camel@jd2.commandprompt.com>
  References: <c76ea21c05032915342c89504e@mail.gmail.com> <1112140257.27795.67.camel@jd2.commandprompt.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox