From: Snoop <snoop@email.it>
To: Achilleas Mantzios <achill@matrix.gatewaynet.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: PostgreSQL in Shared Disk Failover mode on FreeBSD+CARP+RAIDZ
Date: Wed, 22 Dec 2010 20:49:17 +0100
Message-ID: <1293047357.33180.30.camel@blackfriar.inhio.eu> (raw)
In-Reply-To: <201012210952.41004.achill@matrix.gatewaynet.com>
References: <3702fd882cd904ce76ccd7c09d7645d9@213.152.156.147>
<201012210952.41004.achill@matrix.gatewaynet.com>
After some enlightening considerations by Scott Marlowe I'm actually now
considering a streaming replication with dedicated network connection
and two different data dirs on the same storage. This would bypass the
lock issue, make replication very fast and make my life "easier" with
one reliable (replicated) data storage.
Cannot say if this is the best solution but I'm studying ... trying to
deny myself. :)
Thanks for your reply Achilleas.
On Tue, 2010-12-21 at 10:52 +0300, Achilleas Mantzios wrote:
> Óôéò Tuesday 21 December 2010 03:23:25 ï/ç snoop@email.it Ýãñáøå:
> > Hi everybody,
> > I'm trying to figure out a way to setup a PostgreSQL HA cluster solution.
> >
> > I've done some research and I've an idea of different possible solutions,
> > but I'd honestly like to implement it using CARP in a "Shared Disk Failover"
> > fashion.
>
> This reminds me of the serialization stack on shared disks (DASD) in the MVS IBM oper system.
> It takes a lot of work to do that on OS level. Its smth beyond multiprocessing and high availability.
> Think about it. In FreeBSD (or any of-the-shelf Unix), there is no inherent way to implicitly lock files.
> Even on the same machine, if two users/processes modify the same file, the one who saves (closes)
> the file last, generally wins. In order to do that, you will have to use explicit locking done by the application.
> The OS by itself does not do that by default.
> Things get tougher in a networked environment since file serialization should be applied at network-level.
> This combination of data sharing (the idea of decoupling the concept of redundant hardware
> from the concept of redundant disks) with the characteristics of parallel computing was realized in
> IBM's Parallel Sysplex technology: http://en.wikipedia.org/wiki/IBM_Parallel_Sysplex
> On top of it, someone could have CICS, DB2,etc... almost any available application.
> It would be interesting to know if there is some concept close to it in the open source-Unix world.
>
> --
> Achilleas Mantzios
>
--
Caselle da 1GB, trasmetti allegati fino a 3GB e in piu' IMAP, POP3 e SMTP autenticato? GRATIS solo con Email.it http://www.email.it/f
Sponsor:
Riccione Capodanno Low Cost: hotel 3 stelle sup centralissimo, zona relax, pacchetto mezza pensione con bevande, bottiglia per festeggiare. 2gg euro 165,00 a persona
Clicca qui: http://adv.email.it/cgi-bin/foclick.cgi?mid=11205&d=22-12
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 from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-admin@postgresql.org
Cc: snoop@email.it, achill@matrix.gatewaynet.com
Subject: Re: PostgreSQL in Shared Disk Failover mode on FreeBSD+CARP+RAIDZ
In-Reply-To: <1293047357.33180.30.camel@blackfriar.inhio.eu>
References: <3702fd882cd904ce76ccd7c09d7645d9@213.152.156.147> <201012210952.41004.achill@matrix.gatewaynet.com> <1293047357.33180.30.camel@blackfriar.inhio.eu>
* 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