Re: Remove IndexInfo.ii_OpclassOptions field

From: Peter Eisentraut <peter(at)eisentraut(dot)org>
To: Michael Paquier <michael(at)paquier(dot)xyz>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Remove IndexInfo.ii_OpclassOptions field
Date: 2023-10-03 15:56:08
Message-ID: 06370f1c-ce6a-6a04-7d7c-72fbd081ea25@eisentraut.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 30.08.23 02:51, Michael Paquier wrote:
> On Tue, Aug 29, 2023 at 10:51:10AM +0200, Peter Eisentraut wrote:
>> At a glance, however, I think my patch is (a) not related, and (b) if it
>> were, it would probably *help*, because the change is to not allocate any
>> long-lived structures that no one needs and that might get out of date.
>
> Hmm, yeah, perhaps you're right about (b) here. I have a few other
> high-priority items for stable branches on my board before being able
> to look at all this in more details, unfortunately, so feel free to
> ignore me if you think that this is an improvement anyway even
> regarding the other issue discussed.

I have committed this.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message shveta malik 2023-10-03 15:57:23 Re: Synchronizing slots from primary to standby
Previous Message Vik Fearing 2023-10-03 15:49:22 Re: Allow deleting enumerated values from an existing enumerated data type