News for hackers. Stuff that matters.

A comment on Writing a MySQL storage engine from scratch (2016).

Re:Writing a MySQL storage engine from scratch (2016) by anton_gogolev on Thursday June 15, 2017 @04:13AM (#14558688)
Oh, and it becomes painfully obvious why MySQL cannot use more than one index while executing the query.
[ Parent | on HN ]
Re:Writing a MySQL storage engine from scratch (2016) by morgo on Thursday June 15, 2017 @06:38AM (#14559189)
It has been able to use more than one index per table since MySQL 5.0 (2005):

https://dev.mysql.com/doc/refman/5.7/en/index-merge-optimiza...

[ Parent | on HN ]
Re:Writing a MySQL storage engine from scratch (2016) by hoschicz on Thursday June 15, 2017 @06:22AM (#14559144)
Can PostgreSQL use more than one index per table while executing a query?
[ Parent | on HN ]
Re:Writing a MySQL storage engine from scratch (2016) by anton_gogolev on Thursday June 15, 2017 @06:43AM (#14559213)
Absolutely: https://www.postgresql.org/docs/8.3/static/indexes-bitmap-sc...
[ Parent | on HN ]
Re:Writing a MySQL storage engine from scratch (2016) by sfilargi on Thursday June 15, 2017 @04:30AM (#14558740)
one index per table

(Sorry for being pedantic)

[ Parent | on HN ]