Re: [PATCH][BUG FIX] Unsafe access pointers. - Mailing list pgsql-hackers

From Daniel Gustafsson
Subject Re: [PATCH][BUG FIX] Unsafe access pointers.
Date
Msg-id FCE1BDEF-8B51-4AC2-9FE7-B885B3CFA321@yesql.se
Whole thread Raw
In response to [PATCH][BUG FIX] Unsafe access pointers.  (Ranier Vilela <ranier_gyn@hotmail.com>)
Responses RE: [PATCH][BUG FIX] Unsafe access pointers.  (Ranier Vilela <ranier_gyn@hotmail.com>)
List pgsql-hackers
> On 15 Nov 2019, at 12:25, Ranier Vilela <ranier_gyn@hotmail.com> wrote:

> It's probably not happening, but it can happen, I think.

I don't think it can, given how elog() works.

> -    if (!HeapTupleIsValid(classtup))
> +    if (!HeapTupleIsValid(classtup)) {
>         elog(ERROR, "cache lookup failed for operator class %u", opclassoid);
> +        return false;

elog or ereport with a severity of ERROR or higher will never return.

> -    if (!HeapTupleIsValid(familytup))
> +    if (!HeapTupleIsValid(familytup)) {
>         elog(ERROR, "cache lookup failed for operator family %u", opfamilyoid);
> +        ReleaseSysCache(classtup);
> +        return false;
> +    }

Not only will elog(ERROR ..) not return to run this, the errorhandling
machinery will automatically release resources and clean up.

cheers ./daniel



pgsql-hackers by date:

Previous
From: Ranier Vilela
Date:
Subject: [PATCH][BUG FIX] Unsafe access pointers.
Next
From: Fabien COELHO
Date:
Subject: Re: segfault in geqo on experimental gcc animal