postgresql - How can I get an hstore query that searches multiple terms to use indexes? -


i have query underperforming, data hstore column:

select "vouchers".* "vouchers" "vouchers"."type" in ('vouchertype') , ((data -> 'giver_id')::integer = 1) , ((data -> 'recipient_email') null)

i've tried adding following indexes:

create index free_boxes_recipient on vouchers using gin ((data->'recipient_email')) ((data->'recipient_email') null);

create index voucher_type_giver on vouchers using gin ((data->'giver_id')::int)

as overall index: create index voucher_type_data on vouchers using gin (data)

here's current query plan:

seq scan on vouchers  (cost=0.00..15158.70 rows=5 width=125) (actual time=122.818..122.818 rows=0 loops=1)   filter: (((data -> 'recipient_email'::text) null) , ((type)::text = 'vouchertype'::text) , (((data -> 'giver_id'::text))::integer = 1))   rows removed filter: 335148 planning time: 0.196 ms execution time: 122.860 ms

how can index hstore column down more reasonable query?

for the documentation:

hstore has gist , gin index support @>, ?, ?& , ?| operators.

you searching integer value can use simple btree index this:

create index on vouchers (((data->'giver_id')::int));  explain analyse select *  vouchers vtype in ('vouchertype')  , (data -> 'giver_id')::integer = 1  , (data -> 'recipient_email') null;                                                           query plan                                                          ----------------------------------------------------------------------------------------------------------------------------  bitmap heap scan on vouchers  (cost=4.66..82.19 rows=1 width=34) (actual time=0.750..0.858 rows=95 loops=1)    recheck cond: (((data -> 'giver_id'::text))::integer = 1)    filter: (((data -> 'recipient_email'::text) null) , (vtype = 'vouchertype'::text))    heap blocks: exact=62    ->  bitmap index scan on vouchers_int4_idx  (cost=0.00..4.66 rows=50 width=0) (actual time=0.018..0.018 rows=95 loops=1)          index cond: (((data -> 'giver_id'::text))::integer = 1)  planning time: 2.115 ms  execution time: 0.896 ms (8 rows)

Comments

Post a Comment

Popular posts from this blog

jOOQ update returning clause with Oracle -

according http://www.jooq.org/doc/3.8/manual/sql-building/sql-statements/update-statement/ jooq doesn't support returning clause in update statements databases except firebird , postgres. does know, still correct oracle jooq? according oracle's documentation, oracle db supports returning clase delete, insert, or update statements. incorrect manual you're right - manual wrong , should fixed: https://github.com/jooq/jooq/issues/5470 single row update returning jooq 3.8 added support single row update .. returning statements. internally, uses callablestatement , pl/sql block of form: begin update "my_table" set "my_table"."column" = 'xyz' "my_table"."id" = 1 returning "my_table"."id", "my_table"."column" ?, ?; ? := sql%rowcount; end; the relevant issue is: https://github.com/jooq/jooq/issues/5190 multi row update returning a...
Read more

java - Warning equals/hashCode on @Data annotation lombok with inheritance -

i have entity inherits other. on other hand, i'm using lombok project reduce boilerplate code, put @data annotation. annotation @data inheritance produces next warning: generating equals/hashcode implementation without call superclass, though class not extend java.lang.object. if intentional, add '@equalsandhashcode(callsuper=false)' type. is advisable add annotation @equalsandhashcode (callsuper = true) or @equalsandhashcode (callsuper = false) ? if not added, 1 callsuper=false or callsuper=true ? the default value false . 1 if don't specify , ignore warning. yes, recommended add @equalsandhashcode annotation on @data annotated classes extend else object. cannot tell if need true or false , depends on class hierarchy, , need examined on case-by-case basis. however, project or package, can configure in lombok.config call super methods if not direct subclass of object. lombok.equalsandhashcode.callsuper = call for configuration system ...
Read more

java - BasicPathUsageException: Cannot join to attribute of basic type -

i using java 8 jpa (hibernate 5.2.1). have clause works perfectly, until introduce clause make use foreign key table values too. i getting following error: basicpathusageexception: cannot join attribute of basic type i think problem related fact have join table, , not sure how create join using join table. employee - employee_category - category model (employee.java): @manytomany(cascade = cascadetype.all, fetch=fetchtype.eager) @jointable ( name="employee_category", joincolumns={ @joincolumn(name="emp_id", referencedcolumnname="id") }, inversejoincolumns={ @joincolumn(name="cat_id", referencedcolumnname="id") } ) private set<category> categories; model (category.java): @id private string id; jpa when introduce following code, fails error above (i think problem new piece of code): join<t, category> category = from.join("id"); predicates.add(criteriabuilder.like(category....
Read more