Re: constraint exclusion and nulls in IN (..) clause

From: Amit Langote <Langote_Amit_f8(at)lab(dot)ntt(dot)co(dot)jp>
To: emre(at)hasegeli(dot)com
Cc: Ashutosh Bapat <ashutosh(dot)bapat(at)enterprisedb(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: constraint exclusion and nulls in IN (..) clause
Date: 2018-03-06 10:20:10
Message-ID: 2eb0c3bf-cf7a-1937-df24-5c19f3145cc8@lab.ntt.co.jp
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 2018/03/06 19:16, Emre Hasegeli wrote:
>> Hmm, state->next refers to two different pointer values on line 1 and line
>> 2. It may end up being set to NULL on line 1. Am I missing something?
>
> True, lnext(state->next) can set it to NULL. I confused by the below
> code on the same function doing the steps in reverse order. With this
> cleared, I have nothing else to say, so I am setting this to ready for
> committer.

Thanks. :)

Regards,
Amit

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Jeevan Chalke 2018-03-06 10:31:35 Re: [HACKERS] Partition-wise aggregation/grouping
Previous Message Emre Hasegeli 2018-03-06 10:16:11 Re: constraint exclusion and nulls in IN (..) clause