Re: [PATCH] remove deprecated v8.2 containment operators - Mailing list pgsql-hackers

From Tom Lane
Subject Re: [PATCH] remove deprecated v8.2 containment operators
Date
Msg-id 287835.1605283075@sss.pgh.pa.us
Whole thread Raw
In response to Re: [PATCH] remove deprecated v8.2 containment operators  (Peter Eisentraut <peter.eisentraut@enterprisedb.com>)
Responses Re: [PATCH] remove deprecated v8.2 containment operators  (Peter Eisentraut <peter.eisentraut@enterprisedb.com>)
List pgsql-hackers
Peter Eisentraut <peter.eisentraut@enterprisedb.com> writes:
> On 2020-11-12 23:28, Tom Lane wrote:
>> I'm on board with pulling these now --- 8.2 to v14 is plenty of
>> deprecation notice.  However, the patch seems incomplete in that
>> the code support for these is still there -- look for
>> RTOldContainedByStrategyNumber and RTOldContainsStrategyNumber.
>> Admittedly, there's not much to be removed except some case labels,
>> but it still seems like we oughta do that to avoid future confusion.

> Yeah, the stuff in gistproc.c should be removed now.  But I wonder what 
> the mentions in brin_inclusion.c are and whether or how they should be 
> removed.

I think those probably got cargo-culted in there at some point.
They're visibly dead code, because there are no pg_amop entries
for BRIN opclasses with amopstrategy 13 or 14.

This comment that you removed in 2f70fdb06 is suspicious:

    # we could, but choose not to, supply entries for strategies 13 and 14

I'm guessing that somebody was vacillating about whether it'd be
a feature to support these old operator names in BRIN, and
eventually didn't, but forgot to remove the code support.

            regards, tom lane



pgsql-hackers by date:

Previous
From: Stephen Frost
Date:
Subject: Re: WIP: WAL prefetch (another approach)
Next
From: Justin Pryzby
Date:
Subject: error_severity of brin work item