Re: Best high availability solution ?
От | Dave Page |
---|---|
Тема | Re: Best high availability solution ? |
Дата | |
Msg-id | E7F85A1B5FF8D44C8A1AF6885BC9A0E4013885CA@ratbert.vale-housing.co.uk обсуждение исходный текст |
Ответ на | Best high availability solution ? (Arnaud Lesauvage <thewild@freesurf.fr>) |
Ответы |
Re: Best high availability solution ?
|
Список | pgsql-general |
> -----Original Message----- > From: pgsql-general-owner@postgresql.org > [mailto:pgsql-general-owner@postgresql.org] On Behalf Of Tino > Wildenhain > Sent: 31 May 2006 12:14 > To: Arnaud Lesauvage > Cc: pgsql-general@postgresql.org > 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.
В списке pgsql-general по дате отправления: