text:
|General Discussion
|« Previous MessageNext Message »
|Bjorn Munch
|September 21 2013 4:10pm
|MySQL Community Server 5.7.2 has been released (part 3 of 4)
|View as plain text
* InnoDB: During a transaction commit, prepare_commit_mutex is acquired to preserve the commit order. If the commit operation failed, the transaction would be rolled back but the mutex would not be released. Subsequent insert operations would not be able to acquire the same mutex. This fix frees prepare_commit_mutex during innobase_rollback. (Bug #16513588) * InnoDB: The row0purge.h include file contained a self-referencing inclusion. (Bug #16521741) * InnoDB: The InnoDB memcached test.demo_test table would fail to work when defined as a utf8 charset table. (Bug #16499038) * InnoDB: This fix replaces the IB_ULONGLONG_MAX constant with LSN_MAX where the code refers to log sequence numbers, or with TRX_ID_MAX where trx->no is initialized to an undefined value. This change does not alter the value of the constant. (Bug #16458660) * InnoDB: This fix corrects the text for InnoDB error 6025, which stated, "InnoDB: read can't be opened in ./ib_logfile0 mode.". The corrected message states, "InnoDB: ./ib_logfile0 can't be opened in read mode." The variable and mode in the message construct were transposed. (Bug #16434398) * InnoDB: The page_zip_available function would count some fields twice. (Bug #16463505) * InnoDB: This fix removes most calls to OS_THREAD_SLEEP from InnoDB. (Bug #16472953, Bug #68588) * InnoDB: Concurrently inserting into a full-text table would cause some inserts to fail. Duplicate values would be generated for full-text search document IDs when performing inserts into a hidden full-text search document ID column. (Bug #16469399) * InnoDB: FLUSH TABLES FOR EXPORT would sleep too often while flushing pages from buffer pools. (Bug #16471701) * InnoDB: In cases where threads are forced to do single page flushing, fsync() would be triggered for all data files. This fix allows for synchronous single page flushing. (Bug #16477781) * InnoDB: When changing the shared tablespace file name using innodb_data_file_path and leaving the current log files in place, InnoDB would create a new tablespace file and overwrite the log files resulting in a mismatch between the data dictionary and tables on disk. This bug fix ensures that InnoDB does not create a new tablespace if there are inconsistent system tablespaces, undo tablespaces, or redo log files. (Bug #16418661) * InnoDB: An InnoDB memcached file descriptor leak would cause a serious error. (Bug #16466664) * InnoDB: In debug builds, an insert would fail with an invalid assertion: sync_thread_levels_g(array, level - 1, TRUE). (Bug #16409715) * InnoDB: Multiple concurrent calls to dict_update_statistics() would result in unnecessary server load. (Bug #16400412) * InnoDB: On 64-bit Windows builds, INNODB_BUFFER_POOL_SIZE would not accept an allocation of more than 32GB. This limitation was due to a bug that truncated the internal value for the InnoDB buffer pool size to 32 bits on 64-bit Windows builds. (Bug #16391722, Bug #68470) * InnoDB: An ALTER TABLE operation that performed a table copy failed because a temporary tablespace with the same name already existed. This fix makes temporary tables and tablespace names more unique by adding the current log sequence number (LSN) to the end of the previous table or file name. For example, table name "test/#sql-ib21" becomes "test/#sql-ib21-1701208," where 1701208 is the current LSN. Both the LSN and the table ID are needed to ensure that the name is unique because it is theoretically possible for multiple threads to have the same LSN. Including the table ID allows the temporary name to be associated with the table. (Bug #16403420) * InnoDB: Crash recovery would fail with a !recv_no_log_write assertion when reading a page. (Bug #16405422) * InnoDB: Restarting InnoDB in read-only mode and running a workload would occasionally return a global_segment < os_aio_n_segments assertion. (Bug #16362046) * InnoDB: When the InnoDB shutdown mode (innodb_fast_shutdown) is set to 2 and the master thread enters the flush loop, the thread would not be able to exit under some circumstances. This could lead to a shutdown hang. (Bug #16411457) * InnoDB: Creating a foreign key constraint using the ALTER TABLE INPLACE algorithm requires foreign_key_checks to be set to 0 (SET foreign_key_checks = 0;). As a result, an appropriate duplicate ID check would not be performed. (Bug #16413976) * InnoDB: This fix removes dated and incomplete code that is protected by the UNIV_LOG_ARCHIVE macro. (Bug #16296837) * InnoDB: RENAME TABLE would result in a hang due to a MySQL mutex acquisition deadlock. (Bug #16305265) * InnoDB: DROP DATABASE failed if the database contained an InnoDB table that had a data file in an external data directory. The external data file had an "InnoDB Symbolic Link" file type (.isl) that was not recognized by MySQL. This fix adds .isl as a known InnoDB file type. (Bug #16338667) * InnoDB: When tables are linked by foreign key constraints, loading one table would open other linked tables recursively. When numerous tables are linked by foreign key constraints, this would sometimes lead to a thread stack overflow causing the server to exit. Tables linked by foreign key constraints are now loaded iteratively. Cascade operations, which were also performed in a recursive manner, are now performed iteratively using an explicit stack. (Bug #16244691, Bug #65384) * InnoDB: Under testing, a FLUSH TABLE operation resulted in a timeout due to a missing acknowledgement that the purge thread had stopped. (Bug #16277387) * InnoDB: For a compressed table, the "page reorganize" function would ignore the innodb_log_compressed_pages option and always log the entire compressed page, which increased the size of the redo log. The "page reorganize" function now adheres to the innodb_log_compressed_pages option and does not log compressed page images to the redo log when innodb_log_compressed_pages is set to "OFF". (Bug #16267120) * InnoDB: After disabling foreign key checks with SET foreign_key_checks=0 and performing a DROP INDEX, the table was no longer accessible after restarting the server. This fix allows the table with missing foreign key indexes to be accessed when SET foreign_key_checks=0. When the table is accessible, the user must recreate the missing indexes to fulfill the foreign key constraints. (Bug #16208542, Bug #68148) * InnoDB: When a transaction is in READ COMMITTED isolation level, gap locks are still taken in the secondary index when a row is inserted. This occurs when the secondary index is scanned for duplicates. The function row_ins_scan_sec_index_for_duplicate() always calls the function row_ins_set_shared_rec_lock() with LOCK_ORDINARY irrespective of the transaction isolation level. This fix modifies the row_ins_scan_sec_index_for_duplicate() function to call row_ins_set_shared_rec_lock() with LOCK_ORDINARY or LOCK_REC_NOT_GAP, based on the transaction isolation level. (Bug #16133801, Bug #68021) * InnoDB: Starting mysqld with --innodb_log_buffer_size=50GB failed to allocate memory and returned NULL. For non-debug builds there was no check in place and a segmentation fault occurred. This fix adds a log message stating that memory failed to be allocated, and adds an assertion. (Bug #16069598, Bug #68025) * InnoDB: When UNIV_DEBUG is enabled in debug builds, buf_validate() is often called which sometimes results in false alarms in tests on semaphore wait timeout. This fix increases counter values to reduce false alarms. (Bug #16068056) * InnoDB: While processing read-write workloads, InnoDB would scan more pages than are required for flushing, unnecessarily consuming CPU resource. (Bug #16037180) * InnoDB: The explain_filename function, which provides information about a partition by parsing the file name, would return an error when attempting to parse a file name with no partition information. (Bug #16051728) * InnoDB: Stopping the server, removing a database table (d1.t1) .frm file from the data directory, restarting the server, and dropping the database (d1), would cause an assertion. (Bug #16043216) * InnoDB: While printing a UTF-8 table name, InnoDB would truncate the table name, resulting in an incomplete buffer and subsequent Valgrind error. This bug fix also addresses an incorrect debugging error message. (Bug #16066351) * InnoDB: TRUNCATE TABLE would fail to handle the return value from btr_create when btr_create is invoked by TRUNCATE TABLE for creation of a new index. (Bug #16026889) * InnoDB: Persistent stats would be disabled unnecessarily when running in read-only mode. When running in read-only mode, fetching stats from disk does not involve any modification of on-disk data except for when ANALYZE TABLE is run. This fix enables persistent stats for read-only mode. (Bug #16083211) * InnoDB: An overflow would occur for innodb_row_lock_time_max and innodb_row_lock_current_waits. This fix modifies code logic in storage/innobase/srv/srv0srv.c. (Bug #16005310) * InnoDB: Attempting to create a table while in innodb_read_only mode would result in the following error: ERROR 1015 (HY000): Can't lock file (errno: 165 - Table is read only). (Bug #15963619) * InnoDB: An active FLUSH TABLE FOR EXPORT thread would cause a hang during shutdown. The fix ensures that trx_is_interrupted() is checked during ibuf_merge. (Bug #15953255) * InnoDB: innochecksum would return an error when run on compressed tables. (Bug #14612872, Bug #66779) * InnoDB: A multi-row INSERT ... ON DUPLICATE KEY UPDATE insert failure, caused by a duplicate key error, would result in duplicate auto-increment values. (Bug #14483484, Bug #66301) * InnoDB: A mismatch between .ibd files and the InnoDB data dictionary could occur if TRUNCATE TABLE is interrupted by a crash. The mismatch would be encountered after recovery. To avoid this problem, truncate table information is written to a truncate log file that resides temporarily in the log directory. The truncate log file has the following naming convention: ib_space_id_trunc.log. If the truncate TRUNCATE operation is successful, the truncate log file is removed. If the TRUNCATE operation is interrupted by a crash, information is read from the truncate log file during recovery, the log records are applied, and the truncate log file is removed. (Bug #14174004, Bug #13997329, Bug #17227149, Bug #17238361) * InnoDB: The documentation incorrectly stated that START TRANSACTION WITH CONSISTENT SNAPSHOT provides a consistent snapshot only if the current isolation level is REPEATABLE READ or SERIALIZABLE. START TRANSACTION WITH CONSISTENT SNAPSHOT only works with REPEATABLE READ. All other isolation levels are ignored. The documentation has been revised and a warning is now generated whenever the WITH CONSISTENT SNAPSHOT clause is ignored. (Bug #14017206, Bug #65146) * InnoDB: The srv_master_thread background thread, which monitors server activity and performs activities such as page flushing when the server is inactive or in a shutdown state, runs on a one second delay loop. srv_master_thread would fail to check if the server is in a shutdown state before sleeping. (Bug #13417564, Bug #63276) * InnoDB: In the error log, a full-text search index would be reported missing from the data dictionary during a TRUNCATE TABLE operation. After restarting mysqld, the following InnoDB error would be reported: "InnoDB: Error: trying to load index idx13 for table test/g1 but the index tree has been freed.." (Bug #12429565) * InnoDB: Compiling InnoDB on Windows Vista 64-bit with VS2005 would result in compilation errors. (Bug #11752731, Bug #44004) * InnoDB: When the value provided for innodb_buffer_pool_size on 32-bit systems is too large, an error message would incorrectly reference the internal variable, innobase_buffer_pool_size, instead of innodb_buffer_pool_size. (Bug #11759578, Bug #51901) * InnoDB: In many cases InnoDB calls exit(1) when it encounters a fatal error. An exit(1) call does not produce a crash dump or provide information about the process state. Additionally, on Windows, an exit(1) call does not report a crashed process in the Event Viewer. This fix replaces exit(1) calls with ut_error calls in a number of places. (Bug #56400, Bug #11763660) * InnoDB: Creating a table with a comment or default textual value containing an apostrophe that is escaped with a backslash would sometimes cause the InnoDB storage engine to omit foreign key definitions. (Bug #61656, Bug #12762377) * InnoDB: Setting foreign_key_checks=0 and running ALTER TABLE to change the character set of foreign key columns for a database with multiple tables with foreign key constraints would leave the database in an inconsistent state. Subsequent ALTER TABLE operations (using the COPY algorithm) with foreign_key_checks=1 would fail due to the detected inconsistency. Reversion of the partially executed ALTER TABLE operation would also fail, resulting in the loss of the table being altered. When running the same ALTER TABLE operation with a RENAME clause, the inconsistency would not be detected but if the ALTER TABLE operation failed for some other reason, reversion of the partially executed ALTER TABLE would fail with the same result. The bug fix temporarily disables foreign_key_checks while the previous table definition is restored. (Bug #65701, Bug #14227431) * InnoDB: Successive deletes in descending key order would lead to under-filled InnoDB index pages. When an InnoDB index page is under-filled, it is merged with the left or right sibling node. The check performed to determine if a sibling node is available for merging was not functioning correctly. (Bug #68501, Bug #16417635) * InnoDB: The pthread_mutex, commit_threads_m, which was initialized but never used, has been removed from the code base. (Bug #60225, Bug #11829813) * InnoDB: When running an InnoDB full-text search in boolean mode, prefixing an asterisk (*) to a search string ('*string') would result in an error whereas for MyISAM, a prefixed asterisk would be ignored. To ensure compatibility between InnoDB and MyISAM, InnoDB now handles a prefixed asterisk in the same way as MyISAM. (Bug #68948, Bug #16660607) * InnoDB: The row_check_index_for_mysql method, which checks for NULL fields during an index scan or CHECK TABLE operation, would iterate unnecessarily. Thanks to Po-Chun Chang for the patch to correct this issue. (Bug #69377, Bug #16896647) * Partitioning: When upgrading to MySQL 5.5.31 or higher, a message is written into the output of mysql_upgrade when encountering a partitioned table for which the ALGORITHM option is required to maintain binary compatibility with the original; the message includes the ALTER TABLE statement required to make the change. For such a table having a sufficiently large number of partitions, the message was truncated with an error before the complete ALTER TABLE statement could be written. (Bug #16589511) * Partitioning: When a range specified in the WHERE condition of a query against a table partitioned by RANGE entirely within that of one of the partitions, the next partition was also checked for rows although it should have been pruned away. Suppose we have a range-partitioned table t created using the following SQL statement: CREATE TABLE t ( id INT AUTO_INCREMENT, dt DATETIME, PRIMARY KEY (dt,id), UNIQUE KEY (id,dt) ) PARTITION BY RANGE COLUMNS(dt) ( PARTITION p0 VALUES LESS THAN ('2013-01-01'), PARTITION p1 VALUES LESS THAN ('2013-01-15'), PARTITION p2 VALUES LESS THAN ('2013-02-01'), PARTITION p3 VALUES LESS THAN ('2013-02-15'), PARTITION pmax VALUES LESS THAN (MAXVALUE) ); An example of a query that exhibited this issue when run against t is shown here: SELECT COUNT(*) FROM t WHERE dt >= '2013-02-01' AND dt < '2013-02-15'; In this case, partition pmax was checked, even though the range given in the WHERE clause lay entirely within partition p3. (Bug #16447483) * Partitioning: When dropping a partitioned table, the table's .par file was deleted first, before the table definition or data. This meant that, if the server failed during the drop operation, the table could be left in an inconsistent state in which it could neither be accessed nor dropped. The fix for this problem makes the following changes: + Now, when dropping a partitioned table, the table's .par file is not removed until all table data has been deleted. + When executing DROP TABLE of a partitioned table, in the event that its .par file is determined to be missing, the table's .frm file is now immediately deleted, in effect forcing the drop to complete. (Bug #13548704, Bug #63884) * Replication: The data size for a table map event created during execution was calculated, but not when the event was created from a network packet. This could later cause problems when the data fields of such events were treated as if they had a length equal to 0 when trying to write the events to a cache, or to the binary log. To avoid future problems of this nature, the table map's data size is now calculated in both cases. (Bug #17164074) * Replication: When the --relay-log-info-file option was used together with --slave-parallel-workers set to a value greater than 1, mysqld failed to start. (Bug #17160671) * Replication: The mysqlbinlog option --rewrite-db caused USE statements to be ignored, even for databases that were not referenced by the option. (Bug #16914535) * Replication: The condition leading to the issue fixed in Bug #16579083 continued to raise an error even though the condition itself no longer cause the issue to occur. (Bug #16931177, Bug #69369) References: See also Bug #16271657, Bug #16491597, Bug #68251, Bug #68569. * Replication: When rpl_semi_sync_master_timeout was set to an extremely large value, semi-synchronous replication became very slow, especially when many sessions were working in parallel. It was discovered that the code to calculate this timeout was inside the wait loop itself, with the result that an increase in the value of rpl_semi_sync_master_timeout caused repeated iterations. This fix improves the method used to calculate wakeup times, and moves it outside of the wait loop, so that it is executed one time only. (Bug #16878043, Bug #69341) * Replication: It was possible to cause a deadlock after issuing FLUSH TABLES WITH READ LOCK by issuing STOP SLAVE in a new connection to the slave, then issuing SHOW SLAVE STATUS using the original connection. The fix for this includes the addition of the rpl_stop_slave_timeout system variable, to control the time in seconds to wait for slave to stop after issuing STOP SLAVE before returning a warning. (Bug #16856735) * Replication: Some expressions employing variables were not handled correctly by LOAD DATA. (Bug #16753869) * Replication: In some circumstances, the message in the Last_Error column from the output of SHOW SLAVE STATUS referred to GTID_NEXT_LIST although this variable is not currently implemented (the name is reserved for possible future use). Now in such cases the error message no longer refers to this variable. (Bug #16742886, Bug #69096) References: See also Bug #16715809, Bug #69045. * Replication: Point-in-time recovery could fail when trying to restore a single database from a binary log in row-based format using mysqlbinlog with the --database option. (Bug #16698172) * Replication: mysqlbinlog --rewrite-db failed when the name of the destination database contained any underscore (_) characters. (Bug #16737279) * Replication: Issuing a FLUSH TABLES statement on a GTID-enabled master caused replication to fail. It was found that this misbehavior was introduced by the fix for Bug #16062608, which disallowed statements that perform an implicit commit but whose changes are not logged when gtid_next is set to any value other than AUTOMATIC. The changes made in that fix have been reverted, and such statements are (again) allowed without regard to the value of this variable. (Bug #16715809, Bug #69045) * Replication: On Windows platforms, issuing SHOW SLAVE STATUS while the slave I/O thread was being terminated due to an error caused the slave to fail. (Bug #16662771) * Replication: A crash-on-commit error caused InnoDB to lose the previous transaction following execution of a RESET MASTER statement. This occurred because the prepare phase caused a flush to disk, while the commit phase did not perform a corresponding flush within InnoDB. To fix this problem, RESET MASTER now causes storage engine logs to be flushed on commit. (Bug #16666456, Bug #68932) * Replication: When used with the options --dump-slave --include-master-host-port, mysqldump printed the port number within quotation marks, as if it were a string value rather than an integer. (Bug #16615117) * Replication: When processing an Update_rows_log_event or Delete_rows_log_event from the binary log, the before image is hashed and stored in a hash table. Following this, the original table is scanned for the desired records; subsequent processing hashes each record fetched from the original table and performs a lookup for it in the hash table. However, columns read from the image that had originally been set to NULL could instead contain random or "garbage" data, causing the lookup (and thus replication) to fail with an error such as Could not execute Update_rows event on table.... (Bug #16621923) References: See also Bug #11766865. This bug was introduced by Bug #16566658. * Replication: The error displayed by SHOW SLAVE STATUS when a worker thread fails to apply an event contained no event coordinate information. The GTID for the event's group was also not shown. Now in such cases, the text shown for Last_SQL_Error is prefixed with the (physical) master binary log coordinates, as well as the value of gtid_next when this has been set. (Bug #16594095) * Replication: Due to time resolution issues on some systems, the time to be taken by the dump thread for a reply from the slave could be calculated to be less than zero, leading to Semi-sync master wait for reply fail to get wait time errors. Since this condition does not have a negative impact on replication, errors caused by these conditions have been reduced to warnings. (Bug #16579028) * Replication: Linker errors occurred if the header file log_event.h was included in an application containing multiple source files, because the file rpl_tblmap.cc was included in log_event.h. This fix moves the inclusion of rpl_tblmap.cc into the source files that use log_event.h. (Bug #16607258) * Replication: When one or more GTID log events but no previous GTIDs log events were found in the binary log, the resulting error was mishandled and led to a failure of the server. (This is an extremely rare condition that should never occur under normal circumstances, and likely indicates that the binary log file has somehow been corrupted.) Now in such cases, an appropriate error is issued, and is handled correctly. (Bug #16502579, Bug #68638) * Replication: Running the server with --log-slave-updates together with --replicate-wild-ignore-table or --replicate-ignore-table in some cases caused updates to user variables not to be logged. (Bug #16541422) * Replication: When using mysqlbinlog and the mysql client to roll forward two or more binary logs on a server having GTIDs enabled, the gtid_next variable was not properly reset when switching from the first to the second binary log, causing processing to halt with an error at that point. (Bug #16532543) * Replication: The mysqlbinlog options --include-gtids, --exclude-gtids, and --skip-gtids did not work correctly when trying to process multiple files. (Bug #16517775) * Replication: The warning issued when specifying MASTER_USER or MASTER_PASSWORD with CHANGE MASTER TO was unclear for a number of reasons, and has been changed to read, Storing MySQL user name or password information in the master info repository is not secure and is therefore not recommended. Please consider using the USER and PASSWORD connection options for START SLAVE; see 'START SLAVE Syntax' in the MySQL Manual for more information. (Bug #16460123, Bug #16461303, Bug #68602, Bug #68599) * Replication: When the size of an execution event exceeded the maximum set for the buffer (slave_pending_jobs_size_max), row-based replication could hang with Waiting for slave workers to free pending events. (Bug #16439245, Bug #68462) * Replication: Extra binary log rotations were performed due to concurrent attempts at rotation when the binary log became full, which were allowed to succeed. This could lead to the unnecessary creation of many small binary log files. (Bug #16443676, Bug #68575) * Replication: Attempting to execute START SLAVE after importing new slave_master_info and slave_relay_log_info tables failed with an empty error message. Now an appropriate error and message are issued in such cases. (Bug #16475866, Bug #68605) * Replication: Restarting the server after the slave_relay_log_info table had been emptied caused mysqld to fail while trying to return an error. (Bug #16460978, Bug #68604) * Replication: Following disconnection from the master, the slave could under certain conditions report erroneously on reconnection that it had received a packet that was larger than slave_max_allowed_packet, causing replication to fail. (Bug #16438800, Bug #68490) * Replication: An SQL thread error during MTS slave recovery caused the slave to fail. (Bug #16407467, Bug #68506) * Replication: When using the options --read-from-remote-server --stop-never --base64-output=decode-rows --verbose, mysqlbinlog failed to reset the counter used to store the current position within the file when the binary log on the server was rotated. (Bug #16316123, Bug #68347) * Replication: When using mysqldump to back up a database created with MySQL 5.6.4 or an earlier version, setting --set-gtid-purged=AUTO caused the backup to fail, because pre-5.6.5 versions of MySQL did not support GTIDs, and it could not be determined if GTIDs were enabled for the database. This fix makes sure mysqldump does not attempt to output a SET @@global.gtid_purged statement when backing up any pre-5.6.5 databases. (Bug #16303363, Bug #68314) * Replication: After a transaction was skipped due to its GTID already having been logged, all remaining executed transactions were incorrectly skipped until gtid_next was pointed to a different GTID. To avoid this incorrect behavior, all transactions---even those that have been skipped---are marked as undefined when they are commited or rolled back, so that an error is thrown whenever a second transaction is executed following the same SET @@session.gtid_next statement. (Bug #16223835) * Replication: Deadlocks could sometimes occur on group commits with a high number of concurrent updates, as well as when one client held a lock from a commit while another client imposed a lock while rotating the binary log. (Bug #16271657, Bug #16491597, Bug #68251, Bug #68569) * Replication: Modifying large amounts of data within a transaction can cause the creation of temporary files. Such files are created when the size of the data modified exceeds the size of the binary log cache (max_binlog_cache_size). Previously, such files persisted until the client connection was closed, which could allow them to grow until they exhausted all available disk space in tmpdir. To prevent this from occurring, the size of a temporary file created in this way in a given transaction is now reset to 0 when the transaction is committed or rolled back. (Bug #15909788, Bug #66237) * Replication: When semisynchronous replication was enabled, the automatic dropping on the master of an event created using ON COMPLETION NOT PRESERVE caused the master to fail. (Bug #15948818, Bug #67276) * Replication: When the master had more than one table with an auto-increment column, and the slave ignored at least one of these tables due to --replicate-ignore-table rules, but at least one them was replicated, even so---the replicated table or tables having at least one trigger updating one or more tables existing only on the slave---updates to any of the auto-increment tables on the master caused replication to fail. (Bug #15850951, Bug #67504) * Replication: Setting a SET column to NULL inside a stored procedure caused replication to fail. (Bug #14593883, Bug #66637) * Replication: The binary log contents got corrupted sometimes, because the function MYSQL_BIN_LOG::write_cache always thought it had reached the end-of-cache when the function my_b_fill() reported a '0,' while that could also mean an error had occurred. This fix makes sure that whenever my_b_fill() returns a '0,' an error check is performed on info->error. (Bug #14324766, Bug #60173) * Replication: The internal function MYSQL_BIN_LOG::open_binlog() contained an unneeded variable, which has been removed. (Bug #14134590, Bug #60188) * Replication: PURGE BINARY LOGS by design does not remove binary log files that are in use or active, but did not provide any notice when this occurred. Now, when log files are not removed under such conditions, a warning is issued; this warning includes information about the file or files were not removed when the statement was issued. (Bug #13727933, Bug #63138) * Replication: When replicating to a BLACKHOLE table using the binary logging format, updates and deletes cannot be applied and so are skipped. Now a warning is generated for this whenever it occurs. Note binlog_format=STATEMENT is recommended when replicating to tables that use the BLACKHOLE storage engine. (Bug #13004581) * Replication: Temporary files created by LOAD DATA INFILE were not removed if the statement failed. (Bug #11763934, Bug #56708) * Replication: After the client thread on a slave performed a FLUSH TABLES WITH READ LOCK and was followed by some updates on the master, the slave hung when executing SHOW SLAVE STATUS. (Bug #68460, Bug #16387720) * Microsoft Windows: On Microsoft Windows, passing in --local-service to mysqld.exe when also passing in a service name could cause a crash at startup. (Bug #16999777, Bug #69549) * The contents of SQL condition items such as TABLE_NAME, CONSTRAINT_NAME, an so forth were lost if resignaled by a stored routine condition handler. (Bug #17280703) * SELECT * from performance_schema.events_statements_current could raise an assertion due to a race condition under load. (Bug #17164720) * AES_ENCRYPT() and AES_DECRYPT() failed to work correctly when MySQL was built with an AES_KEY_LENGTH value of 192 or 256. (Bug #17170207) * InnoDB full-text searches failed in databases whose names began with a digit. (Bug #17161372) * A successful connection failed to reset the per-IP address counter used to count successive connection failures. This could possibly cause a host to be blocked, when the max_connect_errors limit was reached. (Bug #17156507) * Under load, truncating the accounts Performance Schema table could cause a server exit. (Bug #17084615) * With the thread pool plugin enabled and SSL in use, an error in one connection might affect other connections, causing them to experience a lost connection. (Bug #17087862) * Indexed lookups on POINT columns was slower for InnoDB tables in MySQL 5.7 compared to 5.6. (Bug #17057168) * The Performance Schema was built for embedded server builds. This no longer occurs. (Bug #17041705) * my_pthread.h unconditionally included pfs_thread_provider.h, a noninstalled header file, resulting in compilation failure when compiling MySQL applications against the installed header files. (Bug #17061480) * For debug builds, improper use of SAFE_MUTEX within dbug.c caused different code areas to have different ideas about size and contents of a mutex. This could result in out-of-bounds memory writes. (Bug #16945343) * Initialization of keycache_* variables (see Multiple Key Caches (http://dev.mysql.com/doc/refman/5.7/en/multiple-key-caches.ht ml)) during server startup could write to incorrect memory. (Bug #16945503) * Reads from message buffers for closed connections could occur. (Bug #17003702) * At server startup, it was possible to set the validate_password_length system variable to a value smaller than permitted by the values of other password-length variables related to it. (Bug #16957721) * The server could exit while using a cursor to fetch rows from a UNION query. (Bug #16983143) * The range optimizer incorrectly assumed that any geometry function on a spatial index returned rows in ROWID order, which could result in incorrect query results. (Bug #16960800) * A race condition in the thread pool plugin could cause status variables such as Aborted_connects not to be incremented and permitting concurrent kills to happen for the same thread ID. (Bug #16959022) * mysql_secure_installation did not properly clean up the mysql.proxies_privs table for removed accounts. (Bug #16959850) * The server did excessive locking on the LOCK_active_mi and active_mi->rli->data_lock mutexes for any SHOW STATUS LIKE 'pattern' statement, even when the pattern did not match status variables that use those mutexes (Slave_heartbeat_period, Slave_last_heartbeat, Slave_received_heartbeats, Slave_retried_transactions, Slave_running). Now attempts to show those variables do not lock those mutexes. This might result is slightly stale data, but better performance. (Bug #16904035) * Full-text phrase search in InnoDB tables could read incorrect memory. (Bug #16885178) * It was not possible to keep several major versions of MySQL in the same yum repository. (Bug #16878042) * The Performance Schema could spawn a thread using incorrect instrumentation information. (Bug #16939689) * The Batched Key Access method could return incorrect results on big-endian machines if a table buffered in the BKA join cache used a storage engine such as InnoDB or MyISAM with little-endian storage format, and then the next table used a storage engine such as NDB with native-endian storage format. (Bug #16853897) * The error string for ER_COL_COUNT_DOESNT_MATCH_PLEASE_UPDATE string contained a hardcoded database name ('mysql.%s'), which is incorrect when the error referred to a table in a different database. (Bug #16813605) * Excessive memory consumption was observed for multiple execution of a stored procedure under these circumstances: 1) The stored procedure had an SQL statement that failed during validation. 2) The stored procedure had an SQL statement that required repreparation. (Bug #16857395) * HAVE_REPLICATION now is set from CMake rather than in my_global.h so that it is not dependent on my_global.h having been included. (Bug #16768511) * CMake now assumes the existence of standard C header files such as stdlib.h and stdarg.h. (Bug #16748528) * Some errors in MySQL 5.7 had different numbers than in MySQL 5.6. (Bug #16780120) * Removing a server RPM package did not shut down the existing server if it was running. (Bug #16798868) * INSERT ... ON DUPLICATE KEY UPDATE could cause a server exit if a column with no default value was set to DEFAULT. (Bug #16756402) References: This bug is a regression of Bug #14789787. * An assertion could be raised when the optimizer considered pushing down an index condition containing an updatable user variable and did not contain fields from the index. (Bug #16804581) * The function fill_locks_row(), which is responsible for providing data for the INFORMATION_SCHEMA.INNODB_LOCKS table, would try to look up the B-tree page in the buffer pool for INFIMUM and SUPREMUM records, both of which have a predefined heap_no. This generated unnecessary buffer pool contention and caused information to be omitted when a page was not available in the buffer pool. This fix removes the buffer pool lookup for PAGE_HEAP_NO_INFIMUM (heap_no=0) and PAGE_HEAP_NO_SUPREMUM (heap_no=1) from fill_locks_row(). (Bug #16684523)
|• MySQL Community Server 5.7.2 has been released (part 3 of 4)
|Bjorn Munch
|21 Sep


text:
The Football League has announced that its member clubs have voted "voted to reduce the number of substitutes that can be named on the teamsheet for matches in the npower Football League from 7 to 5" (1). As a rationale for this change, it was stated that "This was felt to be a sensible and prudent step given the financial challenges facing many football clubs and the commitment made earlier this summer to adopt UEFA's Financial Fair Play framework", or, to put it another way, it's ultimately a good way of cutting costs by employing a marginally smaller squad.
I for one would like to see a change in the rules regarding the actual substitutions allowed. Nothing imposes such a feeling of anti-climax at the end of a tense game is the tactical (and essentially unnecessary) substitution of players as the final whistle approaches. It has far more to do with the 'gamesmanship' of Stephen Potter than the gamesmanship of what used to be the Beautiful Game.
Musing on this, I turned out an early report by the Football League (but actually published in the FA Yearbook 1966-67, and hence not available online I'm afraid) called "Substitutes: An Experiment Justified".
It begins "When the Football League introduced its Substitute Rule at the beginning of the 1965-66 season, it was received with misgivings from many people inside and outside the game. Many of those who were against it chose to ignore the fact that substitution of players for injury has been permitted by the Laws of the Game for a good number of years". The second sentence came as a surprise to me. Did substitution actually take place before 1965? Surely in that era the culture was for a player to battle on, hiding injury in spite of the danger of exacerbating it causing permanent injury. Think Bert Trautman.
The report continues: "There were many forecasts of the amount of cheating [sic] and misuse which would follow. In point of fact, there has been no instance of the Substitute by a manager in order to gain a tactical advantage over his team's opponents." Would that the same could be said today.
Data in the report broadly backs up the claim. It records that 772 substitutions had been made in 2,028 League games. These occurred during games thus:
|Period of game
|Up to 10 minutes
|11 to 19 minutes
|20 to 29 minutes
|30 to 45 minutes
Total, first half
|46 to 59 minutes
|60 to 69 minutes
|70 to 79 minutes
|80 to 85 minutes
|86 to 90 minutes
Total, second half
The number of substitutions in those days was limited to one, and, as the report says "If substitution is raised to two, this would increase the danger of substitutes being used tactically, which is really what everyone wants to avoid". Substitution was, in any case, only permitted then for injury.
Subsequently 'everyone' apparently stopped wanting to avoid the use of tactical substitution, and we have seen the number permitted on the bench grow to 5 in 1996 and then the about-to-be abandoned level of 7 in 2008. Memory fails me on when tactical, i.e. for reasons other than injury, substitution was first allowed (any offers?).
Do I detect in all of this the idea that the Football League cares less about the game and its enjoyment by fans today than it did in 1965, and cares more about the costs of its member clubs?
Perhaps I'm being a little harsh. Substitution for injury is a principle I would strongly defend, on the grounds of players' well-being, and I wouldn't want a return to pre-1965 practices. It's just that it seems to me we have gone too far with tactical substitution, something which I still want to avoid, to use the League's phrase.

subset: commoncrawl


text:
(08-21-2013, 01:50 PM)Bring4th_GLB Wrote: Absolutely, please do! Send it to the contact address at http://llresearch.org/contact.aspx.
(08-21-2013, 01:50 PM)Bring4th_GLB Wrote: Who makes that judgment call for others, though? What is the ultimate, universal standard that applies equally to all people irrespective of their depth of understanding and their position along the evolutionary timeline?
(08-31-2013, 04:00 AM)Light of Wisdom Wrote: Firstly, for some people it might have to do with being appreciated which in turn has to do with self-worth. Which in turn has to do with acceptance of other selves.
(08-31-2013, 04:00 AM)Light of Wisdom Wrote: I am certainly for the occasional joke or differently toned response thrown into a topic of a certain flavor...
Quote:Light of Wisdom: Download Link: http://www.mediafire.com/?bgpwczf7zds4d1o
Quote:Light of Wisdom: One universal standard I see is "power". Power comes from knowledge and it enables one to pursue one's desires.
Quote:Peregrine: First, I don't know how to spell this out, but it seems to me that various people enter into the Material at different levels. Maybe some are interested in the more literal aspects, some care about how it could support whatever their own biases are, some thrive on the general social aspect, some on the intellectual stuff, some on the experiential, some feel it's a groovy thing to associate with, and so on. The differentiation and support of these different levels of approach seems to be guided by a passive process. I wonder if the management would consider refining this deliberately...somehow?
Quote:Peregrine: Secondly, speaking of deeper engagement, in your proto-menu I didn't notice an emphasis on ways people can contribute to "the cause," not monetarily, but in other ways. I can't think of anything specific at the moment, but it's something you may wish to ponder for a moment.
Quote:Peregrine: So, what I'm suggesting is an overall format that allows the scholarly types to do their work while offering a discrete place for those seeking advice about a current issue in their lives, another spot for the casual chatter and so forth. From the way the forums are set up it seems as though this was originally intended. I'm averring that such a goal could be more successfully achieved.
Frankly, I feel that the fact that the pursuit of deepening serious understanding is not segregated from the more temporal or off-hand dialogue on this site prevents there forming an accessible body of discussion of lasting value. This perceived fact is only heightened by the general turnover of site users where new people are entering and the more experienced often lose interest. That is, they are offered no satisfying means of engagement.
(09-10-2013, 05:57 PM)Bring4th_GLB Wrote: However, again we come back to the problem of universality. Not everyone wants to be empowered. Many people involved in fundamentalist religious interpretation would emphatically, albeit unconsciously, prefer *not* to have the power of responsibility, of creating their own reality, of having to find their own way, etc.
(09-10-2013, 05:57 PM)Bring4th_GLB Wrote: I think it a worthwhile essay, though! "Sorting the Diamonds from the Rough: How Most Channeled Information is Rubbish." : )
(09-10-2013, 11:00 PM)kainous Wrote: A few things that were impressed on my mind as soon as I read this:
A comments section per question (Ra reading) that is naturally hidden so that you must "do something" (i.e. click an expander) to view them. This would need to be heavily moderated, and the comments to be up/down voted. Overall, this would enable the community to:
Provide links, images and sites that may help with explanations of some of what they have uncovered on the web by other seekers
Tie in some of what the community has seen elsewhere (Bible verse, Tao Te Ching, physics book, etc.)
Express where some words and phrases come
Seek farther by explaining what they've read according to their own lives
(09-10-2013, 11:00 PM)Light of Wisdom Wrote: With maybe a classier subtitle:
How Most Channeled Information is Applesauce.
How Most Channeled Information is Folderol
How Most Channeled Information is Flapdoodle
Quote:Effectively using a bullet-point list, you have spoken to my heart. : )
(09-28-2013, 05:58 AM)Anchor Wrote: How is your fundraiser going? (I just moved you nearer the goal.)
(07-29-2013, 02:09 AM)plenum Wrote: (07-29-2013, 01:19 AM)Bring4th_Admin Wrote: Financial assistance: Our goal is to raise $3,000 to pay for all hosting-related expenses (bandwidth/storage/hardware/software/3rd-party services), and to extend some support for Steve for the enormous investment of time and energy he will be devoting to this project. Given the increased requirements and scope of the project this time around, Steve happily agreed to provide web development services at a deeply discounted rate.
my word is my bond: 100 bucks donated.
(07-29-2013, 01:19 AM)Bring4th_Admin Wrote: Financial assistance: Our goal is to raise $3,000 to pay for all hosting-related expenses (bandwidth/storage/hardware/software/3rd-party services), and to extend some support for Steve for the enormous investment of time and energy he will be devoting to this project. Given the increased requirements and scope of the project this time around, Steve happily agreed to provide web development services at a deeply discounted rate.
(03-27-2014, 03:38 PM)lawman3030 Wrote: Welcome my brothers and sisters I am the Naacal Priest from Khem known as Amon Ra, as a Light Warrior and empath I have been tasked to light pathway to the temple of RA known as the L/L Research Foundation and assist the Light Workers in awakening during the "Harvest"..
There are many who the thin veil of forgetfulness was been lifted from them and they now seek to join us at the table to partake of the fruits of wisdom thus our mission is clear to light the way..
As it is above.. So shall it be below..


