| From: | Peter Geoghegan <pg(at)bowt(dot)ie> |
|---|---|
| To: | Daniel Verite <daniel(at)manitou-mail(dot)org> |
| Cc: | PostgreSQL mailing lists <pgsql-bugs(at)postgresql(dot)org>, Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
| Subject: | Re: Crash report for some ICU-52 (debian8) COLLATE and work_mem values |
| Date: | 2017-08-03 19:19:24 |
| Message-ID: | CAH2-Wz=K2v7p9du0zVXspj=tk3QWKEXNpBU=-VB+0Ys-2tFgfQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-hackers |
On Thu, Aug 3, 2017 at 8:49 AM, Daniel Verite <daniel(at)manitou-mail(dot)org> wrote:
> With query #1 the run goes to completion without crashing (hi heisenbug!),
> but it reports many uses of uninitialised values under ucol_strcollUTF8().
> The full log is attached in log-valgrind-1.txt.gz
>
>
> With query #2 it ends up crashing after ~5hours and produces
> the log in log-valgrind-2.txt.gz with some other entries than
> case #1, but AFAICS still all about reading uninitialised values
> in space allocated by datumCopy().
It would be nice if you could confirm whether or not Valgrind
complains when non-ICU collations are in use. It may just have been
that we get (un)lucky with ICU, where the undefined behavior happens
to result in a hard crash, more or less by accident.
--
Peter Geoghegan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dean Franken | 2017-08-04 02:55:02 | Unable to completely drop pgagent schema |
| Previous Message | Peter Geoghegan | 2017-08-03 18:42:25 | Re: Crash report for some ICU-52 (debian8) COLLATE and work_mem values |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2017-08-03 20:14:45 | xmltable SQL conformance |
| Previous Message | Oliver Ford | 2017-08-03 18:54:48 | Re: Add Roman numeral conversion to to_number |