Re: [BUGS] Crash report for some ICU-52 (debian8) COLLATE and work_mem values
От | Tom Lane |
---|---|
Тема | Re: [BUGS] Crash report for some ICU-52 (debian8) COLLATE and work_mem values |
Дата | |
Msg-id | 7355.1502738237@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | Re: [BUGS] Crash report for some ICU-52 (debian8) COLLATE andwork_mem values (Peter Geoghegan <pg@bowt.ie>) |
Ответы |
Re: [BUGS] Crash report for some ICU-52 (debian8) COLLATE andwork_mem values
|
Список | pgsql-bugs |
Peter Geoghegan <pg@bowt.ie> writes: > On Mon, Aug 14, 2017 at 11:32 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote: >> Maybe, if people are okay with a catversion bump this late, we could >> push the ICU descriptions into pg_collation proper, but I think it >> would be fine to leave pg_import_system_collations's behavior in that >> regard alone for v10, too. > I really think we should add a pg_collation column to store ICU's > description of the collation, because that's something that we'll have > to live with forever. Maybe I'm missing something, but I didn't think there would be anything terribly disastrous about having pg_import_system_collations() install these descriptions as comments in v10 and then changing it to put them directly into pg_collation in later versions. We'd have to adapt the behavior of psql's \dO, but that's true no matter when we change that. > I don't think we have pg_import_system_collations's behavior all > worked out just yet. Agreed, but we can probably tweak that without forcing a catversion bump. regards, tom lane -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
В списке pgsql-bugs по дате отправления: