Thomas Kellerer <spam_eater@gmx.net> writes:
> Tom Lane schrieb am 04.10.2019 um 16:52:
>> No, this thread is a sufficient report. What *would* be a good use
>> of time is to get a stack trace from the crash, if you can.
> I don't know if I did everything correctly, but here it is. I hope it helps
>> icuuc53.dll!0000000064964a80() Unbekannt
> icuuc53.dll!0000000064964c2d() Unbekannt
> icuuc53.dll!0000000064966328() Unbekannt
> icuuc53.dll!0000000064965469() Unbekannt
> icuuc53.dll!000000006495ef28() Unbekannt
> icuuc53.dll!0000000064961501() Unbekannt
> icuuc53.dll!000000006495b330() Unbekannt
> icuuc53.dll!0000000064959b9e() Unbekannt
> icuin53.dll!0000000064a8bd92() Unbekannt
> postgres.exe!get_collation_actual_version(char collprovider, const char * collcollate) Zeile 1533 C
> postgres.exe!DefineCollation(ParseState * pstate, List * names, List * parameters, bool if_not_exists) Zeile 218
C
> postgres.exe!ProcessUtilitySlow(ParseState * pstate, PlannedStmt * pstmt, const char * queryString,
ProcessUtilityContextcontext, ParamListInfoData * params, QueryEnvironment * queryEnv, _DestReceiver * dest, char *
completionTag)Zeile 1292 C
> postgres.exe!standard_ProcessUtility(PlannedStmt * pstmt, const char * queryString, ProcessUtilityContext context,
ParamListInfoData* params, QueryEnvironment * queryEnv, _DestReceiver * dest, char * completionTag) Zeile 933 C
Hm. This trace says that the crash happened somewhere down inside ICU
itself, during the ucol_open() call in get_collation_actual_version().
There isn't much we could have done to mess up the arguments to that
function. That would seem to mean that it's ICU's bug not ours.
Maybe another reason not to be using such an old ICU version :-(.
regards, tom lane