text:
From cchtml.com
Did anyone _ever_ tried successfully to build a debian packet since about 2009??? I've used the --keep keyword of the installer and watched the code. This is ridiculous:
- Detect x* dir name corresponding to X_NAME
case ${X_NAME} in woody|3.0) echo "Error: ${X_NAME} is no longer supported by this installer" ; exit 1 ;; etch|stable|4.0) X_DIR=x710; X_NAME=etch;; lenny|testing) X_DIR=x710; X_NAME=lenny;; sid|unstable) X_DIR=x710; X_NAME=sid;; experimental) X_DIR=x710; X_NAME=experimental;; *) echo "Error: invalid package name passed to --buildpkg" ; exit 1 ;; esac
Besides the fact that lenny hasn't been testing for a long time now, there isn't a X_DIR "x710" in this whole packet thus you don't need to wonder about it is failing all the time with the error: "cp: cannot stat `/tmp/fglrx-install.1GJKvS/x710_64a/*': No such file or directory"


text:
Feel My Presence
By Carlo Longino
The phone is a great synchronous communications device. You call people, they answer, you talk—what could be easier or more efficient? But the phone isn't so great at asynchronous communications—that is, communication that doesn't require people to be actively conversing at the same time. If you call someone and that person's not around, you leave a voicemail and the awful game of telephone tag begins. Text messages are a little bit better at the whole asynchronous thing, but there's still the expectation that messages will be returned immediately; when somebody doesn t text you back right away, you wonder why.
One of the big selling points of cell phones has always been that they allow people to be reached at any time. While this initially seemed like a good idea, plenty of people now consider it a drawback; they re tiring of the constant calls from work, the text messages from friends, or the never-ending flow of e-mails to a BlackBerry. Of course, the simplest solution is just to shut the phone off, but that s sort of an all-or-nothing proposition. What would be really useful would be some sort of status indicator with which users could state some current information—their availability, at the very least, but perhaps their location or their mood, too. This sort of user information is referred to under the umbrella term of "presence," and as communication becomes even more pervasive in our lives, it will take on great importance.
The simplest and most basic example of presence is the instant-messaging status message: "away", "do not disturb," "available," and so on. But even these have begun to evolve, with many IM programs letting users customize their message to better fit their current state (such as "in a meeting"). Skype lets users set status to "Skype Me," an open invitation for anybody and everybody on the system to chat. This message isn t just an indicator of availability—it s also a social signal that tells the world a certain user is looking to interact with fellow humans.
Another way IM status messages are becoming better indicators of presence is how they handle interaction with mobile phones. On AIM, for instance, users who have an account set up to forward messages to a phone are given the status message "mobile." This indicates not only that they're away from a computer, but that they can receive messages on a phone, so users on the other end know not to send an image or something else unsuitable for the device. This is how presence goes beyond just being a status message; it provides information so people can better suit their communications to fit the receiver's current context.
But presence can also be used to help people control incoming communications. Say I set my status to "work": this could route calls from my friends straight to voicemail, or defer their SMS or e-mails. Conversely, when my presence indicates that I'm not at work, calls from my boss or co-workers don't make my phone ring. As fixed and mobile telephone networks converge and merge with traditional Internet services, these types of rules will become necessary—not just so we can better control how people contact us, but to ensure that the right types of communications are directed to the right device.
Presence solutions exist today, but so far, few (if any) mobile operators have chosen to implement them. But they'll become more common as these operators shift to all-IP networks and VoIP. Still, there are already several applications available that offer a rough approximation of presence. Nokia's Sensor application for some of its smartphones is one. Users can create a profile in Sensor, which then searches via Bluetooth for other phones in the vicinity running the application. Users can look at other peoples' profiles and messages, then ping them with messages. It's a pretty crude example of presence, as nothing happens without an explicit action from a user (i.e. changing the profile, or scanning for other Sensor users). And, of course, it has a number of shortcomings—it only works on a small number of phones, and it's dependent on a person with such a phone actually having and running the device. Sensor does, however, illustrate what will be one of the top uses for presence services—hooking up.
Dodgeball is another service that shows some of the promise of mobile presence, again in a social setting. Users can broadcast their location to their friends by sending a message to the service indicating they're at a certain bar or restaurant—and, presumably, also indicating they want to hang out. Dodgeball sends the message, then replies if any friends or friends-of-friends are within a certain radius. Users can also add "crushes" who get notified if they check in with a location nearby. While the location element is significant, Dodgeball messages are more than that: they're "here I am, come play with me" come-ons, signaling an intent or a desire as much as a location.
So if you're overwhelmed by incoming communication, help is on the way. With so many devices making it possible to simply communicate more, presence will help us communicate better.
Carlo Longino is a writer and analyst that follows the mobile industry. He's co-editor of MobHappy, and also an analyst for Techdirt. He can be reached at firstname.lastname@example.com.
Read more Airtime. The column appears every Tuesday on Gizmodo.


