Re: [SLUG] postgres database replication

[James Peter Gregory <jgre4014@xxxxxxxxxxxxxxxx>]

On Thu, 5 Jul 2001 torqumada@xxxxxxxxxxxxxxxxxx wrote:

> On Thu, 5 Jul 2001, James Peter Gregory wrote:
>
> hi, yeah we did this.. just dump the data and restore on another box.
> it worked for 50million tuples, 20gb production data... ymmv

Ok, so how did you actually do the replication? I mean copying the data to
another system is easy enough, but I need to be able to pull the plug on
either one of these servers at any point and have all the session data etc
maintained. These databases will have a whole lot of inserts and updates
going on all the time, and both servers need to have current data at all
times.

ta.

James.

>
> /Torqumada
>
> > Ok, so the scenario is this: there's about 17000 lines of php code driving
> > this killer-app I'm working on for work, and they want to add database
> > replication. The database is postgres 7.1.2. Furthermore, they want to do
> > load-balancing between the replicated servers. So first of all, my question
> > - has anyone setup any form of replication on postgres? which method did you
>
> --
> Paladin Corporation Pty Ltd.  Ph:+612 9835-4782     Fax:+612 9864-0487
> Software Engineering:    c/c++/perl/sql/eiffel/pascal/haskell/php/java
> Powered by FreeBSD/SMP                  http://www.paladincorp.com.au/
> The  lyf  so  short,  the  craft  so  long  to  lerne     -    Chaucer
>
>
>
> This e-mail and any files transmitted with it are confidential and intended
> solely for the use of the individual or entity to whom they are addressed.
> If you are not the intended addressee, or the person responsible for
> delivering it to them, you may not copy, forward disclose or otherwise use
> it or any part of it in any way. To do so may be unlawful. If you receive
> this e-mail by mistake, please advise the sender immediately.
>
>

-- 
"A one-time pad isn't a cryptosystem: it's a state of mind."