Re: Collations and Replication; Next Steps
От
Peter Eisentraut
Тема
Re: Collations and Replication; Next Steps
Дата
Msg-id
5419CD57.4060507@gmx.net
Ответ на
Re: Collations and Replication; Next Steps (Peter Geoghegan)
Список
Дерево обсуждения
Collations and Replication; Next Steps Matthew Kelly <mkelly@tripadvisor.com>
Re: Collations and Replication; Next Steps Peter Eisentraut <peter_e@gmx.net>
Re: Collations and Replication; Next Steps Peter Geoghegan <pg@heroku.com>
Re: Collations and Replication; Next Steps Greg Stark <stark@mit.edu>
Re: Collations and Replication; Next Steps Peter Eisentraut <peter_e@gmx.net>
Re: Collations and Replication; Next Steps Peter Geoghegan <pg@heroku.com>
Re: Collations and Replication; Next Steps Peter Geoghegan <pg@heroku.com>
Re: Collations and Replication; Next Steps Martijn van Oosterhout <kleptog@svana.org>
Re: Collations and Replication; Next Steps Matthew Kelly <mkelly@tripadvisor.com>
Re: Collations and Replication; Next Steps Martijn van Oosterhout <kleptog@svana.org>
Re: Collations and Replication; Next Steps Bruce Momjian <bruce@momjian.us>
Re: Collations and Replication; Next Steps Peter Eisentraut <peter_e@gmx.net>
Re: Collations and Replication; Next Steps Peter Geoghegan <pg@heroku.com>
Re: Collations and Replication; Next Steps Robert Haas <robertmhaas@gmail.com>
Re: Collations and Replication; Next Steps Craig Ringer <craig@2ndquadrant.com>
Re: Collations and Replication; Next Steps Matthew Kelly <mkelly@tripadvisor.com>
Re: Collations and Replication; Next Steps Tatsuo Ishii <ishii@postgresql.org>
Re: Collations and Replication; Next Steps Peter Eisentraut <peter_e@gmx.net>
Re: Collations and Replication; Next Steps Tatsuo Ishii <ishii@postgresql.org>
Re: Collations and Replication; Next Steps Greg Stark <stark@mit.edu>
Re: Collations and Replication; Next Steps Tatsuo Ishii <ishii@postgresql.org>
Re: Collations and Replication; Next Steps Martijn van Oosterhout <kleptog@svana.org>
Re: Collations and Replication; Next Steps Robert Haas <robertmhaas@gmail.com>
Re: Collations and Replication; Next Steps Peter Geoghegan <pg@heroku.com>
Re: Collations and Replication; Next Steps Peter Geoghegan <pg@heroku.com>
Re: Collations and Replication; Next Steps Oleg Bartunov <obartunov@gmail.com>
Re: Collations and Replication; Next Steps Peter Geoghegan <pg@heroku.com>
Re: Collations and Replication; Next Steps Tatsuo Ishii <ishii@postgresql.org>
Re: Collations and Replication; Next Steps Martijn van Oosterhout <kleptog@svana.org>
Re: Collations and Replication; Next Steps Oleg Bartunov <obartunov@gmail.com>
Re: Collations and Replication; Next Steps Heikki Linnakangas <hlinnakangas@vmware.com>
Re: Collations and Replication; Next Steps Peter Geoghegan <pg@heroku.com>
Re: Collations and Replication; Next Steps Peter Geoghegan <pg@heroku.com>
Re: Collations and Replication; Next Steps Oleg Bartunov <obartunov@gmail.com>
Re: Collations and Replication; Next Steps Peter Eisentraut <peter_e@gmx.net>
Re: Collations and Replication; Next Steps Peter Geoghegan <pg@heroku.com>
Re: Collations and Replication; Next Steps Peter Eisentraut <peter_e@gmx.net>
On 9/16/14 5:57 PM, Peter Geoghegan wrote: > On Tue, Sep 16, 2014 at 2:07 PM, Peter Eisentraut 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 по дате отправления
