Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1YBdQL-0000mh-Dh for pgsql-admin@arkaria.postgresql.org; Thu, 15 Jan 2015 05:56:53 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1YBdQK-0005A2-Sz for pgsql-admin@arkaria.postgresql.org; Thu, 15 Jan 2015 05:56:52 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1YBdQJ-000568-RW for pgsql-admin@postgresql.org; Thu, 15 Jan 2015 05:56:52 +0000 Received: from mail.journyx.com ([209.163.206.41] helo=mail.int.journyx.com) by makus.postgresql.org with esmtps (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1YBdQD-0002BZ-SH for pgsql-admin@postgresql.org; Thu, 15 Jan 2015 05:56:48 +0000 Received: from localhost (localhost [127.0.0.1]) by mail.int.journyx.com (Postfix) with ESMTP id D4126300287; Wed, 14 Jan 2015 23:56:44 -0600 (CST) Received: from mail.int.journyx.com ([127.0.0.1]) by localhost (mail.int.journyx.com [127.0.0.1]) (amavisd-new, port 10032) with ESMTP id KVMqYZe2GrcO; Wed, 14 Jan 2015 23:56:44 -0600 (CST) Received: from localhost (localhost [127.0.0.1]) by mail.int.journyx.com (Postfix) with ESMTP id 9447C30028C; Wed, 14 Jan 2015 23:56:44 -0600 (CST) X-Amavis-Modified: Mail body modified (using disclaimer) - mail.int.journyx.com X-Virus-Scanned: amavisd-new at mail.int.journyx.com Received: from mail.int.journyx.com ([127.0.0.1]) by localhost (mail.int.journyx.com [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id 6ggmT-q9KPGa; Wed, 14 Jan 2015 23:56:44 -0600 (CST) Received: from mail.int.journyx.com (zimbra.int.journyx.com [192.168.100.5]) by mail.int.journyx.com (Postfix) with ESMTP id 4DB53300287; Wed, 14 Jan 2015 23:56:44 -0600 (CST) MIME-Version: 1.0 X-Mailer: CloudMagic X-Mailer: Zimbra 8.5.0_GA_3042 (MobileSync - CloudMagic) X-Cm-Message-Id: 1421301403651530f69f9e8b42aeb4a6bdb1be2eb7a4586c54b7569b9f1bb899742042 To: shyamkant.dhamke@wipro.com Cc: pgsql-admin@postgresql.org Subject: Re: Clustering of pgsql 9.2 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable Message-ID: <1726494568.3799.1421301404096.JavaMail.zimbra@zimbra.int.journyx.com> From: Scott Whitney Date: Wed, 14 Jan 2015 23:56:44 -0600 (CST) Thread-Topic: Clustering of pgsql 9.2 Thread-Index: uefGtqqeYDgrV5S86oNyKR5rlTMyCQ== X-Pg-Spam-Score: 1.1 (+) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-admin Precedence: bulk Sender: pgsql-admin-owner@postgresql.org

Let me begin by deferring to The Big Brains, but I am = not sure there's enough in this to really advise you from The = Implementation Guys. That's me. I/O for any database is an issue, and when = I hear any db talking to a SAN, I get a bit leery. Couple that with = replication, HA and failover=3F

If you could explain a bit more about what you're trying= to accomplish, what expected performance should be, how that SAN is = actually utilized, and such, I might be able to provide some experience on = the issue.


On Wed, = Jan 14, 2015 at 11:27 PM, shyamkant.dhamke@wipro.com <shyamkant.dhamke@wipro.= com> wrote:

Dear All,

 

We have following environment for  database= clustering at production environment:

1.   &nbs= p;   Postgres is running on RedHat 6 enterprise edition for = primary and failover server

2.   &nbs= p;   SAN disk is available

 

Now I need help on following

1.   &nbs= p;   What should be clustering software used for Redhat clustering= =3F Can Veritas Clustering Software (VCS) = clustering be used for clustering REDHAT OS=3F

2.   &nbs= p;   How the SAN disk can be used = to store the data centrally=3F Can this be used as QUORAM = disk=3F

3.   &nbs= p;   Is there any service for = Postgres Database service clustering=3F

 

Please help me in providing details.

 

Regards

Shyamkant