1
0
mirror of https://github.com/MariaDB/server.git synced 2025-11-10 23:02:54 +03:00
Files
mariadb/mysql-test/t
unknown b920ab261e 4 small items in this:
- when we don't have in_addr_t, use uint32.
- a forgotten initialization of slave_proxy_id in sql/log_event.cc (was not really "forgot", was
"we needn't init it there", but there was one case where we needed...).
- made slave_proxy_id always meaningful in THD and Log_event, so we can
rely more on it (no need to test if it's meaningful). THD::slave_proxy_id
is equal to THD::thread_id except for the slave SQL thread.
- clean up the slave's temporary table (i.e. free their memory) when slave
server shuts down.


extra/resolveip.c:
  removed #define as it is simpler to put it in my_net.h
  (because we need the #define elsewhere)
include/my_net.h:
  When in_addr_t is not defined, use uint32.
libmysql/libmysql.c:
  using in_addr_t is more generic.
libmysql/manager.c:
  using in_addr_t is more generic.
mysql-test/t/rpl_chain_temp_table.test:
  comments
sql/log_event.cc:
  * Had forgot to initialize slave_proxy_id in the event constructor (char* buf...).
  Initializing is in fact only needed for Create_file_log_event, because
  it uses slave_proxy_id even if it does not write an event to the binlog
  (it uses slave_proxy_id to write it to SQL-LOAD.info).
  * When we write events we now always write slave_proxy_id, which is now always
  meaningful (as thd->slave_proxy_id is now always meaningful, see change in
  sql_class.cc).
sql/mini_client.cc:
  in_addr_t is more generic.
sql/slave.cc:
  A RELAY_LOG_INFO method to free the slave's temporary tables from memory
  at slave's server shutdown.
  It is called by end_slave(), which is called by close_connections(),
  which is called when the server terminates
  (close_connections() is just before clean_up(); putting the call in 
  clean_up() was buggy, as active_mi is already deleted by close_connections().
sql/slave.h:
  new method
sql/sql_class.cc:
  By default we set THD::slave_proxy_id to THD::thread_id,
  so THD::slave_proxy_id is always meaningful (not 0).
  It's always the same as the thread id except for the slave
  SQL thread.
2003-10-31 23:20:23 +01:00
..
2003-07-03 20:57:51 +05:00
2003-03-13 13:44:03 +01:00
2003-02-03 09:17:47 +01:00
2002-12-26 15:55:22 +02:00
2002-03-13 17:20:17 +00:00
2001-06-12 17:13:52 +03:00
2001-10-08 05:36:35 +03:00
2002-02-13 22:37:19 +02:00
2003-07-09 00:55:07 +03:00
2003-06-01 23:40:01 +03:00
2001-11-20 17:58:00 +01:00
2001-04-17 21:30:02 +02:00
2002-05-17 10:50:57 +03:00
2001-12-13 15:53:18 +02:00
2003-04-15 22:04:16 +03:00
2003-07-03 16:48:47 +05:00
2003-07-10 15:27:02 +05:00
2003-07-03 23:24:23 +05:00
2003-08-22 18:43:46 +03:00
2003-06-19 14:02:19 +05:00
2001-11-30 22:09:44 -07:00
2003-09-09 20:06:50 +03:00
2003-07-09 22:33:26 +03:00
2003-07-01 13:29:55 +03:00
2000-12-29 16:06:10 +02:00
2001-10-24 11:52:19 -06:00
2003-08-20 15:33:21 +03:00
2003-09-24 23:25:58 +04:00
2001-09-27 23:05:54 -06:00
2001-08-18 10:49:00 +03:00
2003-08-20 16:25:44 +03:00
2001-10-08 07:24:04 +03:00
2003-05-14 01:27:26 +03:00
2003-05-14 01:27:26 +03:00
2001-03-25 01:02:26 +02:00
2001-03-25 01:02:26 +02:00
2003-01-28 08:38:28 +02:00
2003-01-28 08:38:28 +02:00
2003-04-26 21:10:13 +03:00
2003-09-25 00:14:46 +02:00
2002-09-11 06:40:08 +03:00
2002-09-11 06:40:08 +03:00
2003-06-15 12:01:51 +02:00
2003-06-15 12:01:51 +02:00
2003-08-04 10:59:44 +02:00
2002-08-24 02:10:49 +03:00
2001-12-12 18:55:33 -07:00
2003-07-03 10:42:13 +05:00
2001-03-25 01:02:26 +02:00
2001-03-25 01:02:26 +02:00
2001-03-25 01:02:26 +02:00
2001-03-25 01:02:26 +02:00
2001-03-25 01:02:26 +02:00
2003-06-25 17:15:33 +05:00
2003-09-16 20:28:29 +04:00
2002-12-05 03:52:53 +02:00
2002-05-27 23:52:21 +03:00
2001-06-28 15:24:28 +03:00
2003-08-20 16:25:44 +03:00
2003-05-14 01:27:26 +03:00

The file is empty.