[HACKERS] Re: ICU collation variant keywords and pg_collation entries (Was:[BUGS] Crash report for some ICU-52 (debian8) COLLATE and work_mem values)
От | Noah Misch |
---|---|
Тема | [HACKERS] Re: ICU collation variant keywords and pg_collation entries (Was:[BUGS] Crash report for some ICU-52 (debian8) COLLATE and work_mem values) |
Дата | |
Msg-id | 20170813193920.GA3963004@rfd.leadboat.com обсуждение исходный текст |
Ответ на | [HACKERS] Re: ICU collation variant keywords and pg_collation entries (Was:[BUGS] Crash report for some ICU-52 (debian8) COLLATE and work_mem values) (Noah Misch <noah@leadboat.com>) |
Ответы |
Re: [HACKERS] Re: ICU collation variant keywords and pg_collationentries (Was: [BUGS] Crash report for some ICU-52 (debian8) COLLATE andwork_mem values)
|
Список | pgsql-hackers |
On Thu, Aug 10, 2017 at 04:51:16AM +0000, Noah Misch wrote: > On Mon, Aug 07, 2017 at 06:23:56PM -0400, Tom Lane wrote: > > Peter Eisentraut <peter.eisentraut@2ndquadrant.com> writes: > > > On 8/6/17 20:07, Peter Geoghegan wrote: > > >> I've looked into this. I'll give an example of what keyword variants > > >> there are for Greek, and then discuss what I think each is. > > > > > I'm not sure why we want to get into editorializing this. We query ICU > > > for the names of distinct collations and use that. It's more than most > > > people need, sure, but it doesn't cost us anything. > > > > Yes, *it does*. The cost will be borne by users who get screwed at update > > time, not by developers, but that doesn't make it insignificant. > > [Action required within three days. This is a generic notification.] > > The above-described topic is currently a PostgreSQL 10 open item. Peter, > since you committed the patch believed to have created it, you own this open > item. If some other commit is more relevant or if this does not belong as a > v10 open item, please let us know. Otherwise, please observe the policy on > open item ownership[1] and send a status update within three calendar days of > this message. Include a date for your subsequent status update. Testers may > discover new open items at any time, and I want to plan to get them all fixed > well in advance of shipping v10. Consequently, I will appreciate your efforts > toward speedy resolution. Thanks. > > [1] https://www.postgresql.org/message-id/20170404140717.GA2675809%40tornado.leadboat.com This PostgreSQL 10 open item is past due for your status update. Kindly send a status update within 24 hours, and include a date for your subsequent status update. Refer to the policy on open item ownership: https://www.postgresql.org/message-id/20170404140717.GA2675809%40tornado.leadboat.com
В списке pgsql-hackers по дате отправления: