| From: | Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk> |
|---|---|
| To: | Kevin Grittner <kgrittn(at)gmail(dot)com> |
| Cc: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, 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>, 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-09 15:18:10 |
| Message-ID: | 8737meashg.fsf@news-spur.riddles.org.uk |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
>>>>> "Kevin" == Kevin Grittner <kgrittn(at)gmail(dot)com> writes:
>>> 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?
Kevin> Andrew's patch, plus this, covers everything I can think of.
Where'd be a good place to put that function? ruleutils? catalog/index.c ?
(ruleutils is way too big already)
--
Andrew (irc:RhodiumToad)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2016-08-09 15:26:29 | Re: No longer possible to query catalogs for index capabilities? |
| Previous Message | Amit Kapila | 2016-08-09 13:19:01 | Re: [sqlsmith] Failed assertion in joinrels.c |