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

Re: Best high availability solution ?

From: Arnaud Lesauvage <thewild(at)freesurf(dot)fr>
To: Dave Page <dpage(at)vale-housing(dot)co(dot)uk>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Best high availability solution ?
Date: 2006-05-31 10:53:21
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-general
Dave Page a ├ęcrit :
> The code is written, and is good as far as we are aware, but has not been through a beta/release cycle yet.

OK, that's already pretty good then.
Are there binary releases available ?

>> Is there a simple replication solution for windows then ? Or will 
>> I have to stop the master postgresql at night to pgdump and 
>> pgrestore on the backup server ?
> You don't need to stop the master server to pg_dump (in fact, it won't work if you do). On the slave, you can just drop the DBs and pg_restore them.
> PITR is another solution you might consider.

It looks quite harder to script though... But I'll consider it as 
a better solution.

> Might be better if the users know they are being switched over - that way they will know to check for lost transactions etc. If you're using an ODBC app, consider using a separate DSN for the live and backup servers - similar solutions would apply to other interfaces of course.

There are no critical transactions here.
If the DB server fails and users are switched over to a backup 
server with data of the day before, it is just fine.
Losing 1/2 of work is OK, but not working for 4 days is not.

So I might just write a script so that the person in charge when I 
am away can run it and alert everyone.


In response to

pgsql-general by date

Next:From: Dave PageDate: 2006-05-31 11:00:40
Subject: Re: Best high availability solution ?
Previous:From: Tino WildenhainDate: 2006-05-31 10:50:32
Subject: Re: Best high availability solution ?

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