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

From: Emre Hasegeli <emre(at)hasegeli(dot)com>
To: Amit Langote <Langote_Amit_f8(at)lab(dot)ntt(dot)co(dot)jp>
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:16:11
Message-ID: CAE2gYzwUL90jOSOxFhxhG7VWGgT0f+v8=SMyj1S-HKqUbZPP5g@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> 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.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Amit Langote 2018-03-06 10:20:10 Re: constraint exclusion and nulls in IN (..) clause
Previous Message Amit Langote 2018-03-06 10:10:53 Re: constraint exclusion and nulls in IN (..) clause