Re: Searching GIN-index (FTS) and sort by timestamp-column

På onsdag 16. mars 2016 kl. 16:04:08, skrev Evgeniy Shishkin <
itparanoia(at)gmail(dot)com <mailto:itparanoia(at)gmail(dot)com>>:

> On 16 Mar 2016, at 17:52, Evgeniy Shishkin <itparanoia(at)gmail(dot)com> wrote:
>
>
>> On 16 Mar 2016, at 16:37, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>>
>> Andreas Joseph Krogh <andreas(at)visena(dot)com> writes:
>>> 1. Why isnt' folder_id part of the index-cond?
>>
>> Because a GIN index is useless for sorting.
>
> I don't see how gin inability to return sorted data relates to index
condition.
> In fact i tried to reproduce the example,
> and if i change folder_id to int from bigint, then index condition with
folder_id is used
>
>         Index Cond: ((fts_all @@ '''hi'''::tsquery) AND (folder_id = 1))
>

Looks like documentation
http://www.postgresql.org/docs/9.5/static/btree-gin.html
is lying about supporting int8 type
 
Hm, interesting!
 
@Tom: Any idea why BIGINT doesn't work, but INTEGER does?
 
-- Andreas Joseph Krogh
CTO / Partner - Visena AS
Mobile: +47 909 56 963
andreas(at)visena(dot)com <mailto:andreas(at)visena(dot)com>
www.visena.com <https://www.visena.com>
<https://www.visena.com>