| From: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
|---|---|
| To: | Andrey Borodin <x4mmm(at)yandex-team(dot)ru> |
| Cc: | Sergey Mirvoda <sergey(at)mirvoda(dot)com>, borodin(at)octonica(dot)com, Michael Paquier <michael(at)paquier(dot)xyz>, pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: BUG #15420: Server crash. Segmentation fault when parsing xml file |
| Date: | 2018-10-04 11:47:04 |
| Message-ID: | CAFj8pRAaNk6hnyra6bGwdHYq9dqqbV0hKr0X9tLG7FYzAoEBkQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
čt 4. 10. 2018 v 13:43 odesílatel Andrey Borodin <x4mmm(at)yandex-team(dot)ru>
napsal:
>
>
> 4 окт. 2018 г., в 16:38, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
> написал(а):
>
>
>
>
> Actually we found this error in very fresh intatallation of Ubuntu 16.04
>> and postgres 10.5
>> After that we checked every configuration we have.
>> And only postgres 9.4 works as expected.
>>
>
> This issue is related to libxml2 limits - and it cannot to work with
> modern libxml2 libraries.
>
> Yes, root cause is inside libxml2 code.
>
> Can we protect postmaster from crashing from libxml2 error? There is a
> bunch of PG_TRY there, but it does not help.
>
Unfortunately, no. You cannot to handle crash. PostgreSQL doesn't start
separate process for libxml2 calls, and fault there is fatal.
Regards
Pavel
> Best regards, Andrey Borodin.
>
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Pavel Stehule | 2018-10-04 14:02:56 | Re: BUG #15420: Server crash. Segmentation fault when parsing xml file |
| Previous Message | Andrey Borodin | 2018-10-04 11:43:29 | Re: BUG #15420: Server crash. Segmentation fault when parsing xml file |