| From: | Dmitry Tkach <dmitry(at)openratings(dot)com> |
|---|---|
| To: | Stephan Szabo <sszabo(at)megazone23(dot)bigpanda(dot)com> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Backwards index scan |
| Date: | 2003-07-07 21:58:53 |
| Message-ID: | 3F09ED1D.10106@openratings.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-general pgsql-hackers |
>
>
>If you make an opclass that orders in the reverse order you can use that
>opclass in creating the index (which effectively can give you an index
>like x, y desc by using the new opclass on y). There was some talk
>recently about whether we should provide such opclasses as builtins or
>contrib items.
>
>
Ah! Nice :-)
I did not think about it...
Thanks a lot for the hit!
Dima
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tatsuo Ishii | 2003-07-08 01:14:23 | Re: [HACKERS] again: Bug #943: Server-Encoding from EUC_TW |
| Previous Message | Mike Quinn | 2003-07-07 21:58:01 | pg_tables view definition incorrect?? |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Daniel Armbrust | 2003-07-08 01:39:13 | Website (DNS) is hosed!!! |
| Previous Message | Mike Mascari | 2003-07-07 21:58:00 | Re: making multiple updates use indexes: howto? |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kevin Brown | 2003-07-07 22:48:06 | Re: pg_stat_activity |
| Previous Message | Stephan Szabo | 2003-07-07 21:44:46 | Re: Backwards index scan |