| From: | Andres Freund <andres(at)2ndquadrant(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | 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:44:59 |
| Message-ID: | 20140506134459.GA5658@awork2.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2014-05-06 09:37:54 -0400, Tom Lane wrote:
> Andres Freund <andres(at)2ndquadrant(dot)com> writes:
> > 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.
>
> Sorry, it is *way* too late for 9.4.
It's imo a regression/oversight introduced in the pg_lsn patch. Not a
new feature.
Greetings,
Andres Freund
--
Andres Freund http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Christoph Berg | 2014-05-06 13:46:49 | Re: tab completion for setting search_path |
| Previous Message | Tom Lane | 2014-05-06 13:37:54 | Re: New pg_lsn type doesn't have hash/btree opclasses |