text:
$BB'$ and $CC'$ are heights of a given $\triangle ABC$ ($AB\ne AC$). $M$ is mid-point of $BC$ and $H$ is orthocenter of $\triangle ABC$ and $D$ is intersection of lines $B'C'$ and $BC$. Prove $DH \perp AM$.
My idea is to prove that $AC'EHB'$ (or $C'BME$ or $B'EMC$) is cyclic. I tried lots of things, but I think the main thing I lacked in all my deductions if usage of $M$ being a mid-point.
Other idea is to prove that $H$ is orthocenter of $\triangle AMD$, since we already have $AH\perp MD$, it's enough to prove $MH\perp AD$. If $MH\cap AD=\{G\}$, then we should prove that $G$ lies on circle around $AC'(E)HB'$. So another idea would be to prove that some of triangles "composed" of $A,C',E,H,B',G$ with at least once vertices being $E$ or $G$ has circumradius $AH/2$. Some trigonometry?
Another idea would be to mark $E'$ as foot of height from $D$ to $AM$ and then use Menelaus theorem to prove that $A-H-E'$, that is, $E\equiv E'$.
EDIT. The only place where I think I can use the fact that $M$ is midpoint of $BC$ is that $BM=C'M=B'M=CM$, so there are some equal angles. It should help us prove $E$ lies on circumcircle of $\triangle C'BM$, that is, $C'BME$ is cyclic, because we have $\angle MC'B=MBC'$. It's also interesting to notice that once we prove $E$ lies on mentioned circle, we'd conclude that $DE$ is bisector of $\angle C'EB$, which might be a clue but I still can't figure anything out.
EDIT 2. I also thought about using the fact that $\triangle CMA$ and $\triangle BMA$ have same areas. Then we have $AC\sin\alpha_1=BC\sin\alpha_2$ where $\alpha_1=\angle CAM=\angle CAE$ and $\alpha_2=\angle BAM=\angle BAE$, so we might be able to use that somehow for the idea about circumradius being $AH/2$, because we can use sine laws on triangles $\triangle AC'E$ and $AEB'$ (we need to prove $\angle C'EA=\angle B=\beta$ and/or $\angle B'EA=\angle C=\gamma$), from which we might reduce this to proof about similarity of some triangles. Seems like a nice idea that could work but I can't seem to get much from it for now.
Another thing, about the idea of proving that $H$ is orthocenter of $\triangle AMD$. I'm not sure is it better to mark $MH\cap AD=\{G\}$ and prove $MH\perp AD$, or other way around? Or maybe to mark intersection of $AD$ and circumcirle of $AC'HB'$ and $\triangle ABC$ (maybe this is important?) as $G$ and then prove $H\in GM$?
Just adding ideas, since I can't seem to get anywhere, almost like we lack just a little bit something and all of the ideas might actually work very similarly.
Also, since people wondered if it's Olympiad problem or homework problem: it's from Serbian mathematical magazine for high schoolers, it's in the section where one of the hardest problems are. But I still find it harder than the usual ones from geometry.
Please no analytic geometry or complex numbers, and try avoiding vectors unless used only for less significant lemmas.


