Skip site navigation (1) Skip section navigation (2)

Postgres with Sun Cluster HA/Solaris 10

From: "Subbiah Stalin-XCGF84" <SSubbiah(at)Motorola(dot)com>
To: <pgsql-admin(at)postgresql(dot)org>
Cc: <pgsql-performance(at)postgresql(dot)org>
Subject: Postgres with Sun Cluster HA/Solaris 10
Date: 2007-09-05 22:33:06
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-adminpgsql-performance
Hello All,

We have a postgres setup on solaris 10 with sun cluster for HA purposes.
2 nodes are configured in the cluster in active-passive mode 
with pg_data stored on external storage. Everything is working as
expected however, when we either switch the resource group from one node
to other or rg restart on primary node, the apps fails with "An I/O
error occurred while sending to the backend." and doesn't recover back
from db failover. All queries to the db give the above error after
resource group restart.

Our app uses resin container db pooling, with following HA parameters
set. With same settings, the app recovers just fine with database
configured in non-cluster mode i.e. no sun cluster setup etc.

<driver type="org.postgresql.Driver">

Any pointers to debug this futher is greatly appreciated. We are running
postgres 8.2.4.

Other thing i noticed in pg_log/server.logs is that whenever i restart
postgres i get below error, when there is no other postgres running on

"LOG:  could not bind IPv6 socket: Cannot assign requested address
HINT:  Is another postmaster already running on port 5432? If not, wait
a few seconds and retry."


In response to


pgsql-performance by date

Next:From: Thomas FinneidDate: 2007-09-05 22:41:06
Subject: utilising multi-cpu/core machines?
Previous:From: Adam Tauno WilliamsDate: 2007-09-05 22:15:58
Subject: Re: Performance on 8CPU's and 32GB of RAM

pgsql-admin by date

Next:From: Subbiah Stalin-XCGF84Date: 2007-09-05 22:48:52
Subject: RESEND:Postgres with Sun Cluster HA/Solaris 10
Previous:From: Tom LaneDate: 2007-09-05 15:03:22
Subject: Re: No pg_dumplo on 8.2.4

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group