Horton

Re: Collations and Replication; Next Steps

Peter Eisentraut <peter_e@gmx.net>

View thread View on postgr.es
From: Peter Eisentraut <peter_e@gmx.net>
To: Matthew Kelly <mkelly@tripadvisor.com>, Martijn van Oosterhout <kleptog@svana.org>
Cc: Peter Geoghegan <pg@heroku.com>, "pgsql-hackers@postgresql.org" <pgsql-hackers@postgresql.org>, Matthew Spilich <mspilich@tripadvisor.com>
Date: 2014-09-17T18:08:34Z
Lists: pgsql-hackers 
On 9/17/14 9:07 AM, Matthew Kelly wrote:
> Here is where I think the timezone and PostGIS cases are fundamentally different:
> I can pretty easily make sure that all my servers run in the same timezone.  That's just good practice.  I'm also going to install the same version of PostGIS everywhere in a cluster.  I'll build PostGIS and its dependencies from the exact same source files, regardless of when I build the machine.

I wrote time zone *database*, not time zone.  The time zone database  is
(in some configurations) part of glibc.

I also wrote PostGIS dependent libraries, not PostGIS itself.  If you
are comparing RHEL 5 and 6, as you wrote elsewhere, then some of those
will most likely be different.  (Heck, glibc could be different.  Is
glibc never allowed to fix insufficiencies in its floating-point
implementation, for example?)

Also, there is nothing that guarantees that the PostGIS version will be
the same on both sides.