Re: Collations and Replication; Next Steps

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Matthew Kelly <mkelly(at)tripadvisor(dot)com>
Cc: Martijn van Oosterhout <kleptog(at)svana(dot)org>, Peter Geoghegan <pg(at)heroku(dot)com>, Peter Eisentraut <peter_e(at)gmx(dot)net>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>, Matthew Spilich <mspilich(at)tripadvisor(dot)com>
Subject: Re: Collations and Replication; Next Steps
Date: 2014-09-30 14:56:51
Message-ID: 20140930145651.GA23885@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Sep 17, 2014 at 01:07:56PM +0000, Matthew Kelly wrote:
> * Unless you keep _all_ of your clusters on the same OS, machines
> from your database spare pool probably won't be the right OS when you
> add them to the cluster because a member failed.

There has been discussion about having master/streaming slaves use the
same OS version, but a simple OS update of an existing master can break
indexes too.

--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com

+ Everyone has their own god. +

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Dev Kumkar 2014-09-30 15:10:28 Re: [SQL] pg_multixact issues
Previous Message Alvaro Herrera 2014-09-30 14:56:07 Re: pgcrypto: PGP armor headers