postgres does a seqscan, even though there is an index present and it should be much more efficient to use it.I tried to synthetically reproduce it, but it won't make the same choice when i do.I can reproduce it with a simplified set of the data itself though.here's the query, and the analyzed plan:select count(*) from d2join g2 on g2.gid=d2.gidwhere g2.k=1942
pgsql-performance by date:
Соглашаюсь с условиями обработки персональных данных