Re: BUG #17126: Server crashes on dropping user while enumerating owned objects that are droppped concurrently

From: Alexander Lakhin <exclusion(at)gmail(dot)com>
To: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #17126: Server crashes on dropping user while enumerating owned objects that are droppped concurrently
Date: 2021-09-02 04:00:01
Message-ID: 07fc0336-1b28-8269-d7cc-c34d50c650ce@gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Hello Alvaro,
28.07.2021 23:01, Alvaro Herrera wrote:
> On 2021-Jul-28, PG Bug reporting form wrote:
>
>> Dropping a user that owns a number of procedures, while some of them are
>> being dropped, can cause the server crash:
>> There's many places that deal correctly with the possibility that
>> getObjectDescription() would return NULL, but I found two places that
>> don't.
I've found another one in dependency.c:

        else if (behavior == DROP_RESTRICT)
        {
            char       *otherDesc = getObjectDescription(&extra->dependee,
                                                         false);
...
            pfree(otherDesc);
I couldn't trigger a failure at this place yet, but maybe it's worth to
fix here too.

Best regards,
Alexander

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Peter Eisentraut 2021-09-02 08:15:37 Re: BUG #17158: Distinct ROW fails with Postgres 14
Previous Message Etsuro Fujita 2021-09-02 02:56:25 Re: BUG #16583: merge join on tables with different DB collation behind postgres_fdw fails