Re: NULL passed as an argument to memcmp() in parse_func.c

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: Piotr Stefaniak <postgres(at)piotr-stefaniak(dot)me>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>, joerg(at)NetBSD(dot)org
Subject: Re: NULL passed as an argument to memcmp() in parse_func.c
Date: 2015-07-01 20:23:24
Message-ID: 11313.1435782204@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Andres Freund <andres(at)anarazel(dot)de> writes:
> On 2015-07-01 10:51:49 -0400, Tom Lane wrote:
>> The problem is that there are multiple risks to manage here. If I were to
>> back-patch that patch, it would actively break any third-party extensions
>> that might be using the formerly-considered-valid technique of passing a
>> NULL array pointer to these lookup functions. We don't like breaking
>> things in minor releases; that discourages people from updating to new
>> minor releases.

> Yep, let's just fix it in master (and potentially 9.5, I don't care).

It's in the 9.5 branch already.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2015-07-01 20:33:24 Re: Raising our compiler requirements for 9.6
Previous Message Gavin Flower 2015-07-01 20:17:27 Re: Parallel Seq Scan