text:
CensusAtSchool to be launched this week, Oct 2005
|Page tools: Print Page Print All RSS Search this Product
CensusAtSchool to be launched this week
A major initiative in online education - CensusAtSchool - will be launched at the Melbourne Museum on Thursday, October 20, at 10.30am.
The CensusAtSchool program, which will involve students from Years 5 to 12, is free, voluntary and open to all Australian schools.
As its name implies, it basically involves students from around the country taking part in their own census.
It has been organised by the Australian Bureau of Statistics in cooperation with state and federal education authorities and is designed to show that the study of statistics can be fun as well as educational.
No individual will be able to be identified in the program and the strictest privacy measures and Internet security will be in place.
CensusAtSchool will be officially launched at the museum by the federal Parliamentary Secretary to the Treasurer, Chris Pearce. The Australian Statistician Dennis Trewin will also speak.
Media personality and comedian Adam Spencer, who has a First Class Honours degree in Pure Mathematics, will be the keynote speaker. His book, Little book of numbers,has been a success both in Australia and overseas.
After the speeches, school students will give a computer demonstration of how CensusAtSchool works.
The ABS expects that the project will lead to improvements in student understanding of statistics and perhaps introduce students to the possibility of a career in statistics.
More information can be obtained from the ABS website at www.abs.gov.au. Click on the link to CensusAtSchool.
FURTHER INFORMATION: Media requests and interviews
Document Selection
These documents will be presented in a new window.


