Postgres Pro
Downloads
Home   >   mailing lists

Re: [BUGS] Crash report for some ICU-52 (debian8) COLLATE and work_mem values - Mailing list pgsql-bugs

From Tom Lane
Subject Re: [BUGS] Crash report for some ICU-52 (debian8) COLLATE and work_mem values
Date
Msg-id 25202.1502752318@sss.pgh.pa.us
Whole thread Raw
In response to Re: [BUGS] Crash report for some ICU-52 (debian8) COLLATE andwork_mem values  (Peter Geoghegan <pg@bowt.ie>)
Responses Re: [BUGS] Crash report for some ICU-52 (debian8) COLLATE andwork_mem values
List pgsql-bugs
Tree view 
Peter Geoghegan <pg@bowt.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


-- 
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 by date:

Previous
From: Peter Geoghegan
Date:
Subject: Re: [BUGS] Crash report for some ICU-52 (debian8) COLLATE andwork_mem values
Next
From: Masahiko Sawada
Date:
Subject: Re: [BUGS] BUG #14775: Incorrect documentation for the Commit logicalreplication message format