Re: BUG #17326: Postgres crashed when pg_reload_conf() with ssl certificate parameters

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Dmitry Dolgov <9erthalion6(at)gmail(dot)com>
Cc: "James Pang (chaolpan)" <chaolpan(at)cisco(dot)com>, "pgsql-bugs(at)lists(dot)postgresql(dot)org" <pgsql-bugs(at)lists(dot)postgresql(dot)org>
Subject: Re: BUG #17326: Postgres crashed when pg_reload_conf() with ssl certificate parameters
Date: 2021-12-15 01:33:40
Message-ID: YblF9NopbGHQ65/G@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Tue, Dec 14, 2021 at 06:36:54PM +0100, Dmitry Dolgov wrote:
> something weird happens after set_extra_field, and after this point ssl
> context memory seems to be corrupted. Right before that an assign_hook
> from set_user is invoked to do something around "deprecated" options,
> that's why it looks suspicious. As soon as no "deprecated" options left
> in the config the issue disappears.

Hmm, okay. Thanks. I have no idea if this extension is doing
something it should not, but I'd like to keep in mind that there could
be something that could be improved in core depending on what this
module is trying to achieve. At least that's a possibility.
--
Michael

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message James Pang (chaolpan) 2021-12-15 02:54:51 RE: BUG #17326: Postgres crashed when pg_reload_conf() with ssl certificate parameters
Previous Message Peter Geoghegan 2021-12-15 00:02:23 Re: When Update balloons memory