text:
Mustad VF F nail
Reliable and robust for more traction
The VF F is a high-quality nail in the traditional French style with a short neck and a square head.
The nail is suited to a wide range of horseshoes and horses, because apart from other considerations this nail model is available in a wide range of sizes. The VF F is a reliable and robust nail suitable for horses that are used on varied terrains where high traction forces can act on the horseshoe.
Ask the expert
Questions about this product?Let us know
Find your nearest dealer
Product summary
- Model
- French style, short neck
- Type
- square crown head
- Sizes
- VF 4F (44mm) - VF 9.5F (71.5mm)
- Terrain
- Turf/Grass
- Stoney ground
- Sand
- Activity
- Carriage driving
- Draft
- Draft horse showing
- Pleasure riding
- Horse pulling
- Pleasure driving
- Trail
- Trail riding
Find your nearest dealer
Good to know
- square head and short neck
- very suitable for horses that face demanding terrains with high traction forces
- not suitable for very thin hoof walls
Stéphane Bréhin, farrier in France
By delivering detailed information, good quality, a high service level and by showing involvement for their horses, I have gained the respect of my clients
Engineer, farrier, salesman, idealist
Christoph Müller, a German farrier and sales representativeRead story


text:
Add a sportier look to the F650GS/Dakar with the new Single Seat option.
The New single seat option comes complete with supplemental storage rear box, luggage grid, and lock and key.
Installation is quick. Simply replace the current seat configuration.
Form and function at it's best.
I just took a loop with this product--From Reno, through Washoe Valley, Carson, Genoa, Markleeville, over Monitor Pass, South to Bodie, off-road out the backside of Bodie to Mason, and then through Silver Springs, Fernley, and back to Reno.
Great ride--Great Product!
Comfortable and convenient!
Please note: Dimensional Shipping Weight is listed, compartment not watrerproof.
BMW G650GS|F650GS|Dakar|Sertao Single Seat w/Storage
BMW Original Parts


