jrgemignani commented on issue #1235: URL: https://github.com/apache/age/issues/1235#issuecomment-1771393550
I do want to point out the following - Being able to create an index is no guarantee that PostgreSQL will actually use it. PostgreSQL makes decisions on whether to use an index or not. A good example is in the `BitmapAnd` above. Depending on how PostgreSQL weights it, it may not use the indexes within at all, or maybe just one. I just don't want anyone assuming that the lack of an index being used means that it isn't working - as long as you are able to create that index. Additionally, sometimes having multiple indexes can actually have worse performance than no index at all. Again, that `BitmapAnd` above is a good example. In tests from the original issue, GIN indexes actually performed worse than BTree indexes and the two combined performed worse than just running the query without, for large datasets. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@age.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
