Re: Decouple operator classes from index access methods

From: Emre Hasegeli <emre(at)hasegeli(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Decouple operator classes from index access methods
Date: 2021-06-22 17:21:28
Message-ID: CAE2gYzxEsKntCNGC3XeAzKnQNgNLy=2kEPxu=ax85056gGnS-g@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> I can see some value perhaps in letting other opclasses refer to
> btree and hash opclasses rather than duplicating their entries.
> But that doesn't seem to be what you're proposing here.

That's what I am proposing. My idea is to change the current btree
and hash opclasses to be under the new proposed access methods so
btree, hash, and any other index access method can refer to them.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Fabien COELHO 2021-06-22 18:03:58 Re: [HACKERS] WIP aPatch: Pgbench Serialization and deadlock errors
Previous Message Tom Lane 2021-06-22 17:13:08 Re: Assertion failure in HEAD and 13 after calling COMMIT in a stored proc