Re: [PATCH] Possible arithmetic with NULL pointer or test "stack_base_ptr != NULL" is irrelevant. - Mailing list pgsql-hackers

From Tom Lane
Subject Re: [PATCH] Possible arithmetic with NULL pointer or test "stack_base_ptr != NULL" is irrelevant.
Date
Msg-id 1871.1574613617@sss.pgh.pa.us
Whole thread Raw
In response to [PATCH] Possible arithmetic with NULL pointer or test "stack_base_ptr!= NULL" is irrelevant.  (Ranier Vilela <ranier_gyn@hotmail.com>)
Responses RE: [PATCH] Possible arithmetic with NULL pointer or test"stack_base_ptr != NULL" is irrelevant.  (Ranier Vilela <ranier_gyn@hotmail.com>)
List pgsql-hackers
Ranier Vilela <ranier_gyn@hotmail.com> writes:
> Of course, I don't know if it's the best solution, but it's the most obvious.
> Or the test at line 3326 is irrelavant.

> \backend\tcop\postgres.c
>     if (stack_depth > max_stack_depth_bytes &&
>         stack_base_ptr != NULL)
>         return true;

> Otherwise, if is relevant, substraction with NULL pointer is technically,undefined behavior..

[ shrug... ]  Stack overflow in itself is outside the realm of the C
specification.  Also, if you want to get nitty-gritty about it,
I believe that the standard only promises defined results from the
subtraction of two pointers that point to elements of the same array
object.  So the change you propose isn't going to make it any closer
to adhering to the letter of "defined-ness".  In practice, this code
works fine on every platform that Postgres is ever likely to support,
so I see no need to change it.

            regards, tom lane



pgsql-hackers by date:

Previous
From: John W Higgins
Date:
Subject: Re: [PATCH] Style, remove redudant test "if (zeropadlen > 0)"
Next
From: Tom Lane
Date:
Subject: Re: [PATCH] Style, remove redudant test "if (zeropadlen > 0)"