Andreas Joseph Krogh <andr...@visena.com> writes:
> PÃ¥ torsdag 17. mars 2016 kl. 18:20:23, skrev Tom Lane <t...@sss.pgh.pa.us
> FWIW, the reason for that is that the int8_ops operator class that
> btree_gin creates doesn't contain any cross-type operators. Probably
> wouldn't be that hard to fix if somebody wanted to put in the work.
> Can you explain why it works when using prepared statement without casting?
If you mean the example
prepare fish AS SELECT del.id , del.received_timestamp FROM delivery del
WHERE 1= 1 AND del.fts_all @@ to_tsquery('simple', $1) AND
del.folder_id = $2 ORDER BY del.received_timestamp DESC LIMIT 101 OFFSET 0;
you didn't provide any type for the parameter $2, so the parser had to
infer a type, and the applicable heuristic here is "same type that's on
the other side of the operator". So you ended up with "bigint = bigint"
which is in the btree_gin operator class. If you'd specified the
parameter's type as integer, it would've worked the same as Evgeniy's
example.
regards, tom lane
--
Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-performance
