And there DOES come a time where PostgreSQL is not the correct solution.
At this time you can not mirror a postgreSQL server like you can mirror a,
say Oracle server. It sounds like they want mirroring servers the way
some commerical servers can do.
Nothing stopping your employer/patron/slave driver from paying someone to
develop this kind of feature in postgreSQL.
And nothing stopping you from re-writting the app such that the app
worries about mirroring the data. (IE, it makes sure it has its own
transaction set in case it can't talk to the other server, and all queries
are duplicated on the other box.)
On Tue, 17 Oct 2000, Adam Lang wrote:
> Granted it probably not the most efficient solution, but if it is something
> that is really a problem... what about having your dual server, one data
> source setup, but the second server is idle and does nothing and only kicks
> in if the primary drops? Might be more complicated to setup than it sounds
> and there still would be a time delay for the second to pick up, but it
> technically would eliminate the two servers butting heads. Again though,
> not very efficient solution... unless it is very critical and money is no
> object. :)
>
> Adam Lang
> Systems Engineer
> Rutgers Casualty Insurance Company
> ----- Original Message -----
> From: "Joseph Shraibman" <jks@selectacast.net>
> To: <pgsql-interfaces@postgreSQL.org>
> Sent: Tuesday, October 17, 2000 2:53 PM
> Subject: [Fwd: [INTERFACES] 2 computers 1hd 2 postgres daemons. Is it
> possible?]
>
>
> >
> > --
> > Joseph Shraibman
> > jks@selectacast.net
> > Increase signal to noise ratio. http://www.targabot.com
>
>