Re: setting up scan keys
От | Tom Lane |
---|---|
Тема | Re: setting up scan keys |
Дата | |
Msg-id | 19973.1251207195@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | setting up scan keys ("Markus Wanner" <markus@bluegap.ch>) |
Ответы |
Re: setting up scan keys
|
Список | pgsql-hackers |
"Markus Wanner" <markus@bluegap.ch> writes: > Up until now I've used something along the following lines to setup > the scan keys for a BTGreaterStrategy scan: > procinfo = index_getprocinfo(index_rel, i + 1, BTORDER_PROC); > ScanKeyEntryInitializeWithInfo(&skeys[i], > SK_ROW_MEMBER, > (AttrNumber) (i + 1), > strategy, > InvalidOid, > procinfo, > value); Either the SK_ROW_MEMBER flag is entirely wrong, or this is part of a larger structure that you're not telling us about. But also, from anywhere outside the btree index AM itself you should not be dealing in the support function. The scankey is supposed to refer to an operator's underlying function. Your second try looks a bit saner, but it's still using SK_ROW_MEMBER ... why? regards, tom lane
В списке pgsql-hackers по дате отправления: