Re: Collations and Replication; Next Steps - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: Collations and Replication; Next Steps
Date
Msg-id 5419CD57.4060507@gmx.net
Whole thread Raw
In response to Re: Collations and Replication; Next Steps  (Peter Geoghegan <pg@heroku.com>)
Responses Re: Collations and Replication; Next Steps
List 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.




pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: Collations and Replication; Next Steps
Next
From: Martijn van Oosterhout
Date:
Subject: Re: Collations and Replication; Next Steps