| From: | Josh Berkus <josh(at)agliodbs(dot)com> |
|---|---|
| To: | "Sven R(dot) Kunze" <srkunze(at)tbz-pariv(dot)de>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: Reverse Key Index |
| Date: | 2015-02-25 22:31:33 |
| Message-ID: | 54EE4D45.1060704@agliodbs.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On 02/14/2015 10:35 AM, Sven R. Kunze wrote:
> Thanks for the immediate reply.
>
> I understand the use case is quite limited.
>
> On the other hand, I see potential when it comes to applications which
> use PostgreSQL. There, programmers would have to change a lot of code to
> tweak existing (and more importantly working) queries to hash/reverse an
> id column first. Using ORMs would make this change even more painful and
> maybe even impossible.
>
> When reading
> https://richardfoote.wordpress.com/2008/01/14/introduction-to-reverse-key-indexes-part-i/
> carefully, it also seems to work with index scan partially in case of
> equality comparisons.
Seems like a good use for SP-GiST. Go for it!
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Sergey Shchukin | 2015-02-26 06:25:31 | Re: [pgadmin-support] Issue with a hanging apply process on the replica db after vacuum works on primary |
| Previous Message | Sergey Shchukin | 2015-02-24 13:42:06 | Issue with a hanging apply process on the replica db after vacuum works on primary |