text:
The "Lytton Gateway" project, proposed by Lund Smith, Boyd Smith, Jim Baer and Scott Foster, represents in many ways the city's drive to encourage dense developments near major transit centers — a key tenet of New Urbanism. The proposed 64-foot-tall building would stand at the intersection of Alma Street and Lytton Avenue, right across the street from the downtown Caltrain station. A Shell gas station that formerly occupied the property closed in 2010.
Without the zoning change, the development would have been limited to a two-story office building.
The planning commission had previously endorsed the appearance and the concept of the new building, which the city's Architectural Review Board had also approved. But at the Jan. 22 hearing, commissioners argued that the applicants should provide more benefits to justify the increased intensity. The applicants returned this week with an expanded proposal, one that would provide more public parking, more units of affordable housing and a pledge to help the city fund a downtown parking study and landscape improvements. The proposal includes 14 units of housing, seven of which would be below market rate, ground-floor retail and offices on the floors one through four.
At a previous hearing, commissioners said they were concerned about the insufficient number of parking spaces proposed by the applicants. Several residents from the adjacent Downtown North neighborhood near the site urged the commission Wednesday not to green-light the project unless it provides more parking spaces. Among them was Sally-Ann Rudd, president of the Downtown North Residents Association. Rudd said she was concerned about the prospect of Lytton Gateway employees taking over the parking spaces in her residential neighborhood.
"We're already parked up during the day from a mixture of Caltrain commuters and downtown employees," Rudd said. "This has been a subject of some irritation from the residents."
To address the community's and the commission's concerns, the applicants agreed to provide eight surface parking spots and 14 underground-parking spots to the public in addition to the 123 spots they had previously said the project would include. The applicants also agreed to pay $60,000 to help the city fund a downtown parking study and to launch a full-service attendant-parking program that would add another 34 spots to the building.
"We truly believe this is the wave of the future for downtown parking," Lund Smith told the commission, referring to the attendant-parking program.
The applicants also offered to buy Caltrain Go Passes for all of the building's tenants to encourage less driving and to provide two electric-vehicle charging stations.
Tanaka, the most vehement advocate of more parking, urged the applicants to make these 34 attended spots available to the public as metered parking. The rest of the commission rejected the proposal and the applicants said Tanaka's proposal would create security concerns for the building's tenants.
Fineberg was the only other commissioner to vote against the proposal though even she conceded that the new package of public benefits is sufficient. Her main concern was that the project is inconsistent with the Comprehensive Plan, the city's land-use document that is currently undergoing revision.
While the planning commission had earlier voiced reservations about the project's proposed benefits, members agreed Wednesday that the applicants' latest revisions are up to par. Chair Eduardo Martinez called Lytton Gateway a "good project," and Commissioner Samir Tuma thanked the applicants for being "dogged in their efforts to come up with more creative, different public benefits." He praised the project's evolution over the past four meetings.
"No project is a perfect project; no project doesn't have an impact. But I think this has come a long way from the day you walked into the planning office and said you'll build this building," Tuma said.
This story contains 736 words.
Stories older than 90 days are available only to subscribing members. Please help sustain quality local journalism by becoming a subscribing member today.
If you are already a subscriber, please log in so you can continue to enjoy unlimited access to stories and archives. Subscriptions start at $5 per month and may be cancelled at any time.


