From: Jaume Sabater <jsabater@gmail.com>
To: pgsql-admin@postgresql.org
Subject: Re: suggestions/hints for multimaster solution
Date: Fri, 9 Jan 2009 13:46:26 +0100
Message-ID: <3786f7bb0901090446q63ccd2aha409e81bc8d60684@mail.gmail.com> (raw)
In-Reply-To: <496743AD.1070304@transporeon.com>
References: <496727D0.9070801@transporeon.com>
<3786f7bb0901090313l2780aba8ia87d0a41e82acdec@mail.gmail.com>
<496743AD.1070304@transporeon.com>
2009/1/9 Gerd König <koenig@transporeon.com>:
> we want to have a scenario where (at least) 2 servers are r/w accessible
> and if one of the server crashes this should cause (almost) no downtime
> for the database.
> Yes, you're right, it's more like "keeping two databases in sync".
I would call this replication with failover (active-passive). To me,
multimaster sounds like active-active, where clients can send queries
to any of the nodes (that is why all nodes are masters). Of course,
it's just my point of view. :)
> We also use heartbeat for pinging the server themselves. Is it also
> possible to use heartbeat for checking the availability of a service
> (I'm not that familiar with heartbeat, so long) ?
> Does this mean you have two identical installations of pgpool-II on each
> of the db-servers ?
Yes, I have two almost identical installations of pgpool-II on each of
the PostgreSQL servers. pgpool-II handles the pgsql servers. Heartbeat
provides HA to pgpool-II.
Hope it helps, at least clarifying. :)
--
Jaume Sabater
http://linuxsilo.net/
"Ubi sapientas ibi libertas"
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: jsabater@gmail.com
Subject: Re: suggestions/hints for multimaster solution
In-Reply-To: <3786f7bb0901090446q63ccd2aha409e81bc8d60684@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox