Search Postgresql Archives

Re: Best high availability solution ?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



 

> -----Original Message-----
> From: pgsql-general-owner@xxxxxxxxxxxxxx 
> [mailto:pgsql-general-owner@xxxxxxxxxxxxxx] On Behalf Of Tino 
> Wildenhain
> Sent: 31 May 2006 12:14
> To: Arnaud Lesauvage
> Cc: pgsql-general@xxxxxxxxxxxxxx
> Subject: Re: [GENERAL] Best high availability solution ?
> 
> > Then with a script that would change my DNS so that 
> > mypgserver.domain.tld (used in ODBC connection string) 
> points to CNAME 
> > mybackupserver.domain.tld instead of CNAME 
> mymasterserver.domain.tld, 
> > getting back to production ould be quite easy...?
> 
> I guess the users would start over anyway. So easiest if you
> provide a copy of the app with that other connection and
> signal them if the first server dies to just close the first
> and start the backup-application.

Yes - the DNS method would work, but you might run into caching issues
requiring the users to reboot or do a 'ipconfig /flushdns' before they
see the change.

Regards, Dave.


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]
  Powered by Linux