From: | Ron Johnson <ron(dot)l(dot)johnson(at)cox(dot)net> |
---|---|
To: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Veritas cluster management |
Date: | 2017-08-30 13:54:40 |
Message-ID: | c1fdb2b6-a20b-c657-c1a9-0c4bce73773d@cox.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 08/30/2017 08:48 AM, Scott Mead wrote:
>
>
> On Wed, Aug 30, 2017 at 9:43 AM, Ron Johnson <ron(dot)l(dot)johnson(at)cox(dot)net
> <mailto:ron(dot)l(dot)johnson(at)cox(dot)net>> wrote:
>
> Hi,
>
> For any of you with those failover clusters, do you know if "pg_ctl
> reload" works (for compatible config file changes), or must we bounce
> the database using "hares -offline" then "hares -online"?
>
>
> pg_ctl reload does work in this case. HOWEVER, if you do something that
> could cause trouble to the cluster (i.e. a pg_hba.conf change that breaks
> connectivity), this could cause veritas to try and failover. It's
> recommended that you test your changes to avoid these scenarios.
>
> Technically however, pg_ctl reload works just fine, just don't break
> anything :)
That's great news. Many thanks.
--
World Peace Through Nuclear Pacification
From | Date | Subject | |
---|---|---|---|
Next Message | Luca Looz | 2017-08-30 16:37:47 | Re: Serializable Isolation and read/write conflict with index and different keys |
Previous Message | Scott Mead | 2017-08-30 13:48:13 | Re: Veritas cluster management |