1. 11 Jun, 2020 1 commit
  2. 29 Apr, 2020 1 commit
    • Jérome Perrin's avatar
      component/mariadb: install in shared mode · d29fba55
      Jérome Perrin authored
      Mariadb was not shared, because installing mroonga writes a plugin in
      mariadb's plugin dir and it's not allowed for one part to write in
      another part's folder.
      
      The approach is to install mroonga plugin in it's own plugin directory,
      then copy all mariadb default plugins in this plugin directory and
      configure instance to use mroonga's plugin directory.
      
      Groonga also has plugins and we are using groonga-normalizer-mysql
      plugin. Fortunately, groonga reads plugins located in paths listed in
      GRN_PLUGINS_PATH environment variable, so we can use a simpler approach
      of installing plugins in their own installation folder and set
      GRN_PLUGINS_PATH in the environment of processes using groonga, ie. the
      mariadb server process.
      d29fba55
  3. 02 Oct, 2019 1 commit
    • Jérome Perrin's avatar
      erp5: set mariadb timezone to UTC · 0b377eb4
      Jérome Perrin authored
      ERP5Catalog assumes that dates in catalog are UTC, this works
      fine with DATETIME columns that does not carry any timezone
      information, but TIMESTAMP columns are converted to mariadb timezone,
      which is by default system timezone.
      
      If we want ERP5Catalog to query on TIMESTAMP columns with the existing
      logic of converting dates to UTC (because "dates are in UTC in
      catalog"), we need to have TIMESTAMP columns in UTC.
      
      This also generally seem a better default than falling back to system
      timezone.
      
      /reviewed-on nexedi/slapos!623
      0b377eb4
  4. 26 Jul, 2019 1 commit
  5. 23 Jul, 2019 2 commits
  6. 04 Jun, 2019 1 commit
  7. 07 Sep, 2018 1 commit
  8. 08 Feb, 2017 1 commit
  9. 10 Aug, 2016 1 commit
  10. 20 May, 2016 1 commit
  11. 17 Dec, 2015 1 commit
  12. 23 Apr, 2014 1 commit
    • Vincent Pelletier's avatar
      erp5.mariadb: Explicitly disable innodb_file_per_table . · e5325b93
      Vincent Pelletier authored
      MySQL changed the default value 3 times since 5.1, causing a waste of disk
      space when recreating schemas (tables move out of an already large system
      tablespace, which cannot be easily reclaimed).
      Also, per-table option fragments free space: if a table shrinks, freed
      space cannot be used by another table without recreating shrunk table
      (which induces at least a write-lock during data copy, which may not be
      trivial).
      e5325b93
  13. 05 Apr, 2014 1 commit
  14. 20 Mar, 2014 1 commit
  15. 05 Feb, 2014 1 commit
  16. 04 Sep, 2013 1 commit
  17. 08 Aug, 2013 2 commits
  18. 16 Jul, 2013 3 commits