Skip site navigation (1) Skip section navigation (2)

replication and availability

From: stephane parenton <stephane(at)parenton(dot)com>
To: pgsql <pgsql-admin(at)postgresql(dot)org>
Subject: replication and availability
Date: 2003-07-24 13:50:13
Message-ID: 3F1FE415.3040003@parenton.com (view raw or flat)
Thread:
Lists: pgsql-admin
hi everyone,

having read the online doc, and a book, i can't find precisely what i'm 
looking for, but it's maybe normal.... here it is....
I have a distant postgres database used to store networking info. This 
database "may" be unavailable, so i need to have another postgres 
database somewhere else (it theory, i should know where...). What can i 
do to tell somewhere/postgres to be exactly the same as 
elsewhere/postgres... Let's imagine that somewhere/postgres is my 
primary database, shall i have to use triggers in order to insert/delete 
datas in elsewhere/postgres at the same time as somewhere/postgres ? or 
should i have to dump somewhere/postgres regularly and update 
elsewhere/postgres with this dump (cron job ?)...

Isn't there a something in postgres to say elsewhere should be the 
database image of somewhere/postgres ?

regards

stephane


pgsql-admin by date

Next:From: Yogesh BhanuDate: 2003-07-24 17:32:50
Subject: PG-7.3.2 and tru64 5.1a
Previous:From: A.BhuvaneswaranDate: 2003-07-24 09:23:54
Subject: Re: Using the /var/lib/pgsql/data directory in the absense

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group