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: Peter Geoghegan <pg@heroku.com>
Cc: Matthew Kelly <mkelly@tripadvisor.com>, "pgsql-hackers@postgresql.org" <pgsql-hackers@postgresql.org>, Matthew Spilich <mspilich@tripadvisor.com>
Date: 2014-09-17T18:05:11Z
Lists: pgsql-hackers 
On 9/16/14 5:57 PM, Peter Geoghegan wrote:
> On Tue, Sep 16, 2014 at 2:07 PM, Peter Eisentraut <peter_e@gmx.net> wrote:
>> Clearly, this is worth documenting, but I don't think we can completely
>> prevent the problem.  There has been talk of a built-in index integrity
>> checking tool.  That would be quite useful.
> 
> We could at least use the GNU facility for versioning collations where
> available, LC_IDENTIFICATION [1].

It looks like the revisions or dates reported by LC_IDENTIFICATION
aren't ever updated for most locales.