| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Peter Geoghegan <pg(at)bowt(dot)ie> |
| Cc: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Daniel Verite <daniel(at)manitou-mail(dot)org>, PostgreSQL mailing lists <pgsql-bugs(at)postgresql(dot)org> |
| Subject: | Re: Crash report for some ICU-52 (debian8) COLLATE and work_mem values |
| Date: | 2017-08-14 23:11:58 |
| Message-ID: | 25202.1502752318@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-hackers |
Peter Geoghegan <pg(at)bowt(dot)ie> writes:
> Do we really need to pass "if_not_exists = true", anyway? Why
> shouldn't initdb fail if there are apparent duplicate ICU collations?
Because the villagers will come after you; see commit
0b13b2a7712b6f91590b7589a314240a14520c2f.
It's possible that there's an argument for not de-duplicating ICU
collation names even though we must do so for libc collation names.
But I'm not exactly sure what that would be. Having initdb fail if
the ICU configuration is funny isn't going to endear us to anyone.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Masahiko Sawada | 2017-08-15 01:30:46 | Re: BUG #14775: Incorrect documentation for the Commit logical replication message format |
| Previous Message | Peter Geoghegan | 2017-08-14 22:35:24 | Re: Crash report for some ICU-52 (debian8) COLLATE and work_mem values |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2017-08-14 23:16:39 | Re: shared memory based stat collector (was: Sharing record typmods between backends) |
| Previous Message | Peter Eisentraut | 2017-08-14 23:00:43 | Re: postgres_fdw: evaluate placeholdervars on remote server |