| bio | website | |
|---|---|---|
| location | Montreal, Canada | |
| age | 42 | |
| visits | member for | 1 year, 6 months |
| seen | May 7 at 17:48 | |
| stats | profile views | 8 |
|
Dec 13 |
awarded | Teacher |
|
Dec 13 |
answered | MariaDB allowing select only user to create databases |
|
Dec 13 |
comment |
MariaDB allowing select only user to create databases Yup. I was creating databases starting with test_. |
|
Dec 13 |
asked | MariaDB allowing select only user to create databases |
|
Dec 13 |
comment |
mariadb ignoring force index The ix_name will be, but not the bigtable.ix_smalltable_id. I have a few case where 25 entries were created in smalltable with identical name, and if you use those, you end up with full table scan. Writing a deduplicating job now. |
|
Dec 13 |
comment |
mariadb ignoring force index I just noticed that since ix_name is not unique, the index will only be used when there is only one row in smalltable. |
|
Dec 12 |
comment |
mariadb ignoring force index Thanks, this took care of it. |
|
Dec 12 |
accepted | mariadb ignoring force index |
|
Dec 12 |
comment |
mariadb ignoring force index already an index on smalltable_id, it's the primary key |
|
Dec 12 |
revised |
mariadb ignoring force index Added table structure |
|
Dec 12 |
asked | mariadb ignoring force index |
|
May 17 |
awarded | Commentator |
|
May 17 |
comment |
why is mysql still writing data two hours after all transactions have stopped So is there a way to tell how much data is left to be flushed from the double buffer to the main data files? |
|
May 17 |
comment |
why is mysql still writing data two hours after all transactions have stopped Is it possible that double write catchup is causing this? It looks like around 75 pages/second are double written (according to innodb_dblwr_pages_written). |
|
May 17 |
comment |
why is mysql still writing data two hours after all transactions have stopped The data is not being modified, with MVCC you don't increase the timestamp of a row when reading, just when writing. And this system is 90% inserts, 10% updates, so there can't be that much MVCC cleanup. |
|
May 17 |
comment |
why is mysql still writing data two hours after all transactions have stopped 32GB for the server, mysql is using about 22GB. |
|
May 17 |
comment |
why is mysql still writing data two hours after all transactions have stopped But why does purging result in writing if the pages are not dirty? There is no inserts/updates/deletes happening right now on that server. |
|
May 17 |
comment |
why is mysql still writing data two hours after all transactions have stopped It's currently at 57 and stable. |
|
May 17 |
asked | why is mysql still writing data two hours after all transactions have stopped |
|
May 14 |
awarded | Scholar |