pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Clinton Adams <clinton@vote-smart.org>
To: pgsql-admin@postgresql.org
Subject: Replication
Date: Thu, 24 Jan 2002 10:05:13 -0700
Message-ID: <5.0.2.1.0.20020124085539.00acb978@mail.vote-smart.org> (raw)


Hi,

Anyone have thoughts on how I might handle replication with 1 master and 2 
slave databases (minimum)?

I am switching our political database from mysql to postgres and need a 
solid way to replicate data from our internal server to our webserver.  We 
currently use 2 databases per server, one administrative database, one live 
database for the web.  A perl script approximates replication by applying 
changes in the local administrative database to the local live database as 
well as the administrative databases on the other servers.  The catch is 
only the changes marked as release changes are sent to the live database. I 
suppose I really shouldn't call it replication!

Now that I am doing a extensive redesign of the database and the data entry 
client, I am considering consolidating the live and administrative 
databases into one with a 'released' field per table to indicate what's 
live and what's internal, but this sounds like it would really slow down 
the queries.  I could use a trigger to dump all the changes into another 
table, and then have a perl script to send these changes to the 
slaves...and a cronjob on the slaves that removes the records marked as 
internal. Ideas/caveats?

Thanks for any help!
Clinton











view thread (63+ messages)  latest in thread

Message-ID: <5.0.2.1.0.20020124085539.00acb978@mail.vote-smart.org>
Permalink:  ../5.0.2.1.0.20020124085539.00acb978@mail.vote-smart.org/
Also on:    postgresql.org/message-id/5.0.2.1.0.20020124085539.00acb978@mail.vote-smart.org

 · 

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: clinton@vote-smart.org
  Subject: Re: Replication
  In-Reply-To: <5.0.2.1.0.20020124085539.00acb978@mail.vote-smart.org>
  References: <5.0.2.1.0.20020124085539.00acb978@mail.vote-smart.org>

* 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