text:
Get started
- Download the latest version of iOS or iPadOS for your iPhone, iPad, or iPod touch.
- Make sure that your device is signed in to the iTunes & App Store with your Apple ID.
Find iMessage apps in the app drawer
The app drawer gives you quick access to apps that you can use with Messages. To see your app drawer:
- Open Messages.
- Tap to start a new message. Or go to an existing conversation.
- Swipe left or right over the app drawer to find the app that you want to use.
Here are some apps that are automatically in your app drawer:
Store: Download iMessage apps to use with Messages.
Photos: Quickly add photos to your messages right from the app.
Music: Share recently played songs from Apple Music.
Digital Touch: Use Digital Touch to send sketches, taps, kisses, heartbeats, and more.
#images*: Find hundreds of trending GIFs to add to your messages.
Apple Pay: Send and receive money with Apple Pay.*
Animoji: Create and share animated characters that use your voice and mirror your facial expressions.*
Memoji: Create your custom Memoji to match your personality and mood.*
*#images and Apple Pay aren't available in all countries or regions. If you find an issue or have a concern with content found in #images, you can report the content or remove the #images app. You need a compatible iPhone or iPad to use Animoji and Memoji.
Download iMessage apps
You can find and download apps to use with iMessage in the App Store for iMessage. Here's how:
- To go to the App Store for iMessage, tap .
- Tap or the price icon next to the app, then tap Install. You might need to enter your Apple ID password to complete the purchase.
- Tap to return to your message.
After the app downloads, you can find it in your app drawer.
Some apps let you make additional purchases within the app. If you set up Family Sharing, you can use Ask to Buy to help control app downloads and in-app purchases. Learn more about in-app purchases.
Manage iMessage apps
You can add apps to your Favorites so you have quick access to them in the app drawer. You can also reorder apps in the app drawer, remove the ones you don't want, and more. Here's how:
- From the app drawer, swipe left and tap .
- Tap Edit in the upper-right corner to do the following:
- To add an app to your Favorites, tap .
- To remove an app from Favorites, tap , then tap Remove from Favorites.
- To reorder apps in the app drawer, touch and hold , then move the apps in the order that you want.
- To hide an app, turn it off.
- Tap Done.
Delete iMessage apps
- Open Messages.
- Tap to start a new message. Or go to an existing conversation.
- Swipe left over the app drawer and tap .
- Swipe left over the app, then tap Delete.
Do more with iMessage
Use the App Store on your iPhone, iPad, iPod touch, Apple TV, or computer to download apps.


text:
Improving image quality and optimizing dose in every Artis system.
Care for practical, hands-on information about CARE+CLEAR? Here you can discover more about your colleagues' experiences with Dose Saving and Image Quality in Interventional Imaging. Find out first hand about the advantages of our comprehensive portfolio.
Customer Statements
P. Vierbeck, A. Funk, H. Galluhn, R. Kügler, Endoscopy Technicians
Klinikum Altenburger Land, Altenburg
"Low-dose protocols in endoscopy and ERCP are very significant. We often use protocols at 0.81 μGy/image in 22 cm format (corresponding to 0.41 μGy/image in 48 cm format) and always pulsed fluoroscopy (CAREvision)."
"Adjustment of radiographic image possible without radiation exposure, 'Super!' (CAREprofile and CAREposition)"
Dr. Michael Repp, MBA
Klinikum Altenburger Land, Altenburg
"Using CLEAR technology, the system allows for working with the lowest possible amounts of contrast agent with simultaneously high detail recognition of the gastrointestinal tract, especially the pancreaticobiliary ductal system. At the same time the optimized gray scale resolution ensures safe positioning of implants in stenoses of the gastrointestinal tract through certain detection of the stent and its markers."
Dr. Beate Faust-Herzog
Heinrich-Braun-Krankenhaus GmbH, Kirchberg
"An important aspect in gastroenterology is a non-overexposed fluoroscopy image reproduced 1:1 in the digital image."
Prof. Ansgar Berlis
Klinikum Augsburg
"Manufacturers must look after the safety of both patients and medical staff. This type of safety system can determine whether or not a device is selected, which means that manufacturers must treat them as a quality criterion rather than offering them for an additional charge. Who would drive an automobile today without a seatbelt and an airbag?"
"We should be concerned about everyone's well-being. And if we can generate better images using less radiation, then it makes sense for us to do so."
Prof. Thomas Albrecht
Vivantes Hospital Berlin
"I consider minimizing radiological exposure for the intervention personnel to be a matter of key concern. In this connection, progress in the area of device technology must be supplemented by observance of radiological protection measures by the staff."
Dr. Olaf Göing
Sana Klinikum, Berlin
"These days, when we have a better understanding of the connections between radiology dose and potential illness than we did previously, I think that features that enable us to reduce the dose of radiation should be provided as a matter of course. There should not even be the possibility of choosing differently just to cut costs."
"Protecting employees as part of our 'constant activity' in the cardiac catheterization laboratory cannot be rated highly enough."
"If I were buying a catheterization unit I would classify radiological dose-reduction features as a fixture, if the case arose. All other options depend on financial and medical necessity and can still be negotiated, unlike radiological protection."
Charles Mazzarese
Stony Brook Medical Center, New York
"syngo DynaCT and the integrated CARE feature make the task of keeping the dose low virtually effortless"
Prof. Johannes Brachmann
Coburg Clinic, Coburg
"New image algorithms from recent updates deliver the best images we have ever seen."
"Today images show a very homogenous contrast distribution, sharp vessel edges, and minimal background noise. Siemens has done a great job with image processing enhancements."
Dr. Gerard O´Sullivan
University College Hospital Galway, Ireland
"There are certain differences which make the Siemens system in my opinion at least superior, specifically iGuide, the DynaCT, and the ability to pan to a specific position on the patient without using Fluoroscopy is a massive advantage. They seem like little things, but it´s an accumulative thing."
Customer Video statements
Hilde Bosmans
UZ Leuven, Belgium
Join the Right Dose Community
Radiation dose and radiation dose protection for patients and staff is one of the most discussed topics in medical imaging.
Now you can easily and directly share and discuss dose management strategies, settings, and protocols with other clinical experts.
Join the Right Dose Community and benefit from direct peer-to-peer exchange as well as exclusive Siemens information.
The statements by Siemens Healthineers' customers described herein are based on results that were achieved in the customer's unique setting. Since there is no "typical" hospital and many variables exist (e.g., hospital size, case mix, level of IT adoption) there can be no guarantee that other customers will achieve the same results.


text:
Meetings and Events
The Vision Council offers its members many opportunities to meet with other industry leaders throughout the year. The Vision Council facilitates and participates in a variety of events including industry-wide tradeshows such as International Vision Expo, and members-only opportunities including Division and Committee meetings, professional forums, and a yearly Executive Summit.
International Vision Expo
International Vision Expo East and West, the worldwide conference and exhibition for eyecare and eyewear, are trade-only events which draw more than 30,000 eyecare providers each year. More optical professionals make their buying decisions at International Vision Expo than any other annual industry event in North America.
Members of The Vision Council receive discounted rates per net square foot - upwards of 10 percent - for exhibiting at any International Vision Expo & Conference. Members also receive instant access to several other discounts and privileged industry information and statistics.
Division and Committee Meetings
Division, committee and task force meetings provide great opportunities to network with other members that share your business needs and perspectives. Our groups meet regularly to face issues that are important to unique segments of the industry, share best practices, and increase their networks.
Executive Summit
The Vision Council's Executive Summit has become the "must-attend" event for senior executives in the vision industry. Your leadership team will benefit from numerous opportunities for executive-level networking, hot-topic panel discussions, leadership development, economic trend updates, and business strategies.
Lab Division Meeting
The Lab Division meeting is the complete lab event. Each component, from education to exclusive receptions and events, has been thoughtfully designed to help lab professionals grow and succeed. Combined with the continuing education and expansive exhibits at International Vision Expo West - the largest ophthalmic event in the Americas - the Lab Division meeting provides the perfect setting for you to hear about hot topics, network with labs and test drive equipment before implementing new ideas and technologies into your business.
COLA Spring Meeting
The annual COLA Spring Meeting is a must-attend two-day event featuring the latest industry updates and educational sessions.


text:
Before I head off to college this summer, my family is taking a road trip to Iowa and the twin cities. We're no strangers to road trips; we've done two cross-country trips as a family. This time, however, we want to make our trip more eco-friendly.
Eco-friendly rental cars
My dad just bought a hybrid car, so even though it's a little small, we'll take that car to get great gas mileage and reduce our carbon emissions.
My favorite part of our Honda Insight is the green leaf that lights up next to the fuel gauge when you are driving efficiently. Photo By Honda News/Courtesy Flickr.
If you don't own a hybrid vehicle, consider renting one for your trip. You'll get better gas mileage and reduce your carbon emissions.
Major rental cars now offer hybrids in select locations. Enterprise Rent-A-Car is in the lead for the most hybrid vehicles available, followed by Hertz and Budget.
If the rental car location does not offer hybrids, rent the smallest car possible. Make sure to request hybrids so the company knows you're interested!
Once you reach your destination, bike, walk, or take public transportation around town to minimize your carbon footprint.
Organic snacks to go
No road trip would be complete without delicious snacks. Granola trail mix is a great way to go. Now I can take my granola to go with MixMyGranola. I'm drooling just looking at the photos of natural ingredients on the website.
A 16-ounce can of organic granola cost $5, and each of the 45 mix-ins, such as nuts, fruit, cereal, candy and chocolate, costs $1–$2. MixMyGranola also offers a free nutrition calculator to check your mix as you go. If you fall in love with the mix you create, you can save the mix ID to order your perfect concoction again and again.
Not feeling creative? MixMyGranola has 20 pre-mixes such as Energy Booster and Healthy Heart mix that run from $7–$11. Photo Courtesy MixMyGranola.
MixMyGranola uses USDA organic ingredients. The stylish granola containers are fully recyclable, and the label is printed with soy-based ink.
Need another no-fuss snack for the road? Late July also carries the USDA organic seal and specializes in organic cookies and crackers. Late July is a small, family-owned business in Barnstable, Massachusetts.
Late July's 21 count Cookie and Cracker Sampler is the best road trip option. The sampler includes dark chocolate sandwich cookies, peanut butter sandwich crackers and mini cheddar cheese sandwich crackers. It has a unit price of less than $1 per serving at $19.
Energy-efficient hotels
Unfortunately, eco-hotels just recently hit mainstream appeal, so finding one may be a challenge. Flexibility about location may be necessary. The Environmental Protection Agency suggests choosing an Energy Star-labeled hotel.
Want a truly green getaway? The Cairo Marriot hotel is an eco-friendly and beautiful place to stay. Photo By Mussad Hussein/Courtesy Flickr.
Energy Star-labeled use at least 35 percent less energy and emit at least 35 percent less greenhouse gas emissions than their competitors.
The EPA also suggests you do the following once you're in your room:
• Turn off the lights and TV when leaving the hotel room.
• Adjust the thermostat to an energy-saving setting so it doesn't heat or cool the room while empty.
• Unplug electronics such as cell phones chargers and laptops when not in use.Open curtains to take advantage of daylight when possible.
• Reuse linens to save both water and energy.


