1. 18 Jun, 2004 1 commit
    • guilhem@mysql.com's avatar
      API change: mysql_shutdown() now requires a 2nd argument, the shutdown level. · 19dbf58e
      guilhem@mysql.com authored
      mysqld >=4.1.3 will however understand shutdown requests sent by clients <4.1.3.
      And mysqld <4.1.3 will understand shutdown requests sent by clients >=4.1.3
      (it will ignore the level). Those shutdown level are just PLACEHOLDERS now.
      So this change is just to make the 4.1 API suitable before it is frozen. Later
      we will actually implement the shutdown levels.
      19dbf58e
  2. 15 Jun, 2004 2 commits
    • guilhem@mysql.com's avatar
      Adding SHUTDOWN_WAIT_STATEMENTS to the possible arguments of mysql_shutdown(). · 25de7219
      guilhem@mysql.com authored
      Comments on names still welcome.
      25de7219
    • guilhem@mysql.com's avatar
      API change: mysql_shutdown() now needs a 2nd parameter, the shutdown level. · f1fda638
      guilhem@mysql.com authored
      Server will however still accept shutdown without specified level; so that old
      mysqladmin can still shut server down.
      I would like your comments on the names of shutdown level which I chose. You
      are welcome to propose better names. Please however check WL#709 before.
      Reason for the names I propose is to be accurate, thus leaving possibility
      for other levels which we may imagine in the future; that's why I have rejected
      names like "fast", "smart", "graceful" so far. My position is that WAIT_ALL_BUFFERS
      or WAIT_CRITICAL_BUFFERS say what the shutdown does, whereas for "smart", "fast" you
      need to remember what it does.
      This should be pushed in 4.1.3 but only after your comments.
      f1fda638
  3. 14 Jun, 2004 2 commits
  4. 12 Jun, 2004 4 commits
  5. 11 Jun, 2004 13 commits
  6. 10 Jun, 2004 18 commits