pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Scott Marlowe <smarlowe@g2switchworks.com>
To: David B <davidb999@gmail.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: Replication solutions high volume db
Date: Tue, 29 Mar 2005 17:55:38 -0600
Message-ID: <1112140537.31277.15.camel@state.g2switchworks.com> (raw)
In-Reply-To: <c76ea21c05032915342c89504e@mail.gmail.com>
References: <c76ea21c05032915342c89504e@mail.gmail.com>

On Tue, 2005-03-29 at 17:34, David B wrote:
> Folks,
> 
> I'm thinking of replication tools for high volume site.
> Postgres on dual Opteron box. 1/2 GB of data.
> 
> Big overnight load of data.
> Some inserts during the data but mostly selects.
> 
> I think I've narrowed it down to Slony and Mammoth.
> Any pro's or con's on one vs the other?
> 
> There is the obvious price difference but thats managable if Mammoth
> substancially better.
> 
> 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.
> 
> High volume of inserts coming during nightly load (millions of rows).
> These loads are coming in commited blocks of 100.
> 
> 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?
> 
> 
> Anything else I should be concerned about or things I need to consider?
> Personal experiences you have had running either.

I don't see any obvious problems for either replication engine here.

Since slony is free and pretty easy to setup, I'd make a test setup and
see how it handles the load.  

Generally speaking I'd expect Mammoth to handle high loads a little
better since it's a log shipper and not trigger based.  So, if slony
proves too slow for this situation, then I'd recommend asking the folks
at Command Prompt for a demo of their system to see if it can.



view thread (7+ messages)  latest in thread

Message-ID: <1112140537.31277.15.camel@state.g2switchworks.com>
Permalink:  ../1112140537.31277.15.camel@state.g2switchworks.com/
Also on:    postgresql.org/message-id/1112140537.31277.15.camel@state.g2switchworks.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: smarlowe@g2switchworks.com, davidb999@gmail.com
  Subject: Re: Replication solutions high volume db
  In-Reply-To: <1112140537.31277.15.camel@state.g2switchworks.com>
  References: <c76ea21c05032915342c89504e@mail.gmail.com> <1112140537.31277.15.camel@state.g2switchworks.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