| 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 13:49:07 |
| Message-ID: | CAB7nPqSNgr4OQQOGkONtmNBM+ybE1YzBm5TPEd6j=PJcM=jUkw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, May 6, 2014 at 4:14 PM, Andres Freund <andres(at)2ndquadrant(dot)com> wrote:
> Hi,
>
> Craig just mentioned in an internal chat that there's no btree or even
> hash opclass for the new pg_lsn type. That restricts what you can do
> with it quite severely.
> Imo this should be fixed for 9.4 - after all it was possible unto now to
> index a table with lsns returned by system functions or have queries
> with grouping on them without casting.
Makes sense, especially knowing operators needed for btree processing
are already defined. Patch attached solves that. Now to include it in
9.4 where development is over is another story... I wouldn't mind
adding it to the next commit fest either.
Regards,
--
Michael
| Attachment | Content-Type | Size |
|---|---|---|
| 20140506_pglsn_btree_hash.patch | text/plain | 6.5 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Nicolas Barbier | 2014-05-06 13:53:54 | Re: 9.4 release notes |
| Previous Message | Robert Haas | 2014-05-06 13:49:04 | Re: sb_alloc: a new memory allocator for PostgreSQL |