| From: | Michael Paquier <michael(at)paquier(dot)xyz> |
|---|---|
| To: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
| Cc: | Sergey Mirvoda <sergey(at)mirvoda(dot)com>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Andrey Borodin <x4mmm(at)yandex-team(dot)ru>, Andrew Borodin <borodin(at)octonica(dot)com>, pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: BUG #15420: Server crash. Segmentation fault when parsing xml file |
| Date: | 2018-10-04 23:27:06 |
| Message-ID: | 20181004232706.GA1629@paquier.xyz |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Thu, Oct 04, 2018 at 05:02:05PM +0200, Pavel Stehule wrote:
> čt 4. 10. 2018 v 16:42 odesílatel Sergey Mirvoda <sergey(at)mirvoda(dot)com>
> napsal:
>> Sure, but bug is mostly about unhandled server crash. Is it normal?
>
> Nobody can handle process crash. This should be fixed on libxml2 side.
If some code crashes in glibc or within a system call, impacting
Postgres backends, there is usually little to do, and the correct call
is to fix the place where the problem happens. If libxml2 has
integrated with a new API which is considered safer to use, then we
could consider working on improving Postgres regarding that aspect.
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Gierth | 2018-10-05 03:40:57 | Re: BUG #15420: Server crash. Segmentation fault when parsing xml file |
| Previous Message | Pavel Stehule | 2018-10-04 15:02:05 | Re: BUG #15420: Server crash. Segmentation fault when parsing xml file |