Re: best way to fetch next/prev record based on index

Поиск
Список
Период
Сортировка
Искать
От
Greg Stark
Тема
Re: best way to fetch next/prev record based on index
Дата
Msg-id
876587spxw.fsf@stark.xeocode.com
Ответ на
Список
Дерево обсуждения
Re: best way to fetch next/prev record based on index "Merlin Moncure" <merlin.moncure@rcsonline.com>
Re: best way to fetch next/prev record based on index Stephan Szabo <sszabo@megazone.bigpanda.com>
Re: best way to fetch next/prev record based on index Greg Stark <gsstark@mit.edu>
Re: best way to fetch next/prev record based on index Tom Lane <tgl@sss.pgh.pa.us>
Re: best way to fetch next/prev record based on index Greg Stark <gsstark@mit.edu>
Re: best way to fetch next/prev record based on index Tom Lane <tgl@sss.pgh.pa.us>
Re: best way to fetch next/prev record based on index Greg Stark <gsstark@mit.edu>
Re: best way to fetch next/prev record based on index Tom Lane <tgl@sss.pgh.pa.us>
Re: best way to fetch next/prev record based on index Greg Stark <gsstark@mit.edu>

Tom Lane  writes:

> One thing I did not like about your first pass is that it makes
> unsupportable assumptions about there being a semantic relationship
> between operators named, say, '<' and '<='.  

Hm, I think I even had caught that issue on the mailing list previously.

In that case though, it seems even the existing code is insufficient. Instead
of testing whether the operator with strcmp against "=" and "<>" it should
perhaps be looking for an operator class and the strategy number for the
operator and its negator.

-- 
greg
В списке pgsql-performance по дате отправления
От: Tom Lane
Дата:
От: Tom Lane
Дата:
FAQ