| From: | Kevin Grittner <kgrittn(at)gmail(dot)com> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Stephen Frost <sfrost(at)snowman(dot)net>, Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk>, Robert Haas <robertmhaas(at)gmail(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: No longer possible to query catalogs for index capabilities? |
| Date: | 2016-08-08 20:13:15 |
| Message-ID: | CACjxUsMT5OtjEYa5NrypmEs=5yAecTUm2qdypRXo5O8+tHiZ+g@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sun, Aug 7, 2016 at 11:53 PM, Alvaro Herrera
<alvherre(at)2ndquadrant(dot)com> wrote:
>> Building on the has-property approach Andrew suggested, I wonder if
>> we need something like pg_index_column_has_property(indexoid, colno,
>> propertyname) with properties like "sortable", "desc", "nulls first".
>
> This seems simple enough, on the surface. Why not run with this design?
Andrew's patch, plus this, covers everything I can think of.
--
Kevin Grittner
EDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2016-08-08 20:19:08 | Re: Heap WARM Tuples - Design Draft |
| Previous Message | Peter Geoghegan | 2016-08-08 19:44:02 | Parallel tuplesort, partitioning, merging, and the future |