Date: Sat, 18 Jun 2005 13:26:14 -0400 (EDT)
From: brew@theMode.com
To: pgsql-general@postgresql.org
Subject: Re: Replication
In-Reply-To: <20050618055500.35323.qmail@web32215.mail.mud.yahoo.com>
Message-ID: <Pine.BSF.4.58.0506181305390.44139@themode.com>
References: <20050618055500.35323.qmail@web32215.mail.mud.yahoo.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII


Jeffery.....

> I have been searching for the ability for replication between postgresql
> database servers. Many of the solutions That I have seen either work
> only un*x or requires an expensive commercial license. I am looking
> something rather short term and maybe for a long term solution.

If you don't actually need replication, and your database isn't huge, you
could instead just keep a backup server.  You could simply do an automated
pg_dumpall once a day (for instance), followed by an automated ftp,
followed by an automatic load into the backup database.

Guess you'd set it up as a service on windows, under *nix I use ssl rsync
and cron.  In the event I have to use my backup website server at another
location (only once, so far) it's read only and only up to date from the
night before.  But it's better than a nonworking website.

Of course I have a way to redirect the web requests, too.

Actually, now that I think about it, I put this together for my own use,
in my spare time, using machines I had available already.  If I had to do
it for a client I would do it right (with replication, load sharing,
etc.).

This is one way to keep it simple, but it might not meet your needs,
though.

brew

 ==========================================================================
                  Strange Brew   (brew@theMode.com)
  Check out my Stock Option Covered Call website  http://www.callpix.com
     and my Musician's Online Database Exchange http://www.TheMode.com
 ==========================================================================