| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | John Naylor <john(dot)naylor(at)enterprisedb(dot)com> |
| Cc: | Michael Paquier <michael(at)paquier(dot)xyz>, Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, Daniel Verite <daniel(at)manitou-mail(dot)org> |
| Subject: | Re: speed up unicode decomposition and recomposition |
| Date: | 2020-10-23 16:07:52 |
| Message-ID: | 207789.1603469272@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
I chanced to do an --enable-coverage test run today, and I got this
weird message during "make coverage-html":
genhtml: WARNING: function data mismatch at /home/postgres/pgsql/src/common/unicode_norm.c:102
I've never seen anything like that before. I suppose it means that
something about 783f0cc64 is a bit fishy, but I don't know what.
The emitted coverage report looks fairly normal anyway. It says
unicode_norm.c has zero test coverage, which is very possibly correct
since I wasn't running in UTF8 encoding, but I'm not entirely sure of
that either.
This is with RHEL8's lcov-1.13-4.el8 package. I suppose the first
question is does anybody else see that?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David G. Johnston | 2020-10-23 16:08:50 | Re: [PATCH] Add section headings to index types doc |
| Previous Message | Simon Riggs | 2020-10-23 16:03:19 | Re: Deleting older versions in unique indexes to avoid page splits |