into  ramayana.hindu.god:/home/tsmith/m/bk/maint/51

into  ramayana.hindu.god:/home/tsmith/m/bk/maint/51

into  ramayana.hindu.god:/home/tsmith/m/bk/maint/51

into  ramayana.hindu.god:/home/tsmith/m/bk/maint/50

  
Initialize thd->variables.pseudo_thread_id when a new embedded
thd is created.

into  ramayana.hindu.god:/home/tsmith/m/bk/51-target22-X

Update some tests in the "parts" suite, so they're skipped if the
requisite plugins are not present in the mysqld.

Bug #30316: Some "parts" tests fail because the server uses "--secure-file-priv"
Bug #30341: Test suite "parts" needs to be adapted to the new rules disallowing many functio
Bug #30408: Suite "parts" needs bug numbers updated
Bug #30411: Suite "parts" needs bug numbers updated: ER_UNIQUE_KEY_NEED_ALL_FIELDS_IN_PF
Bug #30576: part_supported_sql_func_innodb.test tries to LOAD DATA outside of var dir
Bug #30581: partition_value tests use disallowed CAST() function

Included are some general fixes to allow the "parts" test suite to be run
successfully.  This includes disabling a few tests or parts of tests,
cleaning up the test cases and their results, etc.  Basically, these tests
have not been run for some time, and had suffered some bit rot.

The bugs were fixed as a single changeset, because in some ways they depend
on each other.  I couldn't be sure I'd updated all the error codes (for
bugs 30408 and 30411) without also adapting to the new allowed functions
rules (bug 30341), and vice versa.

into  bk-internal.mysql.com:/data0/bk/mysql-5.1-arch

A local variable may be used uninitialized in 
ha_partition::get_auto_increment().  Initialize it properly.

into  whalegate.ndb.mysql.com:/home/tomas/mysql-5.1-target-5.1.22

into  magare.gmz:/home/kgeorge/mysql/work/mysql-5.1-target-5.1.22-joro

re-pushing for 5.1.22.

into  trift2.:/MySQL/M51/target-5.1.22

into  trift2.:/MySQL/M51/target-5.1.22

 - Set sql_mode to default when creating system tables

1) "test_db.sql" is a plaintext file, no binary;
2) do not try to strip the binaries, it will not work.

into  whalegate.ndb.mysql.com:/home/tomas/mysql-5.1-target-5.1.22

into  pippilotta.erinye.com:/shared/home/df/mysql/build/mysql-5.1-build

  
MySQL replicates the time zone only when operations that involve
it are performed. This is controlled by a flag. But this flag
is set only on successful operation.
The flag must be set also when there is an error that involves
a timezone (so the master would replicate the error to the slaves).

into  pilot.(none):/data/msvensson/mysql/mysql-5.1-new-maint

 - "mysql" and "mysqlcheck" should not read defaults file

 - Update result file to include these "misleading errors", better to 
run mysql_upgrade with them than not at all.

into  mysql.com:/data0/mysqldev/my/build-200708231546-5.0.48/mysql-5.0-release

 - Change to use '' to quote a string inside another string

  
  A test case was waiting for a fixed number of seconds for a specific 
  state of the slave IO thread to take place.
  Fixed by waiting in a loop for that specific thread state instead 
  (or timeout).

 - Remove disabling of mysql_upgrade

keep_files_on_create made a startup option

into  pilot.(none):/data/msvensson/mysql/mysql-5.1-new-maint

 - Chop off .libs/ part of path if running in non installed builddir
   using libtool

Bug #16979: AUTO_INC lock in InnoDB works a table level lock
  Add a table level counter that tracks the number of AUTOINC locks that are
  pending and/or granted on a table. We peek at this value to determine whether
  a transaction doing a simple INSERT in innodb_autoinc_lock_mode = 1, needs to
  acquire the AUTOINC lock or not. This change is related to Bug# 16979.
Bug #27950: Duplicate entry error in auto-inc after mysqld restart
  We check whether the AUTOINC sub-system has been initialized (first) by
  holding the AUTOINC mutex and if initialization is required then we
  initialize using our normal procedure.

into  a88-113-38-195.elisa-laajakaista.fi:/home/my/bk/mysql-5.1-marvel

into  a88-113-38-195.elisa-laajakaista.fi:/home/my/bk/mysql-5.1-marvel

into  a88-113-38-195.elisa-laajakaista.fi:/home/my/bk/mysql-5.0-marvel

Bug #16979: AUTO_INC lock in InnoDB works a table level lock
  - this is a major change in InnoDB auto-inc handling.
Bug #27950: Duplicate entry error in auto-inc after mysqld restart
  - Init AUTOINC from delete_row().
Bug #28781: InnoDB increments auto-increment value incorrectly with ON DUPLICATE KEY UPDATE
  - Use value specified by MySQL, in update_row().

into  trift2.:/MySQL/M51/push-5.1