Re: SQL:2011 application time

From: Peter Eisentraut <peter(at)eisentraut(dot)org>
To: Paul Jungwirth <pj(at)illuminatedcomputing(dot)com>, jian he <jian(dot)universality(at)gmail(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: SQL:2011 application time
Date: 2023-11-23 09:08:54
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers

On 20.11.23 08:58, Peter Eisentraut wrote:
> On 17.11.23 19:39, Paul Jungwirth wrote:
>> But I feel the overall approach is wrong: originally I used hardcoded
>> "=" and "&&" operators, and you asked me to look them up by strategy
>> number instead. But that leads to trouble with core gist types vs
>> btree_gist types. The core gist opclasses use RT*StrategyNumbers, but
>> btree_gist creates opclasses with BT*StrategyNumbers.
> Ouch.
> That also provides the answer to my question #2 here:
> I don't have a good idea about this right now.  Could we just change
> btree_gist perhaps?  Do we need a new API for this somewhere?

After further thought, I think the right solution is to change
btree_gist (and probably also btree_gin) to use the common RT* strategy
numbers. The strategy numbers are the right interface to determine the
semantics of index AM operators. It's just that until now, nothing
external has needed this information from gist indexes (unlike btree,
hash), so it has been a free-for-all.

I don't see an ALTER OPERATOR CLASS command that could be used to
implement this. Maybe we could get away with a direct catalog UPDATE.
Or we need to make some DDL for this.

Alternatively, this could be the time to reconsider moving this into core.

In response to


Browse pgsql-hackers by date

  From Date Subject
Next Message Heikki Linnakangas 2023-11-23 09:19:14 Re: psql not responding to SIGINT upon db reconnection
Previous Message Amit Kapila 2023-11-23 09:03:14 Re: pgoutput incorrectly replaces missing values with NULL since PostgreSQL 15