Hi All, During my journey of designing Pg based solution at my work I was severely hit by several shortcomings in GiST. The most severe one is the lack of support for SAOP filters as it makes it difficult to have partition pruning and index (only) scans working together.
To overcome the difficulties I implemented a simple extension: https://github.com/mkleczek/btree_gist_extra mkleczek/btree_gist_extra: Extra operators support for PostgreSQL btree_gist github.com Since it provides a separate operator class from btree_gist it requires re-indexing the data. So I thought maybe it would be a good idea to incorporate it into btree_gist. I am aware of two patches related to SAOP being discussed at the moment but I am not sure if SAOP support for GiST indexes is planned. Let me know if you think it is a good idea to work on a patch. More general remark: I am wondering if SAOP support in core should not be implemented by mapping SAOP operations to specialised operators and delegating all the work to index AMs. That way core could be decoupled from particular index AMs implementation details. Thanks! — Michal
