Re: [Maria-developers] Windows installer MWL#55 finished.
@wlad I came across an issue with the .msi from Oracle. refer: http://bugs.mysql.com/bug.php?id=60830 In short: if somebody installs a 'n-bit' version and on top of this a 'm-bit' version various inconsistencies happen inside Windows system menus. I concluded that 1) either: a n-bit of a x.y version should refuse to install if a m-bit of same x.y version is installed 2) or: n-bit and m-bit should should identify themselves so that Windows can handle them in parallel. (not only 'MySQL Server 5.5 but MySQL Server 5.5 - 64 bit etc.) Is this something you have been considering? -- Peter On Tue, Mar 8, 2011 at 20:23, Vladislav Vaintroub w...@montyprogram.comwrote: *From:* Peter Laursen [mailto:peter_laur...@webyog.com] *Sent:* Mittwoch, 2. März 2011 11:30 *To:* Vladislav Vaintroub *Cc:* Kazuhisa Ichikawa; maria-developers@lists.launchpad.net *Subject:* Re: [Maria-developers] Windows installer MWL#55 finished. It seems that http://downloads.askmonty.org/mariadb/ still has the old NSIS-based installer for 5.1.55? – Peter Yes, 5.1 will have the old installer until the end of 5.1’s life. Also, in 5.2/5.3 the new installer is not pushed yet, because it is not yet reviewed. On Tue, Feb 8, 2011 at 00:46, Vladislav Vaintroub w...@montyprogram.com wrote: ___ Mailing list: https://launchpad.net/~maria-developers Post to : maria-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~maria-developers More help : https://help.launchpad.net/ListHelp
Re: [Maria-developers] Windows installer MWL#55 finished.
From: Peter Laursen [mailto:peter_laur...@webyog.com] Sent: Mittwoch, 13. April 2011 00:52 To: Vladislav Vaintroub Cc: Kazuhisa Ichikawa; maria-developers@lists.launchpad.net Subject: Re: [Maria-developers] Windows installer MWL#55 finished. Hi Peter, @wlad I came across an issue with the .msi from Oracle. refer: http://bugs.mysql.com/bug.php?id=60830 In short: if somebody installs a 'n-bit' version and on top of this a 'm-bit' version various inconsistencies happen inside Windows system menus. I concluded that 1) either: a n-bit of a x.y version should refuse to install if a m-bit of same x.y version is installed 2) or: n-bit and m-bit should should identify themselves so that Windows can handle them in parallel. (not only 'MySQL Server 5.5 but MySQL Server 5.5 - 64 bit etc.) Is this something you have been considering? We are be doing 2) – installing 32 and 64 bit side-by-side, 64 bit package identifies itself with “x64” suffix -- Peter On Tue, Mar 8, 2011 at 20:23, Vladislav Vaintroub w...@montyprogram.com wrote: From: Peter Laursen [mailto:peter_laur...@webyog.com] Sent: Mittwoch, 2. März 2011 11:30 To: Vladislav Vaintroub Cc: Kazuhisa Ichikawa; maria-developers@lists.launchpad.net Subject: Re: [Maria-developers] Windows installer MWL#55 finished. It seems that http://downloads.askmonty.org/mariadb/ http://downloads.askmonty.org/mariadb/ still has the old NSIS-based installer for 5.1.55? – Peter Yes, 5.1 will have the old installer until the end of 5.1’s life. Also, in 5.2/5.3 the new installer is not pushed yet, because it is not yet reviewed. On Tue, Feb 8, 2011 at 00:46, Vladislav Vaintroub mailto:w...@montyprogram.com w...@montyprogram.com wrote: ___ Mailing list: https://launchpad.net/~maria-developers Post to : maria-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~maria-developers More help : https://help.launchpad.net/ListHelp
[Maria-developers] WL#197 New (by Mdcallag): table lock wait timeouts
--- WORKLOG TASK -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- TASK...: table lock wait timeouts CREATION DATE..: Wed, 13 Apr 2011, 17:09 SUPERVISOR.: IMPLEMENTOR: COPIES TO..: CATEGORY...: Server-RawIdeaBin TASK ID: 197 (http://askmonty.org/worklog/?tid=197) VERSION: WorkLog-4.0 STATUS.: Un-Assigned PRIORITY...: 60 WORKED HOURS...: 0 ESTIMATE...: 0 (hours remain) ORIG. ESTIMATE.: 0 PROGRESS NOTES: DESCRIPTION: MySQL has table_lock_wait_timeout but that doesn't do anything. For some apps it would help to timeout sessions blocked on a table lock. For example, when ALTER TABLE runs it implicitly gets an X lock on the table cache entry. Queries that follow are blocked until it finishes. The client-side read timeout might expire and disconnect the client but the server-side thread will continue blocking and the server can fill with blocked sessions. Right now the stack when the client blocks is open_tables - open_table - wait_for_condition. I implemented a demo for this by: 1) use pthread_cond_timedwait in wait_for_condition 2) check for timeout expiration in open_tables and error out Without the change in 2) the session will loop within open_tables on calls to open_table. ESTIMATED WORK TIME ESTIMATED COMPLETION DATE --- WorkLog (v4.0.0) ___ Mailing list: https://launchpad.net/~maria-developers Post to : maria-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~maria-developers More help : https://help.launchpad.net/ListHelp