From: | Greg Stark <stark(at)mit(dot)edu> |
---|---|
To: | Peter Geoghegan <pg(at)bowt(dot)ie> |
Cc: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: RFC: Key normalization for nbtree |
Date: | 2017-07-10 23:08:54 |
Message-ID: | CAM-w4HPRrXZY-gMYxPkWPV8QqeEDB3EptW9FtuPiWM=fPB==vg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 10 July 2017 at 19:40, Peter Geoghegan <pg(at)bowt(dot)ie> wrote:
> Key normalization means creating a representation for internal page
> items that we always just memcmp(), regardless of the details of the
> underlying datatypes.
One thing I would like to see is features like this added to the
opclasses (or opfamilies?) using standard PG functions that return
standard PG data types. So if each opclass had a function that took
the data type in question and returned a bytea then you could
implement that function using a language you felt like (in theory),
test it using standard SQL, and possibly even find other uses for it.
That kind of abstraction would be more promising for the future than
having yet another C api that is used for precisely one purpose and
whose definition is "provide the data needed for this usage".
--
greg
From | Date | Subject | |
---|---|---|---|
Next Message | Greg Stark | 2017-07-10 23:17:39 | Re: New partitioning - some feedback |
Previous Message | Claudio Freire | 2017-07-10 23:04:42 | Re: Vacuum: allow usage of more than 1GB of work mem |