Re: New pg_lsn type doesn't have hash/btree opclasses

From: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
To: Andres Freund <andres(at)2ndquadrant(dot)com>
Cc: PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org>, Robert Haas <robertmhaas(at)gmail(dot)com>, Craig Ringer <craig(at)2ndquadrant(dot)com>
Subject: Re: New pg_lsn type doesn't have hash/btree opclasses
Date: 2014-05-06 23:03:50
Message-ID: CAB7nPqSuGNztUvhPbKuo4V1k=o5Fsq6GjBr39TN3Kd0m8r1cPQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, May 6, 2014 at 10:49 PM, Michael Paquier
<michael(dot)paquier(at)gmail(dot)com> wrote:
> Makes sense, especially knowing operators needed for btree processing
> are already defined. Patch attached solves that.
Please find attached an updated patch, I completely forgot that the
compare function needs to return {-1, 0, 1}.
--
Michael

Attachment Content-Type Size
20140507_pglsn_btree_hash_v2.patch text/plain 6.2 KB

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2014-05-06 23:07:22 Re: New pg_lsn type doesn't have hash/btree opclasses
Previous Message Peter Geoghegan 2014-05-06 23:01:16 Re: default opclass for jsonb (was Re: Call for GIST/GIN/SP-GIST opclass documentation)