Arnaud Lesauvage <thewild@xxxxxxxxxxx> writes: > Indeed, the new query does not perform that well : > "Hash Join (cost=112.75..307504.97 rows=2024869 width=355) (actual time=53.995..246443.811 rows=2020061 loops=1)" > ... > "Total runtime: 2777844.892 ms" > I removed all unnecessary indexes on t1 before running the query (I left the index on uid and the multicolumn index containind the updated field). > I believe the multicolumn-functional-index computation is taking some time here, isn't it ? Given that the plan itself only takes 246 sec, there's *something* associated with row insertion that's eating the other 2500+ seconds. Either index entry computation or constraint checking ... regards, tom lane
