Hello pslawek83,
as Sergei has already told you, the issue is not the uniqueness of the
indexes.
Some notes after reading your queries and the tables:
- I see two versions of the query, one having `attrib=5`, the other without.
- on table raw_stats_lookup, you do not have an index on (domain, id
IMO, MariaDB (like MySQL) would better issue a warning when trying to create a
hash index and the engine does not support it. I'm not surprised if someone
thinks that all engines support hash :)
Regards
Federico
Gio 6/3/14, Sergei Golubchik ha scri
Ok i wasn't able to reproduce the issue fully, now data is different ... but
again, "skipped rows" number changes, and index sizes differ a lot:
Uniq index:
http://screencast.com/t/SrBS1L5xeB8
http://screencast.com/t/3dVMU7b69AH2
Normal index:
http://screencast.com/t/Zl5Jm2OZ
http://screencast.com
ok sergei! thanks :) maybe gsoc idea/jira task?
2014-03-06 14:33 GMT-03:00 Sergei Golubchik :
> Hi, Roberto!
>
> On Mar 06, Roberto Spadim wrote:
> > Hello! Only btree, no hash indexes?
>
> Aria? Yes. b-tree and r-tree, no hash indexes.
>
> > > Aria only supports BTREE indexes anyway.
>
> Regard
Hi, Roberto!
On Mar 06, Roberto Spadim wrote:
> Hello! Only btree, no hash indexes?
Aria? Yes. b-tree and r-tree, no hash indexes.
> > Aria only supports BTREE indexes anyway.
Regards,
Sergei
___
Mailing list: https://launchpad.net/~maria-discuss
Pos
Hello! Only btree, no hash indexes?
2014-03-06 13:46 GMT-03:00 Sergei Golubchik :
> Hi, pslawek83!
>
> On Feb 17, pslawek83 wrote:
> > Hi Guys,
> > any comments on this issue? It seems that partial unique indexes can't
> be used in joins.
> > https://mariadb.atlassian.net/browse/MDEV-5663
>
> Pl
Hi, pslawek83!
On Feb 17, pslawek83 wrote:
> Hi Guys,
> any comments on this issue? It seems that partial unique indexes can't be
> used in joins.
> https://mariadb.atlassian.net/browse/MDEV-5663
Please, show EXPLAIN EXTENDED (and SHOW WARNINGS after it) for this
query of yours.
> * Why the ser
7 matches
Mail list logo
