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

From: Andres Freund <andres(at)anarazel(dot)de>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
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 18:00:59
Message-ID: 20150701180059.GF30708@awork2.anarazel.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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

Regards,

Andres

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Geoghegan 2015-07-01 18:05:57 Re: Raising our compiler requirements for 9.6
Previous Message Peter Geoghegan 2015-07-01 17:59:09 Re: Refactoring speculative insertion with unique indexes a little