Received: from maia.hub.org (maia-3.hub.org [200.46.204.243]) by mail.postgresql.org (Postfix) with ESMTP id 195AA133616B for ; Tue, 21 Dec 2010 03:52:52 -0400 (AST) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.243]) (amavisd-maia, port 10024) with ESMTP id 22605-06 for ; Tue, 21 Dec 2010 07:52:44 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from smadev.internal.net (host3.dynacom.ondsl.gr [62.103.35.211]) by mail.postgresql.org (Postfix) with ESMTP id 880961337B5B for ; Tue, 21 Dec 2010 03:52:42 -0400 (AST) Received: from smadev.internal.net (localhost.internal.net [127.0.0.1]) by smadev.internal.net (8.14.2/8.14.2) with ESMTP id oBL7qfE1065158 for ; Tue, 21 Dec 2010 09:52:41 +0200 (EET) (envelope-from achill@matrix.gatewaynet.com) Received: from localhost (localhost [[UNIX: localhost]]) by smadev.internal.net (8.14.2/8.14.2/Submit) id oBL7qfS7065157 for pgsql-admin@postgresql.org; Tue, 21 Dec 2010 09:52:41 +0200 (EET) (envelope-from achill@matrix.gatewaynet.com) From: Achilleas Mantzios Organization: Dynacom Tankers Mgmt To: pgsql-admin@postgresql.org Subject: Re: PostgreSQL in Shared Disk Failover mode on FreeBSD+CARP+RAIDZ User-Agent: KMail/1.9.7 References: <3702fd882cd904ce76ccd7c09d7645d9@213.152.156.147> In-Reply-To: <3702fd882cd904ce76ccd7c09d7645d9@213.152.156.147> MIME-Version: 1.0 Content-Disposition: inline Date: Tue, 21 Dec 2010 10:52:40 +0300 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Message-Id: <201012210952.41004.achill@matrix.gatewaynet.com> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-0.451 tagged_above=-10 required=5 tests=BAYES_00=-1.9, RCVD_IN_BRBL_LASTEXT=1.449 X-Spam-Level: X-Archive-Number: 201012/143 X-Sequence-Number: 36372 =CE=A3=CF=84=CE=B9=CF=82 Tuesday 21 December 2010 03:23:25 =CE=BF/=CE=B7 sn= oop@email.it =CE=AD=CE=B3=CF=81=CE=B1=CF=88=CE=B5: > Hi everybody, > I'm trying to figure out a way to setup a PostgreSQL HA cluster solution. >=20 > 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 Failov= er" > fashion. This reminds me of the serialization stack on shared disks (DASD) in the MV= S IBM oper system. It takes a lot of work to do that on OS level. Its smth beyond multiprocess= ing 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 ex= plicit 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 shou= ld be applied at network-level. This combination of data sharing (the idea of decoupling the concept of red= undant hardware from the concept of redundant disks) with the characteristics of parallel c= omputing was realized in=20 IBM's Parallel Sysplex technology: http://en.wikipedia.org/wiki/IBM_Paralle= l_Sysplex On top of it, someone could have CICS, DB2,etc... almost any available appl= ication. It would be interesting to know if there is some concept close to it in the= open source-Unix world. =2D-=20 Achilleas Mantzios