Re: strange IS NULL behaviour

On 2013-09-06 23:07:04 -0400, Bruce Momjian wrote:
> On Fri, Sep 6, 2013 at 11:00:24PM -0400, Tom Lane wrote:
> > Bruce Momjian <bruce(at)momjian(dot)us> writes:
> > > On Thu, Sep 5, 2013 at 05:06:41PM -0400, Bruce Momjian wrote:
> > >> Another possible fix would be to avoid the IS NULL value optimizer
> > >> expansion if a ROW construct is inside a ROW(). I have attached a patch
> > >> that does this for review.
> >
> > > Having received no replies, do people perfer this version of the patch
> > > that just punts nested ROW IS NULL testing to execQual.c?
> >
> > For some reason I read your previous message as saying you were willing to
> > wait for considered reviews this time. If not, I'll just write a blanket
> > -1 for any version of this patch.
>
> Are you saying people will comment later? I wasn't clear that was the
> plan. I can certainly wait.

You do realize mere mortals in the project frequently have to wait
*months* to get comments on their patches? Not getting any for less than
48h doesn't seem to be saying much.

Why don't you add the proposal to the commitfest?

Greetings,

Andres Freund

--
Andres Freund http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services