Re: New pg_lsn type doesn't have hash/btree opclasses - Mailing list pgsql-hackers

From Michael Paquier
Subject Re: New pg_lsn type doesn't have hash/btree opclasses
Date
Msg-id CAB7nPqT-TuPOBWUgFmkTemSY0fDgtvK4s+zmp-h6ee9Z9e+FKg@mail.gmail.com
Whole thread Raw
In response to Re: New pg_lsn type doesn't have hash/btree opclasses  (Fujii Masao <masao.fujii@gmail.com>)
Responses Re: New pg_lsn type doesn't have hash/btree opclasses  (Andres Freund <andres@2ndquadrant.com>)
List pgsql-hackers
On Fri, May 9, 2014 at 10:01 PM, Fujii Masao <masao.fujii@gmail.com> wrote:
> +DATA(insert OID = 3260 (    403        pglsn_ops        PGNSP PGUID ));
> +DATA(insert OID = 3261 (    405        pglsn_ops        PGNSP PGUID ));
>
> The patch looks good to me except the name of index operator class.
> I think that "pg_lsn_ops" is better than "pglsn_ops" because it's for "pg_lsn"
> data type.
Well, yes... Btw, before doing anything with this patch, I think that
the version of Fabrizio could be used as a base, but the regression
tests should be reshuffled a bit...
-- 
Michael



pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: Cache lookup error when using jsonb, json_build_object and a WITH clause
Next
From: Andres Freund
Date:
Subject: Re: New pg_lsn type doesn't have hash/btree opclasses