Hello
I have CURSOR for query SELECT a FROM table ORDER BY xyz, where table
a is extremely large and xyz is hard-to-evaluate, but indexable
expression(using gist).
As far as I understand, on
SELECT a FROM table ORDER BY xyz LIMIT X
query postgres do not fetch entire index or table, but it uses "n
ank does not use index
> because index does not store enough information for ranking:
> http://archives.postgresql.org/pgsql-general/2011-07/msg00351.php
>
> On Sat, Feb 18, 2012 at 12:39, Andrey Chursin wrote:
>>
>> Hello
>>
>> I have two unrelated questions ab
Hello.
My application need to set advisory lock on UUID key, almost like it
does pg_advisory_xact_lock function. The problem is argument type of
this function - it consumes 8-byte value, not 16-byte.
I can not lock on any(hi, low or middle) 8-byte part of UUID, as far
as it can produce unexpected
Hello
I have two unrelated questions about fts function ts_rank:
1) I've created GiST index on column with fts vector, but query
SELECT * FROM table ORDER BY ts_rank(field, :query) LIMIT 20
is perfomed with sequential table scan. Index was created on field
column. Does it mean FTS indexes does no
