- developers - lists.mariadb.org

[Maria-developers] Updated (by Psergey): Windows installer for MariaDB (55)
by worklog-noreply＠askmonty.org 15 Oct '09

15 Oct '09

----------------------------------------------------------------------- WORKLOG TASK -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- TASK...........: Windows installer for MariaDB CREATION DATE..: Wed, 14 Oct 2009, 00:07 SUPERVISOR.....: Monty IMPLEMENTOR....: COPIES TO......: CATEGORY.......: Server-RawIdeaBin TASK ID........: 55 (http://askmonty.org/worklog/?tid=55) VERSION........: Server-9.x STATUS.........: Un-Assigned PRIORITY.......: 60 WORKED HOURS...: 0 ESTIMATE.......: 0 (hours remain) ORIG. ESTIMATE.: 0 PROGRESS NOTES: -=-=(Psergey - Thu, 15 Oct 2009, 23:38)=-=- High-Level Specification modified. --- /tmp/wklog.55.old.22618 2009-10-15 23:38:06.000000000 +0300 +++ /tmp/wklog.55.new.22618 2009-10-15 23:38:06.000000000 +0300 @@ -7,8 +7,7 @@ 1.1 Step 1: simple installer ~~~~~~~~~~~~~~~~~~~~~~~~~~~~ An installer package that -- Copies files on installation -- Registers mysqld a service +- Shows GPL Licence - Prompts the user for "essential" configuration options. Preliminary list of "essential" options: * Install directory @@ -22,22 +21,23 @@ 2. ask for things without answers for which the newbies can get into trouble. +- Copies files to destination directory - Checks if the target installation directory, TCP port, or named pipe are busy. If they are, it asks to remove the previous installation first and aborts. (that is: upgrades are not supported in step#1) -- Generates appropriate my.cnf file -- Sets up SQL user with specified password +- Generates appropriate my.cnf file (from a template) +- Sets up SQL root user with specified password - Adds start menu items - to start the server manually (with --console) - to start mysql client - - to edit the my.cnf file. -- Registers MariaDB to start as a service with the specified parameters. -- Registers MariaDB as installed software, sets up uninstaller. + - to edit the my.cnf file +- Registers MariaDB to start as a service with the specified parameters +- Registers MariaDB as installed software, sets up uninstaller (TODO: should the uninstaller the datadir or leave it? (or ask the user?)) - Creates installation log, and in case of any failures presents the log to the user and requests to file it as a bug (How far we should go here depends - on how complex and error-prone the final installation procedure will be). + on how complex and error-prone the installation procedure will end up being). 1.2 Step 2: Upgrades from MySQL or MariaDB ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -=-=(Psergey - Thu, 15 Oct 2009, 16:34)=-=- High-Level Specification modified. --- /tmp/wklog.55.old.3919 2009-10-15 16:34:22.000000000 +0300 +++ /tmp/wklog.55.new.3919 2009-10-15 16:34:22.000000000 +0300 @@ -81,6 +81,6 @@ 3. Other notes -------------- -* MySQL's logo is the seal. It can be found here: +* MariaDB's logo is the seal. It can be found here: http://askmonty.org/wiki/index.php/MariaDB_Logo -=-=(Bothorsen - Thu, 15 Oct 2009, 15:40)=-=- High-Level Specification modified. --- /tmp/wklog.55.old.1396 2009-10-15 15:40:03.000000000 +0300 +++ /tmp/wklog.55.new.1396 2009-10-15 15:40:03.000000000 +0300 @@ -81,6 +81,6 @@ 3. Other notes -------------- -* MySQL's logo is the seal (see e.g. here: https://code.launchpad.net/maria) - Bo Thorsen has the latest revision of the picture in various formats. +* MySQL's logo is the seal. It can be found here: +http://askmonty.org/wiki/index.php/MariaDB_Logo -=-=(Psergey - Thu, 15 Oct 2009, 15:22)=-=- High-Level Specification modified. --- /tmp/wklog.55.old.466 2009-10-15 15:22:05.000000000 +0300 +++ /tmp/wklog.55.new.466 2009-10-15 15:22:05.000000000 +0300 @@ -16,7 +16,7 @@ 14-10-2009 about data directory, Vista and UAC) * root password * default character set - * <TODO come up with the final list. The criteria for inclusion are: + * TODO come up with the final list. The criteria for inclusion are: 1. ask for things that are essential to have a working setup as soon as the installation is complete 2. ask for things without answers for which the newbies can get into @@ -25,11 +25,14 @@ - Checks if the target installation directory, TCP port, or named pipe are busy. If they are, it asks to remove the previous installation first and aborts. (that is: upgrades are not supported in step#1) +- Generates appropriate my.cnf file +- Sets up SQL user with specified password - Adds start menu items - to start the server manually (with --console) - to start mysql client - to edit the my.cnf file. -- Registers MariaDB as installed, sets up uninstaller. +- Registers MariaDB to start as a service with the specified parameters. +- Registers MariaDB as installed software, sets up uninstaller. (TODO: should the uninstaller the datadir or leave it? (or ask the user?)) - Creates installation log, and in case of any failures presents the log to @@ -54,9 +57,10 @@ 1.4 Items not on the wishlist ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -This is a list of things that one might want an installer to do but that are out -of scope of this WL entry. -* Calibration of my.cnf parameters based on available memory, number of CPUs, etc. +This is a list of things that one might want an installer to do but that are +out of scope of this WL entry: +* Calibration of my.cnf parameters based on available memory, number of CPUs, + etc. 2. Installer wishlist (developer POV) -=-=(Psergey - Thu, 15 Oct 2009, 15:17)=-=- High-Level Specification modified. --- /tmp/wklog.55.old.32703 2009-10-15 15:17:17.000000000 +0300 +++ /tmp/wklog.55.new.32703 2009-10-15 15:17:17.000000000 +0300 @@ -24,7 +24,7 @@ - Checks if the target installation directory, TCP port, or named pipe are busy. If they are, it asks to remove the previous installation first - and aborts. + and aborts. (that is: upgrades are not supported in step#1) - Adds start menu items - to start the server manually (with --console) - to start mysql client @@ -36,8 +36,8 @@ the user and requests to file it as a bug (How far we should go here depends on how complex and error-prone the final installation procedure will be). -1.2 Step 2: upgrades from MySQL -~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +1.2 Step 2: Upgrades from MySQL or MariaDB +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ - Same as above but with handling of the case where MySQL has been already installed: - offer to replace MySQL. -=-=(Psergey - Thu, 15 Oct 2009, 15:15)=-=- High-Level Specification modified. --- /tmp/wklog.55.old.32588 2009-10-15 15:15:27.000000000 +0300 +++ /tmp/wklog.55.new.32588 2009-10-15 15:15:27.000000000 +0300 @@ -52,6 +52,13 @@ installer does. TODO come up with options +1.4 Items not on the wishlist +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +This is a list of things that one might want an installer to do but that are out +of scope of this WL entry. +* Calibration of my.cnf parameters based on available memory, number of CPUs, etc. + + 2. Installer wishlist (developer POV) ------------------------------------- * Some "installshield-like" tool that's easy to use (suggestion by Webyog: -=-=(Psergey - Thu, 15 Oct 2009, 13:15)=-=- High-Level Specification modified. --- /tmp/wklog.55.old.27290 2009-10-15 13:15:59.000000000 +0300 +++ /tmp/wklog.55.new.27290 2009-10-15 13:15:59.000000000 +0300 @@ -11,7 +11,9 @@ - Registers mysqld a service - Prompts the user for "essential" configuration options. Preliminary list of "essential" options: - * Destination directory + * Install directory + - Data directory (see email from Peter Laursen on maria-developers@ dated + 14-10-2009 about data directory, Vista and UAC) * root password * default character set * <TODO come up with the final list. The criteria for inclusion are: -=-=(Psergey - Thu, 15 Oct 2009, 00:36)=-=- High-Level Specification modified. --- /tmp/wklog.55.old.27409 2009-10-15 00:36:24.000000000 +0300 +++ /tmp/wklog.55.new.27409 2009-10-15 00:36:24.000000000 +0300 @@ -11,6 +11,7 @@ - Registers mysqld a service - Prompts the user for "essential" configuration options. Preliminary list of "essential" options: + * Destination directory * root password * default character set * <TODO come up with the final list. The criteria for inclusion are: @@ -18,6 +19,7 @@ the installation is complete 2. ask for things without answers for which the newbies can get into trouble. + - Checks if the target installation directory, TCP port, or named pipe are busy. If they are, it asks to remove the previous installation first and aborts. -=-=(Psergey - Thu, 15 Oct 2009, 00:35)=-=- High-Level Specification modified. --- /tmp/wklog.55.old.27287 2009-10-15 00:35:54.000000000 +0300 +++ /tmp/wklog.55.new.27287 2009-10-15 00:35:54.000000000 +0300 @@ -4,15 +4,33 @@ -------------------------------- From the user point of view: -1.1 Step 1: simplest installer -~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +1.1 Step 1: simple installer +~~~~~~~~~~~~~~~~~~~~~~~~~~~~ An installer package that - Copies files on installation - Registers mysqld a service -- Checks if installation directory, MySQL's port, or named pipe are +- Prompts the user for "essential" configuration options. Preliminary list + of "essential" options: + * root password + * default character set + * <TODO come up with the final list. The criteria for inclusion are: + 1. ask for things that are essential to have a working setup as soon as + the installation is complete + 2. ask for things without answers for which the newbies can get into + trouble. +- Checks if the target installation directory, TCP port, or named pipe are busy. If they are, it asks to remove the previous installation first and aborts. -- Uninstall procedure (TODO: should that remove the datadir or leave it?) +- Adds start menu items + - to start the server manually (with --console) + - to start mysql client + - to edit the my.cnf file. +- Registers MariaDB as installed, sets up uninstaller. + (TODO: should the uninstaller the datadir or leave it? (or ask the user?)) + +- Creates installation log, and in case of any failures presents the log to + the user and requests to file it as a bug (How far we should go here depends + on how complex and error-prone the final installation procedure will be). 1.2 Step 2: upgrades from MySQL ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ @@ -28,6 +46,7 @@ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ - Installer should include configuration wizard that's similar to what MySQL installer does. + TODO come up with options 2. Installer wishlist (developer POV) ------------------------------------- @@ -45,3 +64,8 @@ installation succeeded, then start the server, run some commands, then uninstall. Any ways to achieve that?) +3. Other notes +-------------- +* MySQL's logo is the seal (see e.g. here: https://code.launchpad.net/maria) + Bo Thorsen has the latest revision of the picture in various formats. + -=-=(Psergey - Wed, 14 Oct 2009, 00:46)=-=- High-Level Specification modified. --- /tmp/wklog.55.old.29984 2009-10-14 00:46:50.000000000 +0300 +++ /tmp/wklog.55.new.29984 2009-10-14 00:46:50.000000000 +0300 @@ -29,9 +29,6 @@ - Installer should include configuration wizard that's similar to what MySQL installer does. -1.1 Step 1 -~~~~~~~~~~ - 2. Installer wishlist (developer POV) ------------------------------------- * Some "installshield-like" tool that's easy to use (suggestion by Webyog: ------------------------------------------------------------ -=-=(View All Progress Notes, 11 total)=-=- http://askmonty.org/worklog/index.pl?tid=55&nolimit=1 DESCRIPTION: We need Windows Installer package for MariaDB. HIGH-LEVEL SPECIFICATION: Not a spec so far but a list of points to consider: 1. Installer wishlist (user POV) -------------------------------- >From the user point of view: 1.1 Step 1: simple installer ~~~~~~~~~~~~~~~~~~~~~~~~~~~~ An installer package that - Shows GPL Licence - Prompts the user for "essential" configuration options. Preliminary list of "essential" options: * Install directory - Data directory (see email from Peter Laursen on maria-developers@ dated 14-10-2009 about data directory, Vista and UAC) * root password * default character set * TODO come up with the final list. The criteria for inclusion are: 1. ask for things that are essential to have a working setup as soon as the installation is complete 2. ask for things without answers for which the newbies can get into trouble. - Copies files to destination directory - Checks if the target installation directory, TCP port, or named pipe are busy. If they are, it asks to remove the previous installation first and aborts. (that is: upgrades are not supported in step#1) - Generates appropriate my.cnf file (from a template) - Sets up SQL root user with specified password - Adds start menu items - to start the server manually (with --console) - to start mysql client - to edit the my.cnf file - Registers MariaDB to start as a service with the specified parameters - Registers MariaDB as installed software, sets up uninstaller (TODO: should the uninstaller the datadir or leave it? (or ask the user?)) - Creates installation log, and in case of any failures presents the log to the user and requests to file it as a bug (How far we should go here depends on how complex and error-prone the installation procedure will end up being). 1.2 Step 2: Upgrades from MySQL or MariaDB ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ - Same as above but with handling of the case where MySQL has been already installed: - offer to replace MySQL. - upgrade the data directory (todo we should sort out if anything/what is needed for this). - Uninstall MySQL - Install MariaDB. 1.3 Step 3: Configuration wizard ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ - Installer should include configuration wizard that's similar to what MySQL installer does. TODO come up with options 1.4 Items not on the wishlist ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ This is a list of things that one might want an installer to do but that are out of scope of this WL entry: * Calibration of my.cnf parameters based on available memory, number of CPUs, etc. 2. Installer wishlist (developer POV) ------------------------------------- * Some "installshield-like" tool that's easy to use (suggestion by Webyog: NSIS) * Installation procedure source should reside in MariaDB source repository * Installation procedure source file is better to be in human-readable text format. * It should be possible to automate creation of the installer package, in a way that can be run from buildbot (e.g. the installer package build process should print messages to its stdout) * Any suggestions on how can one automatically test the installation package? (for example, we'll want to start the installer, install, check that installation succeeded, then start the server, run some commands, then uninstall. Any ways to achieve that?) 3. Other notes -------------- * MariaDB's logo is the seal. It can be found here: http://askmonty.org/wiki/index.php/MariaDB_Logo ESTIMATED WORK TIME ESTIMATED COMPLETION DATE ----------------------------------------------------------------------- WorkLog (v3.5.9)

1 0

Re: [Maria-developers] Windows installer kick-off
by Steve Obbayi 15 Oct '09

15 Oct '09

----- Original Message ----- From: "Michael Widenius" <monty(a)askmonty.org> To: "Steve Obbayi" <steve(a)sobbayi.com> Cc: maria-developers(a)lists.launchpad.net Sent: Wednesday, October 14, 2009 11:53:43 AM GMT -05:00 US/Canada Eastern Subject: Re: [Maria-developers] Windows installer kick-off Hi! >>>>> "Steve" == Steve Obbayi <steve(a)sobbayi.com> writes: Steve> Hi All, one thing we need to know is that windows users a lot of the times are beginners. Steve> In addition to that the installer needs to be able to: Steve> 1. create the default user Steve> 2. Choose the location of the data files (not just innoDB but for the other storage engines) Steve> 3. Ability to install multiple servers based on port Good suggestions. Steve> 4. Tell the user to reboot the computer after installation. I found sometimes after a fresh install of mysql on windows it doesnt say that but the server behaves erratic until the time one has to restart the computer. It would be very nice to get more information about the above. I have never seen the above problem and don't know of any reason why a reboot would help. Can you explain the 'erratic' behavior ? Regards, Monty Hi Monty, It happens at times when mysql 5.x is installed on windows and the user set up lets say "root" and the wizard finishes. I have encountered several times that the mysql server is inaccessible using the user that was set (in this case "root" )until a reboot is done then everything works fine. I havent encountered this on windows vista its only windows xp. Regards, Steve

3 3

[Maria-developers] Progress (by Sanja): Avoid flushing keycache to disk in case of DROPping DATABASE (56)
by worklog-noreply＠askmonty.org 15 Oct '09

15 Oct '09

----------------------------------------------------------------------- WORKLOG TASK -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- TASK...........: Avoid flushing keycache to disk in case of DROPping DATABASE CREATION DATE..: Thu, 15 Oct 2009, 17:35 SUPERVISOR.....: Monty IMPLEMENTOR....: Sanja COPIES TO......: CATEGORY.......: Server-Sprint TASK ID........: 56 (http://askmonty.org/worklog/?tid=56) VERSION........: Server-5.1 STATUS.........: Code-Review PRIORITY.......: 60 WORKED HOURS...: 3 ESTIMATE.......: 1 (hours remain) ORIG. ESTIMATE.: 3 PROGRESS NOTES: -=-=(Sanja - Thu, 15 Oct 2009, 17:38)=-=- Patch is done and testsed (tested that we do not flush and we mark tables as damaged before deleting them) Worked 3 hours and estimate 1 hour remain (original estimate increased by 1 hour). -=-=(Sanja - Thu, 15 Oct 2009, 17:36)=-=- Low Level Design modified. --- /tmp/wklog.56.old.7415 2009-10-15 17:36:57.000000000 +0300 +++ /tmp/wklog.56.new.7415 2009-10-15 17:36:57.000000000 +0300 @@ -1 +1,2 @@ - +mark tables of the database as deleting when we remove them from table cache +(before removing from keycache). -=-=(Sanja - Thu, 15 Oct 2009, 17:35)=-=- High-Level Specification modified. --- /tmp/wklog.56.old.7269 2009-10-15 17:35:57.000000000 +0300 +++ /tmp/wklog.56.new.7269 2009-10-15 17:35:57.000000000 +0300 @@ -1 +1 @@ - +Mark the tables as deleting, DESCRIPTION: When DROP DATABASE executed keycache of tables of the database flushed to disk before removing table which is wasting of resources. So better to have table removed from keycache without writing changes on disk as it was done for DROP TABLE. HIGH-LEVEL SPECIFICATION: Mark the tables as deleting, LOW-LEVEL DESIGN: mark tables of the database as deleting when we remove them from table cache (before removing from keycache). ESTIMATED WORK TIME ESTIMATED COMPLETION DATE ----------------------------------------------------------------------- WorkLog (v3.5.9)

1 0

[Maria-developers] Progress (by Sanja): Avoid flushing keycache to disk in case of DROPping DATABASE (56)
by worklog-noreply＠askmonty.org 15 Oct '09

15 Oct '09

----------------------------------------------------------------------- WORKLOG TASK -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- TASK...........: Avoid flushing keycache to disk in case of DROPping DATABASE CREATION DATE..: Thu, 15 Oct 2009, 17:35 SUPERVISOR.....: Monty IMPLEMENTOR....: Sanja COPIES TO......: CATEGORY.......: Server-Sprint TASK ID........: 56 (http://askmonty.org/worklog/?tid=56) VERSION........: Server-5.1 STATUS.........: Code-Review PRIORITY.......: 60 WORKED HOURS...: 3 ESTIMATE.......: 1 (hours remain) ORIG. ESTIMATE.: 3 PROGRESS NOTES: -=-=(Sanja - Thu, 15 Oct 2009, 17:38)=-=- Patch is done and testsed (tested that we do not flush and we mark tables as damaged before deleting them) Worked 3 hours and estimate 1 hour remain (original estimate increased by 1 hour). -=-=(Sanja - Thu, 15 Oct 2009, 17:36)=-=- Low Level Design modified. --- /tmp/wklog.56.old.7415 2009-10-15 17:36:57.000000000 +0300 +++ /tmp/wklog.56.new.7415 2009-10-15 17:36:57.000000000 +0300 @@ -1 +1,2 @@ - +mark tables of the database as deleting when we remove them from table cache +(before removing from keycache). -=-=(Sanja - Thu, 15 Oct 2009, 17:35)=-=- High-Level Specification modified. --- /tmp/wklog.56.old.7269 2009-10-15 17:35:57.000000000 +0300 +++ /tmp/wklog.56.new.7269 2009-10-15 17:35:57.000000000 +0300 @@ -1 +1 @@ - +Mark the tables as deleting, DESCRIPTION: When DROP DATABASE executed keycache of tables of the database flushed to disk before removing table which is wasting of resources. So better to have table removed from keycache without writing changes on disk as it was done for DROP TABLE. HIGH-LEVEL SPECIFICATION: Mark the tables as deleting, LOW-LEVEL DESIGN: mark tables of the database as deleting when we remove them from table cache (before removing from keycache). ESTIMATED WORK TIME ESTIMATED COMPLETION DATE ----------------------------------------------------------------------- WorkLog (v3.5.9)

1 0

[Maria-developers] Updated (by Sanja): Avoid flushing keycache to disk in case of DROPping DATABASE (56)
by worklog-noreply＠askmonty.org 15 Oct '09

15 Oct '09

----------------------------------------------------------------------- WORKLOG TASK -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- TASK...........: Avoid flushing keycache to disk in case of DROPping DATABASE CREATION DATE..: Thu, 15 Oct 2009, 17:35 SUPERVISOR.....: Monty IMPLEMENTOR....: Sanja COPIES TO......: CATEGORY.......: Server-Sprint TASK ID........: 56 (http://askmonty.org/worklog/?tid=56) VERSION........: Server-5.1 STATUS.........: Code-Review PRIORITY.......: 60 WORKED HOURS...: 0 ESTIMATE.......: 3 (hours remain) ORIG. ESTIMATE.: 3 PROGRESS NOTES: -=-=(Sanja - Thu, 15 Oct 2009, 17:36)=-=- Low Level Design modified. --- /tmp/wklog.56.old.7415 2009-10-15 17:36:57.000000000 +0300 +++ /tmp/wklog.56.new.7415 2009-10-15 17:36:57.000000000 +0300 @@ -1 +1,2 @@ - +mark tables of the database as deleting when we remove them from table cache +(before removing from keycache). -=-=(Sanja - Thu, 15 Oct 2009, 17:35)=-=- High-Level Specification modified. --- /tmp/wklog.56.old.7269 2009-10-15 17:35:57.000000000 +0300 +++ /tmp/wklog.56.new.7269 2009-10-15 17:35:57.000000000 +0300 @@ -1 +1 @@ - +Mark the tables as deleting, DESCRIPTION: When DROP DATABASE executed keycache of tables of the database flushed to disk before removing table which is wasting of resources. So better to have table removed from keycache without writing changes on disk as it was done for DROP TABLE. HIGH-LEVEL SPECIFICATION: Mark the tables as deleting, LOW-LEVEL DESIGN: mark tables of the database as deleting when we remove them from table cache (before removing from keycache). ESTIMATED WORK TIME ESTIMATED COMPLETION DATE ----------------------------------------------------------------------- WorkLog (v3.5.9)

1 0

[Maria-developers] Updated (by Sanja): Avoid flushing keycache to disk in case of DROPping DATABASE (56)
by worklog-noreply＠askmonty.org 15 Oct '09

15 Oct '09

----------------------------------------------------------------------- WORKLOG TASK -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- TASK...........: Avoid flushing keycache to disk in case of DROPping DATABASE CREATION DATE..: Thu, 15 Oct 2009, 17:35 SUPERVISOR.....: Monty IMPLEMENTOR....: Sanja COPIES TO......: CATEGORY.......: Server-Sprint TASK ID........: 56 (http://askmonty.org/worklog/?tid=56) VERSION........: Server-5.1 STATUS.........: Code-Review PRIORITY.......: 60 WORKED HOURS...: 0 ESTIMATE.......: 3 (hours remain) ORIG. ESTIMATE.: 3 PROGRESS NOTES: -=-=(Sanja - Thu, 15 Oct 2009, 17:36)=-=- Low Level Design modified. --- /tmp/wklog.56.old.7415 2009-10-15 17:36:57.000000000 +0300 +++ /tmp/wklog.56.new.7415 2009-10-15 17:36:57.000000000 +0300 @@ -1 +1,2 @@ - +mark tables of the database as deleting when we remove them from table cache +(before removing from keycache). -=-=(Sanja - Thu, 15 Oct 2009, 17:35)=-=- High-Level Specification modified. --- /tmp/wklog.56.old.7269 2009-10-15 17:35:57.000000000 +0300 +++ /tmp/wklog.56.new.7269 2009-10-15 17:35:57.000000000 +0300 @@ -1 +1 @@ - +Mark the tables as deleting, DESCRIPTION: When DROP DATABASE executed keycache of tables of the database flushed to disk before removing table which is wasting of resources. So better to have table removed from keycache without writing changes on disk as it was done for DROP TABLE. HIGH-LEVEL SPECIFICATION: Mark the tables as deleting, LOW-LEVEL DESIGN: mark tables of the database as deleting when we remove them from table cache (before removing from keycache). ESTIMATED WORK TIME ESTIMATED COMPLETION DATE ----------------------------------------------------------------------- WorkLog (v3.5.9)

1 0

[Maria-developers] Updated (by Sanja): Avoid flushing keycache to disk in case of DROPping DATABASE (56)
by worklog-noreply＠askmonty.org 15 Oct '09

15 Oct '09

----------------------------------------------------------------------- WORKLOG TASK -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- TASK...........: Avoid flushing keycache to disk in case of DROPping DATABASE CREATION DATE..: Thu, 15 Oct 2009, 17:35 SUPERVISOR.....: Monty IMPLEMENTOR....: Sanja COPIES TO......: CATEGORY.......: Server-Sprint TASK ID........: 56 (http://askmonty.org/worklog/?tid=56) VERSION........: Server-5.1 STATUS.........: Code-Review PRIORITY.......: 60 WORKED HOURS...: 0 ESTIMATE.......: 3 (hours remain) ORIG. ESTIMATE.: 3 PROGRESS NOTES: -=-=(Sanja - Thu, 15 Oct 2009, 17:35)=-=- High-Level Specification modified. --- /tmp/wklog.56.old.7269 2009-10-15 17:35:57.000000000 +0300 +++ /tmp/wklog.56.new.7269 2009-10-15 17:35:57.000000000 +0300 @@ -1 +1 @@ - +Mark the tables as deleting, DESCRIPTION: When DROP DATABASE executed keycache of tables of the database flushed to disk before removing table which is wasting of resources. So better to have table removed from keycache without writing changes on disk as it was done for DROP TABLE. HIGH-LEVEL SPECIFICATION: Mark the tables as deleting, ESTIMATED WORK TIME ESTIMATED COMPLETION DATE ----------------------------------------------------------------------- WorkLog (v3.5.9)

1 0

[Maria-developers] Updated (by Sanja): Avoid flushing keycache to disk in case of DROPping DATABASE (56)
by worklog-noreply＠askmonty.org 15 Oct '09

15 Oct '09

----------------------------------------------------------------------- WORKLOG TASK -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- TASK...........: Avoid flushing keycache to disk in case of DROPping DATABASE CREATION DATE..: Thu, 15 Oct 2009, 17:35 SUPERVISOR.....: Monty IMPLEMENTOR....: Sanja COPIES TO......: CATEGORY.......: Server-Sprint TASK ID........: 56 (http://askmonty.org/worklog/?tid=56) VERSION........: Server-5.1 STATUS.........: Code-Review PRIORITY.......: 60 WORKED HOURS...: 0 ESTIMATE.......: 3 (hours remain) ORIG. ESTIMATE.: 3 PROGRESS NOTES: -=-=(Sanja - Thu, 15 Oct 2009, 17:35)=-=- High-Level Specification modified. --- /tmp/wklog.56.old.7269 2009-10-15 17:35:57.000000000 +0300 +++ /tmp/wklog.56.new.7269 2009-10-15 17:35:57.000000000 +0300 @@ -1 +1 @@ - +Mark the tables as deleting, DESCRIPTION: When DROP DATABASE executed keycache of tables of the database flushed to disk before removing table which is wasting of resources. So better to have table removed from keycache without writing changes on disk as it was done for DROP TABLE. HIGH-LEVEL SPECIFICATION: Mark the tables as deleting, ESTIMATED WORK TIME ESTIMATED COMPLETION DATE ----------------------------------------------------------------------- WorkLog (v3.5.9)

1 0

[Maria-developers] New (by Sanja): Avoid flushing keycache to disk in case of DROPping DATABASE (56)
by worklog-noreply＠askmonty.org 15 Oct '09

15 Oct '09

----------------------------------------------------------------------- WORKLOG TASK -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- TASK...........: Avoid flushing keycache to disk in case of DROPping DATABASE CREATION DATE..: Thu, 15 Oct 2009, 17:35 SUPERVISOR.....: Monty IMPLEMENTOR....: Sanja COPIES TO......: CATEGORY.......: Server-Sprint TASK ID........: 56 (http://askmonty.org/worklog/?tid=56) VERSION........: Server-5.1 STATUS.........: Code-Review PRIORITY.......: 60 WORKED HOURS...: 0 ESTIMATE.......: 3 (hours remain) ORIG. ESTIMATE.: 3 PROGRESS NOTES: DESCRIPTION: When DROP DATABASE executed keycache of tables of the database flushed to disk before removing table which is wasting of resources. So better to have table removed from keycache without writing changes on disk as it was done for DROP TABLE. ESTIMATED WORK TIME ESTIMATED COMPLETION DATE ----------------------------------------------------------------------- WorkLog (v3.5.9)

1 0

[Maria-developers] New (by Sanja): Avoid flushing keycache to disk in case of DROPping DATABASE (56)
by worklog-noreply＠askmonty.org 15 Oct '09

15 Oct '09

----------------------------------------------------------------------- WORKLOG TASK -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- TASK...........: Avoid flushing keycache to disk in case of DROPping DATABASE CREATION DATE..: Thu, 15 Oct 2009, 17:35 SUPERVISOR.....: Monty IMPLEMENTOR....: Sanja COPIES TO......: CATEGORY.......: Server-Sprint TASK ID........: 56 (http://askmonty.org/worklog/?tid=56) VERSION........: Server-5.1 STATUS.........: Code-Review PRIORITY.......: 60 WORKED HOURS...: 0 ESTIMATE.......: 3 (hours remain) ORIG. ESTIMATE.: 3 PROGRESS NOTES: DESCRIPTION: When DROP DATABASE executed keycache of tables of the database flushed to disk before removing table which is wasting of resources. So better to have table removed from keycache without writing changes on disk as it was done for DROP TABLE. ESTIMATED WORK TIME ESTIMATED COMPLETION DATE ----------------------------------------------------------------------- WorkLog (v3.5.9)

1 0