[gdulli]

It looks promising. I wanted to try it out but I got this error when it was reading the metadata on my database:

"Encountered more 0 entries in index columns list than there were expressions in 'indexprs' expressions list for index 'activity_emd5_00_expr_activity_type_expr1_idx'. Current count = '1', parsed expressions = 1, 'indexprs' value='({OPEXPR :opno 3963 :opfuncid 3948 :opresulttype 25 :opretset false :opcollid 100 :inputcollid 100 :args ({VAR :varno 1 :varattno 6 :vartype 114 :vartypmod -1 :varcollid 0 :varlevelsup 0 :varnoold 1 :varoattno 6 :location 43} {CONST :consttype 25 :consttypmod -1 :constcollid 100 :constlen -1 :constbyval false :constisnull false :location 60 :constvalue 12 [ 48 0 0 0 118 101 114 116 105 99 97 108 ]}) :location 57} {OPEXPR :opno 3963 :opfuncid 3948 :opresulttype 25 :opretset false :opcollid 100 :inputcollid 100 :args ({VAR :varno 1 :varattno 5 :vartype 114 :vartypmod -1 :varcollid 0 :varlevelsup 0 :varnoold 1 :varoattno 5 :location 89} {CONST :consttype 25 :consttypmod -1 :constcollid 100 :constlen -1 :constbyval false :constisnull false :location 108 :constvalue 6 [ 24 0 0 0 105 100 ]}) :location 105})'"

For your reference, here's that index:

"activity_emd5_00_expr_activity_type_expr1_idx" UNIQUE, btree ((source_details ->> 'vertical'::text), activity_type, (activity_details ->> 'id'::text))

[johnyzee]

Thank you, I will look into this. What is your PG version if I may ask?

[gdulli]

9.3beta2

[johnyzee]

Hey, you might not get this but the issue you reported is now fixed (failure to resolve segmented index expressions after some changes to PG system functions). Thanks for reporting this and let me know if I can help with anything.