text:
(Redirected from UPnP Sharing)
| Video library
Music library
|Media sources
Kodi has several built-in UPnP A/V (Universal Plug and Play Audio Visual) features, including the ability to receive UPnP and DLNA content pushed to Kodi, browse UPnP and DLNA media sources, sharing a Kodi library with other UPnP and DLNA devices, and even controlling UPnP and DLNA devices. UPnP is also the easiest way to share a library from one Kodi device to another.
UPnP may refer to:
- UPnP/Media source - A type of media source that can be added in Kodi to receive videos from a UPnP server
- UPnP/Server - Kodi's UPnP server abilities
- UPnP/Client - Kodi as an UPnP/DLNA client ("play to" target)
- HOW-TO:Share libraries using UPnP - How to share Kodi from one device (as a server) to another Kodi device (as a media source).
- UPnP/Developer notes - Notes for developers.


text:
Tuesday, November 10, 2009
Should Andy Pettitte Make The Hall Of Fame?
I first looked at where he ranked all time in RSAA. That stat is from the Lee Sinins Complete Baseball Encyclopedia. It is "RSAA--Runs saved against average. It's the amount of runs that a pitcher saved vs. what an average pitcher would have allowed," including park adjustments. Pettitte now has 204 RSAA. That ranks him 77th all-time. Seems like too low of a rank to make the Hall. But he is 18th among lefites. Maybe left-handed pitchers have a tougher time than righties, so maybe the bar should be a little lower for them. It is not anyone's fault if they are left-handed. They could not have simply worked hard to become a righty. Of course, it also is the case that lefties simply have less value since there are many more right-handed batters. And maybe the Hall has to recognize how much value a pitcher had. But I will continue to show where Pettitte ranks among lefties.
Next I found the RSAA per IP for all pitchers with 2000+ career IP. Pettitte had .0697 (or . 63 runs per 9 IP). That was good enough for 58th. But among lefties, he was 13th. Then I found each pitcher's expected winning percentage using the Bill James pythagorean formula and assumed a league average of 4.5 runs per game. Each pitcher was given a number of games equal to his IP/9. That was multiplied by the expected winning percentage to get projected wins. I then subtracted from that the number of wins a replacement pitcher would have won. For that, I assumed a .400 winning pct. This process predicted that Pettitte would win 186.8 games while the replacement would win 130.06. So that gives him 56.74 WARP or wins above replacement pitcher. He ranks 87th in this WARP measure but is 20th among lefties.
But runs saved is partly determined by the fielders. So I created simple fielding independent ERA. I looked at all all pitchers with 2000+ career IP and used the following stats, all relative to the league average: ERA, HR, SO and BB. 100 is average. A number over 100 means better than average. I ran a regression with ERA as the dependent variable and the others as the independent variables. Here is the equation
Here are Pettitte's numbers:
So, for example, he gave up 44% fewer HRs than the average pitcher (this comes from Lee Sinins Complete Baseball Encyclopedia). Plugging these numbers into the equation, Pettitte gets 116.85, meaning his projected ERA based on fielding independent stats is 16.85% better than the league average. But his actual ERA is 17% better, so he just happens to project well. Anwyay, he ranks 69th overall but is 20th among lefties.
I also computed a WARP using this predicted ERA in the manner described above. Pettitte ranks 89th while being 21st among lefties with 57.62.
The biggest think in his favor is ranking 13th in RSAA/IP for lefties. But some of his other ranks are pretty low. I think the Hall of Fame has about 219 players, of whom 71 are pitcers or 32.4%. If a team has 25 players and pitchers are 40% of the team, then the Hall should have pitchers (about 87). But if all the position players are deserving (not likely, but I will play along anyway), then about 38 more pitchers need to be in (109/257 is about .4). Only 15 of the pitchers were lefties and Pettitte does rank fairly high among lefties. And if there should be 109 pitchers, he seems to be in the top 109 all-time. Even if there should be 87, even his worst rank that I found is close to that. Of course, all of this assumes that there are no undeserving players or pitchers in right now.
A couple of other things. I thought maybe Pettitte got an advantage pitching at Yankee stadium above the normal park adjustments since he is a lefty and might face alot of righties there where they have a harder time hitting HRs. But from Retrosheet, he gave up a HR% (based on batters faced) at home of 1.94%. On the road it was 2.01%. That does not seem to out of the ordinary. But his HR% (based on ABs) vs. righties has been 2.18% while vs. lefties it has been 2.18% as well. It seems like it should be higher against righties because over the last three years in MLB left-handed pitchers have allowed a HR% of about .5 percentage points higher against right-handed batters. That points to him getting an advantage from Yankee Stadium, but then his home HR% does not seem to give him much of an edge. So I don't know what to conclude from that.
I also once created what I called the Pitcher's Homerun/Walk Rating. It combined a pitcher's ability to prevent both HRs and BBs into one index rating. Pettitte was 23rd among pitchers with 2000+ IP from 1920-2006. Now it looks like he has slipped to 32nd. But that is out of 277 pitchers. Pretty darn good.
2 comments:
- David Pinto said...
How much should we adjust Pettitte's walk rate for his extraordinary ability to pick runners off base and induce double plays. Andy's WHIP underestimates his ability since he was so good at removing base runners.
- November 11, 2009 at 4:44 PM
- Cyril Morong said...
Thanks for dropping by and commenting. Great questions that I probably don't have the answers for. Are there any stats out there on pick offs and DPs, especially relative to league average? His RSAA would be affected by such an abililty (and recall he ranks 13th among lefties in RSAA/IP). Retrosheet has GDPs but I guess it would take some time to compare that to the league average. Then you would have to determine the number of opportunities he had.
I did find in one study that he did give up fewer runs than expected based on OBP, SLG, SO rate and handedness. His ERA was about .08 lower than predicted. That study is at
If he was getting alot of benefit from pickoffs and DPs, it is not showing up.
So far in his career, his actual ERA is .06 lower than his component ERA, according to Bill James. That only takes into account hits, HRs, BBs and HBP. Maybe these other things you mention could be the difference.
But I did a study on component era which is at
If I use the formula from that, which is
ERA = .427 + .881*CERA + .1188*SO/IP - .0986*DUM(for LHP)
on Pettitte, it predicts he would have a 3.91 ERA, which is what he does have. Being a lefty might help on the DPs since you face more righties. And a lower strikeout rate means more chances for DPs. He has been just about average at that. So is his DP ability due to inducing groundballs or lack of strikeouts (maybe a combo)? I don't know, but it appears he has the ERA we would expect based on the normal stats. But there could still be other things going on.
- November 11, 2009 at 5:57 PM


text:
Find a Park
View Statewide Map
2 Parks Found
Mike Roess Gold Head Branch State Park
Gold Head is located on rolling sandhills on the North Central Ridge of Florida with one of the few remaining examples of an old growth stand of longleaf pines. A steep head ravine with seepage springs forms Gold Head Branch and bisects the park. Marshes, lakes and scrub provide habitat for a wide variety of wildlife.
6239 State Road 21
Keystone Heights FL 32656
Wekiwa Springs State Park
With emerald springs feeding the Wekiwa River and lush tropical hammocks, this unique park just minutes from downtown Orlando is perfect for observing abundant wildlife or cooling off on a summer day. Miles of trails beg to be explored on foot, bike or horseback, and canoes and kayaks are available on-site.
1800 Wekiwa Cir.
Apopka FL 32712


text:
With veneer or a thin plywood deck you could use lighter foam, especially in the middle.
1/8" divinycell is pretty standard for bomber decks over 2#/ft^3 foam, for the whole board to be stronger 2.5# foam.
If you want to push your evident expertise with machine-cut, hand finished boards to the next level, why not go with your usual cut blank and add d-cell composite deck, box insert and hull?
You could get super rigidity and strength if you, for example, laid a carbon patch both under and over the d-cell from rear to front foot positions, with a similar approach on the bottom.
And still use 2# foam.
Or for a quicker build, depending on your hand shaping preferences, the 3 layers of d-cell would be built like the transom of a speedboat, very strong. And stiff if not carved away into deep concaves top or bottom.