Re: bug report
Hello. Please, could you send a more detailed report. Include information about MySQL and operating system versions. See: http://dev.mysql.com/doc/mysql/en/Bug_reports.html You may want to force a recovery. See: http://dev.mysql.com/doc/mysql/en/forcing-recovery.html Pierre-Henry Perret [EMAIL PROTECTED] wrote: When starting mysqld, I got the err message (in file) 051005 05:26:47 mysqld started 051005 5:26:47 InnoDB: Database was not shut down normally. InnoDB: Starting recovery from log files... InnoDB: Starting log scan based on checkpoint at InnoDB: log sequence number 0 43902 InnoDB: Doing recovery: scanned up to log sequence number 0 43902 051005 5:26:47 InnoDB: Error: trying to access a stray pointer 88b8fff8 InnoDB: buf pool start is at 8b8, end at 938 InnoDB: Probable reason is database corruption or memory InnoDB: corruption. If this happens in an InnoDB database recovery, InnoDB: you can look from section 6.1 at http://www.innodb.com/ibman.html InnoDB: how to force recovery. 051005 5:26:47 InnoDB: Assertion failure in thread 137490432 in file ../../innobase/include/buf0buf.ic line 261 InnoDB: We intentionally generate a memory trap. InnoDB: Send a detailed bug report to [EMAIL PROTECTED] mysqld got signal 11; This could be because you hit a bug. It is also possible that this binary or one of the libraries it was linked against is corrupt, improperly built, or misconfigured. This error can also be caused by malfunctioning hardware. We will try our best to scrape up some info that will hopefully help diagnose the problem, but since we have already crashed, something is definitely wrong and this may fail. key_buffer_size=268435456 read_buffer_size=1044480 Fatal signal 11 while backtracing 051005 05:26:47 mysqld ended -- For technical support contracts, goto https://order.mysql.com/?ref=ensita This email is sponsored by Ensita.NET http://www.ensita.net/ __ ___ ___ __ / |/ /_ __/ __/ __ \/ /Gleb Paharenko / /|_/ / // /\ \/ /_/ / /__ [EMAIL PROTECTED] /_/ /_/\_, /___/\___\_\___/ MySQL AB / Ensita.NET ___/ www.mysql.com -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: Bug-Report: mysqld 4.1.3 crashes on startup
Hi! On Aug 01, Helge Jung wrote: Description: When I start up my fresh compiled mysqld it crashes immediately, the error log file says: It was reported just a few hours ago at bugs.mysql.com (which is the recommended way to report bugs, by the way :) you may follow the progress using http://bugs.mysql.com/4844 Regards, Sergei -- __ ___ ___ __ / |/ /_ __/ __/ __ \/ / Sergei Golubchik [EMAIL PROTECTED] / /|_/ / // /\ \/ /_/ / /__ MySQL AB, Senior Software Developer /_/ /_/\_, /___/\___\_\___/ Osnabrueck, Germany ___/ www.mysql.com -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: bug report
Eric, Please read http://www.mysql.com/doc/en/Using_stack_trace.html and follow instructions on how to resolve the stack trace. Resolved stack trace is much more helpful in diagnosing the problem, so please do resolve it please use the resolve_stack_dump program in combination with the mysqld.sym which are shipped with the MySQL distro. You may have table corruption. Run CHECK TABLE on your tables. If it prints something to the .err log, please send the output to me. If you have problems starting up mysqld or dumping your tables, see http://www.innodb.com/ibman.html#Forcing_recovery for help. What does uname -a say about your Linux kernel? You should upgrade to a kernel = 2.4.20 if not yet running one. Earlier Linux kernels seem to cause corruption in many computers. 030905 20:06:18 InnoDB: Warning: using a partial-field key prefix in search Any idea what SQL query might be causing the above warning? Do you use LIKE 'abcd%' ? Best regards, Heikki Tuuri Innobase Oy http://www.innodb.com Foreign keys, transactions, and row level locking for MySQL InnoDB Hot Backup - a hot backup tool for MySQL Order MySQL technical support from https://order.mysql.com/ - Original Message - From: Eric Aubourg [EMAIL PROTECTED] Newsgroups: mailing.database.myodbc Sent: Tuesday, September 09, 2003 2:37 AM Subject: bug report 030905 10:39:38 mysqld started 030905 10:39:40 InnoDB: Database was not shut down normally. InnoDB: Starting recovery from log files... InnoDB: Starting log scan based on checkpoint at InnoDB: log sequence number 2 3128426578 InnoDB: Doing recovery: scanned up to log sequence number 2 3128426578 InnoDB: Last MySQL binlog file position 0 762953481, file name ./makiki-bin.016 030905 10:39:40 InnoDB: Flushing modified pages from the buffer pool... 030905 10:39:40 InnoDB: Started /data/upena/soft/mysql/bin/mysqld: ready for connections. Version: '4.0.14-max-log' socket: '/tmp/mysql.sock' port: 3306 030905 20:06:18 InnoDB: Warning: using a partial-field key prefix in search A mysqld process already exists at Sun Sep 7 00:26:58 HST 2003 A mysqld process already exists at Sun Sep 7 00:27:59 HST 2003 A mysqld process already exists at Sun Sep 7 00:28:45 HST 2003 InnoDB: Error: trying to access page number 3422338945 in space 0 InnoDB: which is outside the tablespace bounds. InnoDB: Byte offset 0, len 16384, i/o type 10 030908 11:27:35 InnoDB: Assertion failure in thread 370700 in file fil0fil.c line 1176 InnoDB: Failing assertion: 0 InnoDB: We intentionally generate a memory trap. InnoDB: Send a detailed bug report to [EMAIL PROTECTED] mysqld got signal 11; This could be because you hit a bug. It is also possible that this binary or one of the libraries it was linked against is corrupt, improperly built, or misconfigured. This error can also be caused by malfunctioning hardware. We will try our best to scrape up some info that will hopefully help diagnose the problem, but since we have already crashed, something is definitely wrong and this may fail. key_buffer_size=16777216 read_buffer_size=131072 max_used_connections=4 max_connections=100 threads_connected=1 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 80383 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. thd=0x884f9d8 Attempting backtrace. You can use the following information to find out where mysqld died. If you see no messages after this, something went terribly wrong... Cannot determine thread, fp=0xbe3faf68, backtrace may not be correct. Stack range sanity check OK, backtrace follows: 0x80d9a90 0x40039a24 0x82ccda7 0x82a0809 0x82a0c55 0x82937b5 0x82c5e24 0x82c50e6 0x82730d3 0x828d7f5 0x8284dc0 0x8286e3f 0x821c398 0x813b40e 0x8140e6e 0x8143631 0x80e51cb 0x80e7fba 0x80e3483 0x80e2edd 0x80e26ce 0x40036e17 0x40191dda New value of fp=(nil) failed sanity check, terminating stack trace! Please read http://www.mysql.com/doc/en/Using_stack_trace.html and follow instructions on how to resolve the stack trace. Resolved stack trace is much more helpful in diagnosing the problem, so please do resolve it -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED] -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: Bug Report
Nils Wisiol wrote: hi There is a Bug in the InstallWizard Engine. If I install mysql on my winxp professional system WITHOUT sp1, install shield say goodbye when the setup is almost ready. i've tried custom and completly installation. maybe its a failied download. the mysql version is: mysql-4.0.14b-win.zip Are you allowed to patch the box to SP1a? I am running XP SP1a with MDAC 2.7 latest fix. Should work. On the MySQL download site there was a note not use tools like GetRight (before the GeoIP days). Did you try to reget that file? Try to download it into a different dir or delete the possibly corrupted archive first. HTH, Jakob Doelling ^-- To Unix or not to Unix. That is the question whether 'tis nobler in the mind to suffer slings and arrows of vast documentation or to take arms against a sea of buggy OS and by raping the support lines end then? ; Contact: \/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/ \/Jakob Dölling \/EMail: mailto:[EMAIL PROTECTED]/ Treuerzipfel 13 ICQ #: 47326203 /\D-38678 Clausthal /\SMS #: +49-82668-8918663/\ /\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\ /\Webmaster of http://www.bank-ic.de/ /\ \/\/ -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: Bug report: LIMIT of 1000 rows returned on SELECT (2nd try)
Johnson, David C [EMAIL PROTECTED] wrote: From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: LIMIT of 1000 rows returned on SELECT (2nd try) Description: When doing a query on a table with more than 1000 rows, the SELECT * query returns only the first 1000 rows. Do you use SQL_SELECT_LIMIT session variable? -- For technical support contracts, goto https://order.mysql.com/?ref=ensita This email is sponsored by Ensita.net http://www.ensita.net/ __ ___ ___ __ / |/ /_ __/ __/ __ \/ /Victoria Reznichenko / /|_/ / // /\ \/ /_/ / /__ [EMAIL PROTECTED] /_/ /_/\_, /___/\___\_\___/ MySQL AB / Ensita.net ___/ www.mysql.com -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: Bug Report, timestamp columns
On 26 Mar 2003 at 9:23, Alejandro Paz wrote: As you can see the colum `b' is updated, too. Note, you have to insert a delay of almost 1 second between the first select and the update, because the column `b' takes the current time!. Only happens with timestamp columns not with datetime ones. You seem to be surprised that b is updated. Have you read the documentation for TIMESTAMP? | The TIMESTAMP column type provides a type that you can use to | automatically mark INSERT or UPDATE operations with the current | date and time. If you have multiple TIMESTAMP columns, only the | first one is updated automatically. [explanation continues] http://www.mysql.com/doc/en/DATETIME.html The strange thing about your example is not the updating of b but the odd value assigned to c, which seems to be different from NOW(), but you say nothing about that. -- Keith C. Ivey [EMAIL PROTECTED] Tobacco Documents Online http://tobaccodocuments.org Phone 202-667-6653 -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: Bug Report: mysql-3.23.38-win
Keith, please upgrade to 3.23.55. Your MySQL version is very old. Best regards, Heikki Tuuri Innobase Oy --- InnoDB - transactions, row level locking, and foreign key support for MySQL See http://www.innodb.com, download MySQL-Max from http://www.mysql.com sql query - Original Message - From: Keith Engelhardt [EMAIL PROTECTED] Newsgroups: mailing.database.mysql Sent: Monday, March 03, 2003 1:52 AM Subject: Bug Report: mysql-3.23.38-win I am attempting to get mysql-3.23.38-win on a Windows 98 SE box. The mysql-3.23.38-win.zip install wizard allowed me to install to D:\MYSQL I have tweaked the my.cfg file as follows: # Example mysql config file. # Copy this file to c:\my.cnf to set global options # # One can use all long options that the program supports. # Run the program with --help to get a list of available options # This will be passed to all mysql clients [client] #password=my_password port=3306 #socket=MySQL # Here is entries for some specific programs # The following values assume you have at least 32M ram # The MySQL server [mysqld] port=3306 #socket=MySQL skip-locking default-character-set=latin1 set-variable = key_buffer=16M set-variable = max_allowed_packet=1M set-variable = thread_stack=128K set-variable = flush_time=1800 # Uncomment the following row if you move the MySQL distribution to another # location #basedir = [mysqldump] quick set-variable = max_allowed_packet=16M [mysql] no-auto-rehash basedir = d:/mysql datadir= d:/mysql/data [mysqld] innodb_data_file_path = ibdata:30M innodb_data_home_dir=\mysql\data [isamchk] set-variable= key=16M [client_fltk] #help_file= c:\mysql\sql_client\MySQL.help #client_file= c:\mysql\MySQL.options history_length=20 database = test queries_root= d:\mysql\queries last_database_file= d:\mysql\lastdb -- When mySQL is launched via D:\mysql\bin\mysqld.exe --basedir D:\mysql I get the following: Innobase: Assertion failure in thread 4225946759 in file M:\mysql-3.23\innobase os\os0file.c line 187 Innobase: we intentionally generate a memory trap. Innobase: Send a bug report to [EMAIL PROTECTED] 030302 18:45:05 D:\MYSQL\BIN\MYSQLD.EXE: Got signal 11. Aborting! 030302 18:45:05 Aborting InnoDB: Warning: shutting down not properly started database 030302 18:45:05 D:\MYSQL\BIN\MYSQLD.EXE: Shutdown Complete Sincerely, Keith E. [EMAIL PROTECTED] - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
Re: Bug Report: Restrictions on index naming
On Wed, Jan 15, 2003 at 11:44:24AM +1100, Daniel Kasak wrote: Hi all, I recently had to restore from a backup and discovered that mysql didn't want to re-create a table which had the minus symbol (-) in it, eg Yeah, you need to quote such names now. Upgrade your version of mysqldump and the problem will go away, I believe. -- Jeremy D. Zawodny | Perl, Web, MySQL, Linux Magazine, Yahoo! [EMAIL PROTECTED] | http://jeremy.zawodny.com/ MySQL 3.23.51: up 30 days, processed 1,013,700,735 queries (379/sec. avg) - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
RE: Bug Report: Restrictions on index naming
MySQLCC probably uses the backtick (`) to escape stuff so it issued UNIQUE KEY `IDX_Postcode-Location` (Postcode,Location) and not UNIQUE KEY IDX_Postcode-Location (Postcode,Location) It has been mentioned on the list a few times in the last couple months that if you escape strings containing hyphens with a backtick they work. That doesn't mean it is a good idea to use them. You can try running your dump with the quote-names flag, maybe. I haven't tried it to see what the output is. Run mysqldump's help to see what all the flags are and what they mean. -Original Message- Hi all, I recently had to restore from a backup and discovered that mysql didn't want to re-create a table which had the minus symbol (-) in it, eg DROP TABLE IF EXISTS Postcodes; CREATE TABLE Postcodes ( DanPK mediumint(8) unsigned NOT NULL auto_increment, MyStamp timestamp(14) NOT NULL, Postcode smallint(2) NOT NULL default '0', Location varchar(100) default NULL, State char(3) default NULL, RegionID mediumint(8) unsigned NOT NULL default '0', PRIMARY KEY (DanPK), UNIQUE KEY IDX_Postcode-Location (Postcode,Location) ) TYPE=MyISAM; I had added the index with MySQLCC (I think) and the database had been working fine as far as I could tell (minus the crash this morning). The table def is from mysqldump --opt, which I use each night, in combination with the --log-update option to assist in disaster recovery. When I tried to restore from the backup (mysqldump output) it gave me a syntax error around the -Location bit. But it _did_ let me create the index like this before. Thinking about it more, I probably shouldn't have used a minus. I can see why that would be reserved. Any chance of enforcing that in alter table commands (which I would have used to get the index there), or is it considered too expensive to do these kinds of checks? - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
Re: bug report
Adam, in your earlier message you quoted 3 log files, but below in the printout it says 2 log files. Best to do SHOW VARIABLES; and check from the current directory innodb_log_group_home_dir how many ib_logfiles there really are. 030107 06:42:58 mysqld started /usr/local/mysql/bin/mysqld: unrecognized option `--innodb_log_files_in_group=3' /usr/local/mysql/bin/mysqld: unrecognized option `--innodb log files in group=2' We have not touched /etc/my.cnf and have restarted the server many times. I had to change it to: set-variable=innodb log files in group=2 to get it to restart (a suggestion by Heikki Tuuri) If I try the wrong syntax, I get: heikki@hundin:~/mysql-max-3.23.53a-pc-linux-gnu-i686/bin mysqld mysqld: unrecognized option `--innodb_log_files_in_group=3' mysqld Ver 3.23.53a-max for pc-linux-gnu on i686 I resolved the stack dump: 0x806bdc5 handle_segfault__Fi + 425 0x8247a78 pthread_sighandler + 184 0x815450c btr_search_info_update_slow + 1072 0x813fe5e btr_cur_search_to_nth_level + 3178 0x811586b row_sel_get_clust_rec_for_mysql + 99 0x8118704 row_search_for_mysql + 6836 0x80b6802 general_fetch__11ha_innobasePcUiUi + 322 0x80b68d0 index_next_same__11ha_innobasePcPCcUi + 40 0x809142d join_read_next__FP14st_read_record + 53 0x8090b89 sub_select__FP4JOINP13st_join_tableb + 337 0x8090843 do_select__FP4JOINPt4List1Z4ItemP8st_tableP9Procedure + 407 0x8089688 mysql_select__FP3THDP13st_table_listRt4List1Z4ItemP4ItemP8st_orderT4T3 T4UiP13select_result + 5592 0x8072320 mysql_execute_command__Fv + 812 0x80755a8 mysql_parse__FP3THDPcUi + 72 0x80714c4 do_command__FP3THD + 1316 0x8070997 handle_one_connection__FPv + 655 It is possible that the bug is one which is fixed in the upcoming 3.23.55 and in 4.0.8. It could also be memory corruption. What is your Linux kernel version? It is best that you run CHECK TABLE on some tables. MySQL/InnoDB-3.23.55, February x, 2003 ... a.. Fixed a bug: an assertion in btr0sea.c, in function btr_search_info_update_slow could theoretically fail in a race of 3 threads. Regards, Heikki Innobase Oy sql query Subject: bug report From: Adam Gillespie Date: Tue, 7 Jan 2003 09:29:59 -0800 Our db server crashed and this was in the log. One strange thing was that when I went to restart, the error log gave me this line: /usr/local/mysql/bin/mysqld: unrecognized option `--innodb log files in group=2' We have not touched /etc/my.cnf and have restarted the server many times. I had to change it to: set-variable=innodb log files in group=2 to get it to restart (a suggestion by Heikki Tuuri) 030107 4:05:57 InnoDB: Assertion failure in thread 11497484 in file btr0sea.c line 456 InnoDB: We intentionally generate a memory trap. InnoDB: Send a detailed bug report to [EMAIL PROTECTED] mysqld got signal 11; This could be because you hit a bug. It is also possible that this binary or one of the libraries it was linked agaist is corrupt, improperly built, or misconfigured. This error can also be caused by malfunctioning hardware. We will try our best to scrape up some info that will hopefully help diagnose the problem, but since we have already crashed, something is definitely wrong and this may fail key buffer size=134213632 record buffer=2093056 sort buffer=2097144 max used connections=65 max connections=300 threads connected=2 It is possible that mysqld could use up to key buffer size + (record buffer + sort buffer)*max connections = 1358665 K bytes of memory Hope that's ok, if not, decrease some variables in the equation Attempting backtrace. You can use the following information to find out where mysqld died. If you see no messages after this, something went terribly wrong... Stack range sanity check OK, backtrace follows: 0x806bdc5 0x8247a78 0x815450c 0x813fe5e 0x811586b 0x8118704 0x80b6802 0x80b68d0 0x809142d 0x8090b89 0x8090843 0x8089688 0x8072320 0x80755a8 0x80714c4 0x8070997 Stack trace seems successful - bottom reached Please read http://www.mysql.com/doc/U/s/Using stack trace.html and follow instructions on how to resolve the stack trace. Res olved stack trace is much more helpful in diagnosing the problem, so please do resolve it Trying to get some variables. Some pointers may be invalid and cause the dump to abort... thd-query at 0xa9935960 is invalid pointer thd-thread id=4307634 Successfully dumped variables, if you ran with --log, take a look at the details of what thread 4307634 did to cause the crash. In some cases of really bad corruption, the values shown above may be invalid The manual page at http://www.mysql.com/doc/C/r/Crashing.html contains information that should help you find out what is causing the crash Number of processes running now: 0 030107 04:05:58 mysqld restarted /usr/local/mysql/bin/mysqld: unrecognized option `--innodb log files in group=2' /usr/local/mysql/bin/mysqld Ver 3.23.53a-max for pc-linux-gnu on i686 Copyright (C) 2000 MySQL AB, by
Re: Bug report: UNIQUE KEY and DESCRIBE TABLE
Matt,
I am forwarding this to MySQL developers.
Problem description:
MySQL does not return key information about any column after the first
in a unique multi-column key. Also, the MUL flag seems to indicate
that the key is non-unique, when in fact it is.
This output format of DESCRIBE TABLE has been discussed before. It is not
easily understandable, though the above is what Monty intended it to be.
I recommend using
SHOW CREATE TABLE tablename;
to look at a table structure. It contains the foreign key definitions and
all. DESCRIBE TABLE does not contain all information.
Regards,
Heikki
- Original Message -
From: Matt Solnit [EMAIL PROTECTED]
To: Heikki Tuuri [EMAIL PROTECTED]; [EMAIL PROTECTED]
Cc: Henry Bequet [EMAIL PROTECTED]
Sent: Saturday, December 28, 2002 2:44 AM
Subject: Bug report: UNIQUE KEY and DESCRIBE TABLE
===
Bug report -- MySQL v4.06, binary distribution
===
--
Machine specs:
--
Compaq Presario desktop
512 MB RAM
Windows XP Professional SP1
Problem description:
MySQL does not return key information about any column after the first
in a unique multi-column key. Also, the MUL flag seems to indicate
that the key is non-unique, when in fact it is.
There is an equivalent symptom in the MySQL C API. In the flags field
of the MYSQL_FIELD structure returned by mysql_fetch_field(), the
MULTIPLE_KEY_FLAG will only be present in the first column.
-
Test script:
-
mysqlUSE test
mysqlCREATE TABLE mytable (a INT NOT NULL, b INT NOT NULL, c INT NOT
NULL, d INT NOT NULL, PRIMARY KEY (a), UNIQUE KEY (b, c));
mysqlDESCRIBE TABLE mytable;
--
Results:
--
+---+-+--+-+-+---+
| Field | Type| Null | Key | Default | Extra |
+---+-+--+-+-+---+
| a | int(11) | | PRI | 0 | |
| b | int(11) | | MUL | 0 | |
| c | int(11) | | | 0 | |
| d | int(11) | | | 0 | |
+---+-+--+-+-+---+
C test program:
/***
Expected output (according to manual section 8.4.1):
Column `a`: primary=1, unique=0, multiple=0
Column `b`: primary=0, unique=1, multiple=0
Column `c`: primary=0, unique=1, multiple=0
Column `d`: primary=0, unique=0, multiple=0
Actual output:
Column `a`: primary=1, unique=0, multiple=0
Column `b`: primary=0, unique=0, multiple=1
Column `c`: primary=0, unique=0, multiple=0
Column `d`: primary=0, unique=0, multiple=0
***/
#include stdafx.h
#include winsock.h
#include mysql.h
#include stdarg.h
#include stdio.h
#include stdlib.h
MYSQL *db_connect(const char *dbname);
void db_disconnect(MYSQL *db);
void db_do_query(MYSQL *db, const char *query);
const char *server_groups[] = {
test_libmysqld_SERVER, embedded, server, NULL
};
int main(int argc, char* argv[])
{
MYSQL *one;
mysql_server_init(argc, argv, (char **)server_groups);
one = db_connect(test);
const char* query = SELECT * FROM mytable;
mysql_query(one, query);
MYSQL_RES* res = mysql_store_result(one);
int numFields = mysql_num_fields(res);
for (int i = 0; i numFields; i++)
{
MYSQL_FIELD* fld = mysql_fetch_field(res);
char* name = strdup(fld-name);
bool isPrimary = ((fld-flags PRI_KEY_FLAG) 0);
bool isUnique = ((fld-flags UNIQUE_KEY_FLAG) 0);
bool isMulti = ((fld-flags MULTIPLE_KEY_FLAG) 0);
printf(column `%s`: primary=%d, unique=%d, multiple=%d\n, name,
isPrimary, isUnique, isMulti);
}
mysql_close(one);
mysql_server_end();
return 0;
}
static void
die(MYSQL *db, char *fmt, ...)
{
va_list ap;
va_start(ap, fmt);
vfprintf(stderr, fmt, ap);
va_end(ap);
(void)putc('\n', stderr);
if (db)
db_disconnect(db);
exit(EXIT_FAILURE);
}
MYSQL *
db_connect(const char *dbname)
{
MYSQL *db = mysql_init(NULL);
if (!db)
die(db, mysql_init failed: no memory);
/*
* Notice that the client and server use separate group names.
* This is critical, because the server will not accept the
* client's options, and vice versa.
*/
mysql_options(db, MYSQL_READ_DEFAULT_GROUP, test_libmysqld_CLIENT);
if (!mysql_real_connect(db, NULL, NULL, NULL, dbname, 0, NULL, 0))
die(db, mysql_real_connect failed: %s, mysql_error(db));
return db;
}
void
db_disconnect(MYSQL *db)
{
mysql_close(db);
}
---
My contact information:
---
Matt Solnit [EMAIL PROTECTED]
-
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
http://lists.mysql.com/ (the list archive)
To request this thread,
Re: Bug report: UNIQUE KEY and DESCRIBE TABLE
At 16:44 -0800 12/27/02, Matt Solnit wrote: === Bug report -- MySQL v4.06, binary distribution === -- Machine specs: -- Compaq Presario desktop 512 MB RAM Windows XP Professional SP1 Problem description: MySQL does not return key information about any column after the first in a unique multi-column key. Also, the MUL flag seems to indicate that the key is non-unique, when in fact it is. 1) Use SHOW KEYS if you want better information about the indexes on a table. DESCRIBE (aka SHOW COLUMNS) reports some information about indexes, but that is not its primary purpose. 2) UNIQUE indexes can in fact hold non-unique values if any of the indexed columns can be NULL. (A UNIQUE index is allowed to store multiple NULL values.) But you are correct that the index in your particular table can *not* be non-unique, because neither of the indexed columns can be NULL. (A further manifestation of this problem is that UNIQUE indexes in BDB tables can *never* be non-unique, because BDB allows only one NULL in a UNIQUE index, in contrast to other table types.) There is an equivalent symptom in the MySQL C API. In the flags field of the MYSQL_FIELD structure returned by mysql_fetch_field(), the MULTIPLE_KEY_FLAG will only be present in the first column. - Test script: - mysqlUSE test mysqlCREATE TABLE mytable (a INT NOT NULL, b INT NOT NULL, c INT NOT NULL, d INT NOT NULL, PRIMARY KEY (a), UNIQUE KEY (b, c)); mysqlDESCRIBE TABLE mytable; -- Results: -- +---+-+--+-+-+---+ | Field | Type| Null | Key | Default | Extra | +---+-+--+-+-+---+ | a | int(11) | | PRI | 0 | | | b | int(11) | | MUL | 0 | | | c | int(11) | | | 0 | | | d | int(11) | | | 0 | | +---+-+--+-+-+---+ - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
Re: Bug Report
Christopher, - Original Message - From: Christopher Stephan [EMAIL PROTECTED] Newsgroups: mailing.database.mysql Sent: Saturday, December 21, 2002 6:00 PM Subject: Bug Report Hello, following problem occurs using MySql. Can you help me with that Error? this is memory corruption, possibly a memory overrun by the memory buffer which is being freed when the assertion fails. Can you repeat the crash? It would be very valuable to trace a memory corruption bug. I can send a special memory debug version of mysqld which makes it easier. I have now also added diagnostic code to this assertion in 4.0.7. What distro of MySQL-Max-4.0.6 you are using? Please do the following to resolve the stack dump: go to the directory where the MySQL binaries are and: shell gzip -d mysqld.sym.gz shell resolve_stack_dump mysqld.sym paste the stack dump here Now it should print a resolved stack dump. If it was a memory overrun, the stack dump would be very valuable. Regards, Heikki Innobase Oy sql query Betriebssystem: [ SuSE Linux 7.3 (i386) ] MySql Verision: MySql Max 4.0.6 OMEGA.ERR: 021221 14:24:21 InnoDB: Assertion failure in thread 16401 in file mem0pool.c line 491 InnoDB: We intentionally generate a memory trap. InnoDB: Send a detailed bug report to [EMAIL PROTECTED] InnoDB: Thread 10251 stopped in file row0mysql.c line 92 mysqld got signal 11; This could be because you hit a bug. It is also possible that this binary or one of the libraries it was linked against is corrupt, improperly built, or misconfigured. This error can also be caused by malfunctioning hardware. We will try our best to scrape up some info that will hopefully help diagnose the problem, but since we have already crashed, something is definitely wrong and this may fail. key_buffer_size=16777216 read_buffer_size=131072 sort_buffer_size=524280 max_used_connections=6 max_connections=100 threads_connected=7 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 80383 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. thd=0x87cea58 Attempting backtrace. You can use the following information to find out where mysqld died. If you see no messages after this, something went terribly wrong... Cannot determine thread, fp=0xbd9fe508, backtrace may not be correct. Stack range sanity check OK, backtrace follows: 0x80da95a 0x40040bc4 0x830e0e5 0x830cbd2 0x8222d0d 0x822784b 0x813ce03 0x813f9cf 0x810cb65 0x8106b39 0x81067e3 0x80ff7b0 0x810c099 0x80e69c6 0x80e8908 0x80e4123 0x80e9df2 0x80e32ff 0x4003df37 0x40199baa New value of fp=(nil) failed sanity check, terminating stack trace! Please read http://www.mysql.com/doc/U/s/Using_stack_trace.html and follow instructions on how to resolve the stack trace. Resolved stack trace is much more helpful in diagnosing the problem, so please do resolve it Trying to get some variables. Some pointers may be invalid and cause the dump to abort... thd-query at 0x87db350 = INSERT INTO xselected1 ( issueid, accesskey ) SELECT xissue.issueid, '1040477060015' FROM xissue INNER JOIN xstatus ON xissue.attributevalue = xstatus.statusid WHERE (((xissue.projectID)=26) AND (xissue.deleted 'on') AND ((xissue.attributeid=128) And ( ((xstatus.statusid)45) And ((xstatus.statusid)46) And ((xstatus.statusid)42) And ((xstatus.statusid)42) And ((xstatus.statusid)43) And ((xstatus.statusid)44) And ((xstatus.statusid)42) And ((xstatus.statusid)42) And ((xstatus.statusid)42) And ((xstatus.statusid)42) And ((xstatus.statusid)46) And ((xstatus.statusid)42) And ((xstatus.statusid)42) And ((xstatus.statusid)42) And ((xstatus.statusid)49) And ((xstatus.statusid)49) And ((xstatus.statusid)46) And ((xstatus.statusid)43) And ((xstatus.statusid)48) And ((xstatus.statusid)48) And ((xstatus.statusid)45) And ((xstatus.statusid)45)) Or (((xissue.attributeid)=128) And ((xstatus.name) Like'%closed%' GROUP BY xissue.issueid thd-thread_id=7 Successfully dumped variables, if you ran with --log, take a look at the details of what thread 7 did to cause the crash. In some cases of really bad corruption, the values shown above may be invalid. The manual page at http://www.mysql.com/doc/C/r/Crashing.html contains information that should help you find out what is causing the crash. Christopher Stephan [EMAIL PROTECTED] http://www.xudoo.com - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php - Before posting, please check: http://www.mysql.com/manual.php (the manual)
RE: Bug report: Embedded MySQL version 4.05a
Hi Paul! Thank you for the quick response. Indeed, we expect it to work otherwise. In our application, users are authenticated by the operating system, but we were hoping to use the built-in authorization of MySql instead of developing our own. Our strategy is to automatically add users to MySql as they are given to us by the OS and assign permissions to tables using these users. Does that seem reasonable? Thank you! Henry. -Original Message- From: Paul DuBois [mailto:[EMAIL PROTECTED]] Sent: Tuesday, December 10, 2002 9:09 PM To: Matt Solnit; Heikki Tuuri; [EMAIL PROTECTED] Cc: Henry Bequet Subject: Re: Bug report: Embedded MySQL version 4.05a At 15:39 -0800 12/10/02, Matt Solnit wrote: === Bug report -- MySQL v4.05a, binary distribution === -- Machine specs: -- Compaq Presario desktop Windows XP Professional SP1 .NET Framework SP2 Problem description: The security features of MySQL do not seem to work with Embedded MySQL. Instead, every user is given full permissions. Would you expect otherwise? If you have the embedded server linked into an application, it's expected that the application will have full control over the server and can do anything with any of its databases. - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
Re: Bug report: Embedded MySQL version 4.05a
At 15:39 -0800 12/10/02, Matt Solnit wrote: === Bug report -- MySQL v4.05a, binary distribution === -- Machine specs: -- Compaq Presario desktop Windows XP Professional SP1 .NET Framework SP2 Problem description: The security features of MySQL do not seem to work with Embedded MySQL. Instead, every user is given full permissions. Would you expect otherwise? If you have the embedded server linked into an application, it's expected that the application will have full control over the server and can do anything with any of its databases. - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
Re: Bug Report: Replication in 4.0.5beta
Michael, I was able to repeat the bug on Linux now. It seems to happen if I set max_binlog_size to 2M in the SLAVE. The relay binlog gets split into several 2 MB pieces. It does not happen always, but I have a randomized test which produces the error in 1 minute. I was not able to repeat the bug when I had not set the max binlog size in the slave, in which case I think it defaults to 1 GB. heikki@hundin:~/mysql-4.0/sql mysqld --defaults-file=/home/heikki/slavemy.cnf 021204 23:55:45 InnoDB: Started mysqld: ready for connections 021204 23:55:45 Slave I/O thread: connected to master 'slaveuser@hundin:3307', replication started in log 'FIRST' at position 4 021204 23:57:42 Error in Log_event::read_log_event(): 'Event too big', data_len =1447971143,event_type=115 021204 23:58:03 Slave SQL thread: I/O error reading event(errno: -1 cur_log-e rror: 12) 021204 23:58:03 Error reading relay log event: Aborting slave SQL thread becaus e of partial event read 021204 23:58:03 Could not parse log event entry, check the master for binlog co rruption This may also be a network problem, or just a bug in the master or slave code. 021204 23:58:03 Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with SLAVE START. We stopped at log 'binlog. 002' position 13659061 heikki@hundin:~/data ls -l total 51832 -rw-rw1 heikki users24086965 Dec 4 23:57 binlog.001 -rw-rw1 heikki users28925234 Dec 4 23:58 binlog.002 -rw-rw1 heikki users 26 Dec 4 23:57 binlog.index -rw-rw1 heikki users 5 Dec 4 23:55 hundin.pid drwxr-xr-x2 heikki users 619 Sep 5 20:51 mysql drwxr-xr-x2 heikki users 513 Dec 4 23:57 test heikki@hundin:~/data Also, I observed that if I do a big LOAD DATA INFILE when autocommit=1, then the master splits the master binlog into 2 MB pieces as I have instructed, and since I have set max packet size to 1M in both master and the slave, the slave complains: heikki@hundin:~/mysql-4.0/sql mysqld --defaults-file=/home/heikki/slavemy.cnf 021204 23:48:21 InnoDB: Started mysqld: ready for connections 021204 23:48:21 Slave I/O thread: connected to master 'slaveuser@hundin:3307', replication started in log 'FIRST' at position 4 021204 23:52:08 Error reading packet from server: log event entry exceeded max_ allowed_packet; Increase max_allowed_packet on master (server_errno=1236) 021204 23:52:08 Got fatal error 1236: 'log event entry exceeded max_allowed_pac ket; Increase max_allowed_packet on master' from master when reading data from b inary log 021204 23:52:08 Slave I/O thread exiting, read up to log 'binlog.002', position 4 This does NOT happen if I set AUTOCOMMIT=0. I think the above should also be fixed. The slave should read the binlog in smaller pieces, also in the case where AUTOCOMMIT=1. Yet another problem: When LOAD DATA INFILE failed in the master (AUTOCOMMIT=1): mysql load data infile '/home/heikki/rtdump' into table replt3; ERROR 1114: The table 'replt3' is full mysql the slave failed like this: heikki@hundin:~/mysql-4.0/sql mysqld --defaults-file=~/slavemy.cnf 021204 21:45:35 InnoDB: Started mysqld: ready for connections 021204 21:45:35 Slave I/O thread: connected to master 'slaveuser@hundin:3307', replication started in log 'FIRST' at position 4 021204 22:04:22 Slave: Could not open file '/tmp/SQL_LOAD-2-1-4.data', error_co de=2 021204 22:04:22 Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with SLAVE START. We stopped at log 'binlog. 026' position 27 I am forwarding these to the replication developer of MySQL AB. I hope he can fix these to 4.0.6. Best regards, Heikki Tuuri Innobase Oy --- InnoDB - transactions, row level locking, and foreign key support for MySQL See http://www.innodb.com, download MySQL-Max from http://www.mysql.com sql query - Original Message - From: Heikki Tuuri [EMAIL PROTECTED] To: [EMAIL PROTECTED]; [EMAIL PROTECTED] Sent: Thursday, December 05, 2002 12:24 AM Subject: Re: Bug Report: Replication in 4.0.5beta Michael, I have been running tests on 4.0.6 with big insert transactions on Linux. I set max_binlog_size to 2M and max_packet_size to 16M. So far no errors with tables up to 400 MB in size. Looks like MySQL always writes a big transaction as one big block to the current binlog file, and does not cut the binlog file into 2 MB pieces. Thus, it looks like the binlog file rotation cannot be the source of the bug you have observed. If you look in the datadir with ls -l the actual sizes of the master's binlogs, could it be that there really is a 1.3 GB file there? Can you make a script which would always repeat the replication failure? What is the CREATE TABLE statement of your table? What is your my.cnf like? Regards, Heikki - Original Message - From: Heikki Tuuri [EMAIL PROTECTED] To: [EMAIL PROTECTED] Cc: [EMAIL
Re: Bug Report: Replication in 4.0.5beta
Michael, I have been running tests on 4.0.6 with big insert transactions on Linux. I set max_binlog_size to 2M and max_packet_size to 16M. So far no errors with tables up to 400 MB in size. Looks like MySQL always writes a big transaction as one big block to the current binlog file, and does not cut the binlog file into 2 MB pieces. Thus, it looks like the binlog file rotation cannot be the source of the bug you have observed. If you look in the datadir with ls -l the actual sizes of the master's binlogs, could it be that there really is a 1.3 GB file there? Can you make a script which would always repeat the replication failure? What is the CREATE TABLE statement of your table? What is your my.cnf like? Regards, Heikki - Original Message - From: Heikki Tuuri [EMAIL PROTECTED] To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Thursday, November 28, 2002 1:27 PM Subject: Re: Bug Report: Replication in 4.0.5beta Michael, - Original Message - From: Michael Ryan [EMAIL PROTECTED] Newsgroups: mailing.database.mysql Sent: Thursday, November 28, 2002 12:34 PM Subject: Bug Report: Replication in 4.0.5beta The environment info was copied from the mysqlbug command by our external hosting company who truncated the lines therefore the last couple of characters from each line is not there however it was a Solaris 2.8 binary download of 4.0.5beta so you would have all of the info anyway. Description: I am using MySQL 4.0.5beta on Solaris 2.8 from a binary version downloaded from www.mysql.com on the 19th of November 2002. I have one database set up as the master database and 2 databases set up as slave databases. Each database is on a separate SUN server. I am performing intense load testing on MySQL replicated databases using InnoDB tables and transactions and I have come across what is most likely a bug. The replication is failing on the slaves with the following error (this appears both slaves error logs at the same time) :- 021127 13:48:28 Error in Log_event::read_log_event(): 'Event too big', data_len=1397639424,event_type=111 021127 13:55:36 Error in Log_event::read_log_event(): 'Event too big', data_len=1397639424,event_type=111 this definitely looks like a bug in replication. From New Zealand we got the following bug report, which might be connected to this: 02 18:32:54 Error reading packet from server: log event entry exceeded max_allowed_packet - increase max_allowed_packet on master (server_errno=2000) Above errors might happen if the pointer to the binlog becomes displaced. It will then read garbage from the event length field. I think a transaction can consist of many log events. I will run tests on our SunOS-5.8 computer to see if I can repeat this bug. Best regards, Heikki Tuuri Innobase Oy --- InnoDB - transactions, hot backup, and foreign key support for MySQL See http://www.innodb.com, download MySQL-Max from http://www.mysql.com sql query ... BBCi at http://www.bbc.co.uk/ - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
Re: Bug Report: Replication in 4.0.5beta
Michael, - Original Message - From: Michael Ryan [EMAIL PROTECTED] Newsgroups: mailing.database.mysql Sent: Thursday, November 28, 2002 12:34 PM Subject: Bug Report: Replication in 4.0.5beta The environment info was copied from the mysqlbug command by our external hosting company who truncated the lines therefore the last couple of characters from each line is not there however it was a Solaris 2.8 binary download of 4.0.5beta so you would have all of the info anyway. Description: I am using MySQL 4.0.5beta on Solaris 2.8 from a binary version downloaded from www.mysql.com on the 19th of November 2002. I have one database set up as the master database and 2 databases set up as slave databases. Each database is on a separate SUN server. I am performing intense load testing on MySQL replicated databases using InnoDB tables and transactions and I have come across what is most likely a bug. The replication is failing on the slaves with the following error (this appears both slaves error logs at the same time) :- 021127 13:48:28 Error in Log_event::read_log_event(): 'Event too big', data_len=1397639424,event_type=111 021127 13:55:36 Error in Log_event::read_log_event(): 'Event too big', data_len=1397639424,event_type=111 this definitely looks like a bug in replication. From New Zealand we got the following bug report, which might be connected to this: 02 18:32:54 Error reading packet from server: log event entry exceeded max_allowed_packet - increase max_allowed_packet on master (server_errno=2000) Above errors might happen if the pointer to the binlog becomes displaced. It will then read garbage from the event length field. I think a transaction can consist of many log events. I will run tests on our SunOS-5.8 computer to see if I can repeat this bug. Best regards, Heikki Tuuri Innobase Oy --- InnoDB - transactions, hot backup, and foreign key support for MySQL See http://www.innodb.com, download MySQL-Max from http://www.mysql.com sql query ... BBCi at http://www.bbc.co.uk/ - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
Re: Bug report: Embedded MySQL v4.04b
Matt,
thank you for the bug report.
I do not have C# in my computer. Did I understand correctly the bug does not
appear if you use the Embedded Server Library inside C++?
My first note is that you should define USE_TLS in all MySQL modules, like
Monty instructed a week ago. But I guess that cannot cause the corruption of
mysql_data_home.
I looked at the source code, and it looks like mysql_data_home should be a
pointer to a 512-character buffer called mysql_real_data_home, if you define
a datadir, and that is not the default dir (that is, .\) of the running
program. Could it be that mysql_data_home starts to point into some random
location?
I am forwarding this bug report to MySQL developers who know the mysqld
option processing best.
Best regards,
Heikki Tuuri
Innobase Oy
---
InnoDB - transactions, hot backup, and foreign key support for MySQL
See http://www.innodb.com, download MySQL-Max from http://www.mysql.com
sql query
- Original Message -
From: Matt Solnit [EMAIL PROTECTED]
To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Cc: Henry Bequet [EMAIL PROTECTED]
Sent: Wednesday, November 27, 2002 7:12 PM
Subject: Bug report: Embedded MySQL v4.04b
===
Bug report -- MySQL v4.04b, source distribution
===
Machine specs (build machine and test machine are same machine):
Compaq Presario desktop
Windows XP Professional SP1
.NET Framework SP2
--
Build description:
--
libmysqld.dll was built using Microsoft Visual C++ 6.0 SP5 and Microsoft
Visual C++ Processor Pack SP5 (used for ASM files). We build our own
version because we need to make a change so that the DLL will work with
C# clients (see below for more info).
Problem description:
A C# client was built using Microsoft Visual Studio.NET. The client
calls mysql_server_init(), passing in the command-line argument
--datadir=path, then attempts to open a connection using
mysql_init() and mysql_real_connect(). A database that is known to
exist is passed in to the mysql_real_connect() function. The function
call fails and mysql_error() returns Unknown database 'name'.
Behavior is identical using debug and release builds of libmysqld.dll.
The problem does not occur using a C++ client.
---
Possible cause:
---
Stepping into MySQL, I find that the variable mysql_data_home is set
to the correct value when mysql_server_init() returns. However, when
mysql_init() is entered, the value has become corrupted.
C# code:
/**/
/* you will need to customize the datadir and database name */
/**/
using System;
using System.Security;
using System.Runtime.InteropServices;
namespace ConsoleApplication1
{
class Test
{
[STAThread]
static void Main(string[] args)
{
TestDirectToDLL();
}
private static void TestDirectToDLL()
{
string[] args = new string[] {thisappname,
--datadir=c:/iter/source/ADCData};
MySqlAPI.ServerInit(args.Length, args, null);
IntPtr cnn = MySqlAPI.Init(IntPtr.Zero);
IntPtr result = MySqlAPI.Connect(cnn, null, null, null,
iteration, 0, null, 0);
if (result == IntPtr.Zero)
throw new Exception(MySqlAPI.Error(cnn));
MySqlAPI.Close(cnn);
MySqlAPI.ServerEnd();
}
}
class MySqlAPI
{
[SuppressUnmanagedCodeSecurity]
[DllImport(libmysqld.dll,
CharSet=System.Runtime.InteropServices.CharSet.Ansi,
EntryPoint=mysql_server_init, ExactSpelling=true)]
public static extern int ServerInit(int icArgs, string [] strArgs,
string [] strGroups);
[DllImport(libmysqld.dll,
EntryPoint=mysql_server_end, ExactSpelling=true)]
public static extern void ServerEnd();
[SuppressUnmanagedCodeSecurity]
[DllImport(libmysqld.dll, EntryPoint=mysql_init,
ExactSpelling=true)]
public static extern IntPtr Init(IntPtr ihConnection);
[SuppressUnmanagedCodeSecurity]
[DllImport(libmysqld.dll,
CharSet=System.Runtime.InteropServices.CharSet.Ansi,
EntryPoint=mysql_real_connect, ExactSpelling=true)]
public static extern IntPtr Connect(IntPtr ihConnection,
[In] string strHost, [In] string strUser, [In] string strPassword,
[In] string strDatabaseName,
uint iPort, [In] string strSocketName, uint iFlags
);
[SuppressUnmanagedCodeSecurity]
[DllImport(libmysqld.dll, EntryPoint=mysql_close,
ExactSpelling=true)]
public static extern void Close(IntPtr ihConnection);
[DllImport(libmysqld.dll,
EntryPoint=mysql_errno, ExactSpelling=true)]
public static extern uint ErrNo(IntPtr ihConnection);
[DllImport(libmysqld.dll,
RE: Bug report: Embedded MySQL v4.04b
I am looking into USE_TLS. But yes, I see that mysql_real_data_home is not corrupted, only mysql_data_home is. Thanks for your response. -- Matt -Original Message- From: Heikki Tuuri [mailto:[EMAIL PROTECTED]] Sent: Wednesday, November 27, 2002 11:40 AM To: Matt Solnit; [EMAIL PROTECTED] Cc: Henry Bequet Subject: Re: Bug report: Embedded MySQL v4.04b Matt, thank you for the bug report. I do not have C# in my computer. Did I understand correctly the bug does not appear if you use the Embedded Server Library inside C++? My first note is that you should define USE_TLS in all MySQL modules, like Monty instructed a week ago. But I guess that cannot cause the corruption of mysql_data_home. I looked at the source code, and it looks like mysql_data_home should be a pointer to a 512-character buffer called mysql_real_data_home, if you define a datadir, and that is not the default dir (that is, .\) of the running program. Could it be that mysql_data_home starts to point into some random location? I am forwarding this bug report to MySQL developers who know the mysqld option processing best. Best regards, Heikki Tuuri Innobase Oy --- InnoDB - transactions, hot backup, and foreign key support for MySQL See http://www.innodb.com, download MySQL-Max from http://www.mysql.com sql query - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
re: BUG REPORT : key creation
Angeloluca, Tuesday, November 19, 2002, 12:21:58 PM, you wrote: AdBamdc I have a problem with key creation : AdBamdc Server version: 4.0.4-beta-max-nt Binary version AdBamdc PC : DELL OPTIPLEX GX100 AdBamdc OS : Windows 2000 Professional AdBamdc RAM: 256 Mb [skip] AdBamdc 236 Is the maximum permitted length , I don't know why. I got the same result on the 4.0.4, but it works fine on the latest tree. -- For technical support contracts, goto https://order.mysql.com/?ref=ensita This email is sponsored by Ensita.net http://www.ensita.net/ __ ___ ___ __ / |/ /_ __/ __/ __ \/ /Egor Egorov / /|_/ / // /\ \/ /_/ / /__ [EMAIL PROTECTED] /_/ /_/\_, /___/\___\_\___/ MySQL AB / Ensita.net ___/ www.mysql.com - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
Re: bug report: Embedded MySQL v4.04b
Matt,
since you are using InnoDB, you cannot call server_end() and server_init()
again during the lifetime of the process. InnoDB does not clean up its
internal data structures in server_end().
Is there some special reason you would need to shut down the server and
open it again?
Regards,
Heikki
Innobase Oy
sql query
...
===
Bug report -- MySQL v4.04b, source distribution
===
Machine specs (build machine and test machine are same machine):
Dell Inspiron 8200 laptop
Windows XP Professional SP1
.NET Framework SP2
--
Build description:
--
libmysqld.dll was built using Microsoft Visual C++ 6.0 SP5 and Microsoft
Visual C++ Processor Pack SP5 (used for ASM files). We build our own
version because we need to make a change so that the DLL will work with
C# clients (see below for more info).
Problem description:
A C# client was built using Microsoft Visual Studio.NET. The client
calls mysql server init(), mysql server end(), and mysql server init()
again. On second call to mysql server init(), the exception
System.NullReferenceException is thrown.
From an equivalent C++ program, an access violation occurs at the same
point.
Behavior is identical using debug and release builds of libmysqld.dll.
C# code:
using System;
using System.Runtime.InteropServices;
using System.Security;
namespace Reproduce Embedded MySQL crash
{
class Class1
{
[STAThread]
static void Main(string[] args)
{
MySqlAPI.ServerInit(0, null, null);
MySqlAPI.ServerEnd();
MySqlAPI.ServerInit(0, null, null);
MySqlAPI.ServerEnd();
}
}
class MySqlAPI
{
[SuppressUnmanagedCodeSecurity]
[DllImport(libmysqld.dll,
CharSet=System.Runtime.InteropServices.CharSet.Ansi,
EntryPoint=mysql server init, ExactSpelling=true)]
public static extern int ServerInit(int icArgs, string [] strArgs,
string [] strGroups);
[DllImport(libmysqld.dll,
EntryPoint=mysql server end, ExactSpelling=true)]
public static extern void ServerEnd();
}
}
-
C++ code:
-
//
/* modified from test dll.cpp that ships with MySQL */
//
#include stdafx.h
#include winsock.h
#include mysql.h
#include stdarg.h
#include stdio.h
#include stdlib.h
const char *server groups[] = {
test libmysqld SERVER, embedded, server, NULL
};
int main(int argc, char* argv[])
{
mysql server init(argc, argv, (char **)server groups);
mysql server end();
mysql server init(argc, argv, (char **)server groups);
mysql server end();
return 0;
}
---
MySQL binaries:
---
Upon request, I can supply our debug and release builds of
libmysqld.dll.
---
Source code change description:
---
There is only one change we make to the MySQL 4.04b source distribution.
We define USE TLS for the mysys project. The reason is that it's
required for clients that use LoadLibrary(), which includes all C#
clients. More information can be found in the VC++ documentation
article Rules and Limitations for TLS.
---
My contact information:
---
Matt Solnit [EMAIL PROTECTED]
-
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
http://lists.mysql.com/ (the list archive)
To request this thread, e-mail [EMAIL PROTECTED]
To unsubscribe, e-mail [EMAIL PROTECTED]
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
Re: Re: Bug report
Hello Douglas, Saturday, October 19, 2002, 2:47:06 PM, you wrote: D cd /home/mysql/mysql/data D touch ibdata1 D How do I control that size? It means that you already have file ibdata1 and this file has another size that you are specifying in my.cnf ... D - Original Message - D From: Egor Egorov [EMAIL PROTECTED] D To: [EMAIL PROTECTED] D Sent: Saturday, October 19, 2002 6:35 AM D Subject: re: Bug report Douglas, Saturday, October 19, 2002, 1:08:14 AM, you wrote: D INNODB: Error:datafile /home/mysql/mysql/data/ibdata1 is of a different D size D INNODB: than specified in the my.cnf file! D INNODB:Assertion failure in thread 138207232 in file os0file.c D send bug report to [EMAIL PROTECTED] D mysqld got signal 11 D key_buffer_size = 16773120 D read_buffer_size = 131072 D sort_buffer_size = 0 D max_used_connections = 0 D threads_connected = 0 D It is possible that mysqld could use up to D key_buffer_size + (read_buffersize + sort_buffer_size) * D max_connections = 29180 bytes of memory D Hope that's OK; if not, decrease some variables in the equation D 021018 17:50:31 mysqld ended Douglas, did you carefully read error message? INNODB: Error:datafile /home/mysql/mysql/data/ibdata1 is of a different D size INNODB: than specified in the my.cnf file! -- For technical support contracts, goto https://order.mysql.com/?ref=ensita This email is sponsored by Ensita.net http://www.ensita.net/ __ ___ ___ __ / |/ /_ __/ __/ __ \/ /Egor Egorov / /|_/ / // /\ \/ /_/ / /__ [EMAIL PROTECTED] /_/ /_/\_, /___/\___\_\___/ MySQL AB / Ensita.net ___/ www.mysql.com - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
re: Bug report
Douglas, Saturday, October 19, 2002, 1:08:14 AM, you wrote: D INNODB: Error:datafile /home/mysql/mysql/data/ibdata1 is of a different size D INNODB: than specified in the my.cnf file! D INNODB:Assertion failure in thread 138207232 in file os0file.c D send bug report to [EMAIL PROTECTED] D mysqld got signal 11 D key_buffer_size = 16773120 D read_buffer_size = 131072 D sort_buffer_size = 0 D max_used_connections = 0 D threads_connected = 0 D It is possible that mysqld could use up to D key_buffer_size + (read_buffersize + sort_buffer_size) * D max_connections = 29180 bytes of memory D Hope that's OK; if not, decrease some variables in the equation D 021018 17:50:31 mysqld ended Douglas, did you carefully read error message? INNODB: Error:datafile /home/mysql/mysql/data/ibdata1 is of a different size INNODB: than specified in the my.cnf file! -- For technical support contracts, goto https://order.mysql.com/?ref=ensita This email is sponsored by Ensita.net http://www.ensita.net/ __ ___ ___ __ / |/ /_ __/ __/ __ \/ /Egor Egorov / /|_/ / // /\ \/ /_/ / /__ [EMAIL PROTECTED] /_/ /_/\_, /___/\___\_\___/ MySQL AB / Ensita.net ___/ www.mysql.com - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
Re: bug report
Quasimodo wrote: This occured while using phpmyadmin 2.3.0-rc4: You seem to have found a bug in the SQL parser. Please submit a bug report with the data chunk below: --BEGIN CUT-- JElkOiBzcWxwYXJzZXIubGliLnBocCx2IDEuMTUgMjAwMi8wNy8yNiAxODozMDo1OSBsZW05 [snip] This is reporting a bug in phpMyAdmin's SQL parser, not MySQL's. You need to file this bug report at phpMyAdmin's sourceforge bug page: http://sourceforge.net/tracker/?group_id=23067atid=377408 -Mark -- For technical support contracts, visit https://order.mysql.com/?ref=mmma __ ___ ___ __ / |/ /_ __/ __/ __ \/ / Mark Matthews [EMAIL PROTECTED] / /|_/ / // /\ \/ /_/ / /__ MySQL AB, Full-Time Developer - JDBC/Java /_/ /_/\_, /___/\___\_\___/ Flossmoor (Chicago), IL USA ___/ www.mysql.com - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
Re: Bug report
This is documented behavior. Indexes are not used with DESC. Ver 4.X does, however support DESC with an index. Grigoriy Vinogradov wrote: Bug Report: Version: 3.23.51-max OS: Windows ME Problem: Synopsis: Does not use index when ordering records on datetime field in the descending order, even though though this field is NOT NULL. I created the following table: CREATE TABLE Threads (threadID int NOT NULL PRIMARY KEY, forumID int NOT NULL REFERENCES Forums(forumID), discussion char(100), starter char(40), num_replies int, last_modified datetime NOT NULL, INDEX (forumID, last_modified)); When I execute the following query with explain word I notice that index is not used: explain select * from Threads where forumID = 1 order by last_modified desc; If I want to select these records in the ascending order, than the index IS used. Thanks, Greg Vinogradov - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
Re: BUG report (CREATE TEMPORARY TABLES problem) 4.0.2/4.0.3-bk snapshot
Sergey S. Kostyliov writes: Description: Any grant at a tables level make 'CREATE TEMPORARY TABLE' privilege not working ERROR 1142 How-To-Repeat: 1) (under root) mysql GRANT CREATE TEMPORARY TABLES ON *.* TO test_user@localhost IDENTIFIED BY 'test_pass'; Query OK, 0 rows affected (0.01 sec) 2) (under test_user) mysql CREATE TEMPORARY TABLE tmp_table(i INT); Query OK, 0 rows affected (0.00 sec) 3) (under root) mysql CREATE TABLE t (i INT); Query OK, 0 rows affected (0.00 sec) mysql GRANT SELECT ON test.t TO test_user@localhost; Query OK, 0 rows affected (0.00 sec) 4) (under test_user) mysql CREATE TEMPORARY TABLE tmp_table(i INT); ERROR 1142: create command denied to user: 'test_user@localhost' for table 'tmp_table' Hi! Thank you for your bug report. Thanks to it, the above bug was fixed and fix will come up in 4.0.3. -- Regards, __ ___ ___ __ / |/ /_ __/ __/ __ \/ /Mr. Sinisa Milivojevic [EMAIL PROTECTED] / /|_/ / // /\ \/ /_/ / /__ MySQL AB, Fulltime Developer /_/ /_/\_, /___/\___\_\___/ Larnaca, Cyprus ___/ www.mysql.com - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
Re: BUG report (select distinct...) 4.0.2 and latest bk snapshot
Sergey S. Kostyliov writes: At first I want to thank you for a fast answer, On Tuesday 23 July 2002 21:45, Peter Zaitsev wrote: On Tuesday 23 July 2002 19:39, Sergey S. Kostyliov wrote: Description: ERROR 2013: Lost connection to MySQL server during query. snip Note: The same results with oficial mysql-4.0.2 and latest bk snapshot, mysql was compiled with both gcc-3.1 and gcc-295.3 Unfortunately we can't test this bug report as we do not have tables to run this query with. Please check tables you have at first to eliminate corrupted table is the source of the problem and if problem persist upload them into secret directory at ftp://support.mysql.com Sorry, but it doesn't looks like a table corruption. To be sure i've tested this with fresh tables created from a sql script. I can also add that this is easily reproducable on two of my boxes (UP SMP) If you are able to create small repeatable case you may send it in the mail. Unfortunately it's a kind of big test case (1.2Mb) I had uploaded a test case with name select_distinct-ssk.tar.gz to ftp://support.mysql.com/pub/mysql/secret -- Best regards, Sergey S. Kostyliov [EMAIL PROTECTED] Public PGP key: http://sysadminday.org.ru/rathamahata.asc If the table names are : product_supplier route supplier shop_product_supplier then I have got them. I will test your case today. Is it one bug or two ?? -- Regards, __ ___ ___ __ / |/ /_ __/ __/ __ \/ /Mr. Sinisa Milivojevic [EMAIL PROTECTED] / /|_/ / // /\ \/ /_/ / /__ MySQL AB, Fulltime Developer /_/ /_/\_, /___/\___\_\___/ Larnaca, Cyprus ___/ www.mysql.com - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
Re: BUG report (select distinct...) 4.0.2 and latest bk snapshot
On Wednesday 24 July 2002 17:23, Sinisa Milivojevic wrote: Sergey S. Kostyliov writes: At first I want to thank you for a fast answer, On Tuesday 23 July 2002 21:45, Peter Zaitsev wrote: On Tuesday 23 July 2002 19:39, Sergey S. Kostyliov wrote: Description: ERROR 2013: Lost connection to MySQL server during query. cut I had uploaded a test case with name select_distinct-ssk.tar.gz to ftp://support.mysql.com/pub/mysql/secret cut If the table names are : product_supplier route supplier shop_product_supplier Yes they are. 4 tables, names are right. then I have got them. I will test your case today. Is it one bug or two ?? It'is a one bug AFAIK. -- Best regards, Sergey S. Kostyliov [EMAIL PROTECTED] Public PGP key: http://sysadminday.org.ru/rathamahata.asc - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
Re: BUG report (select distinct...) 4.0.2 and latest bk snapshot
On Tuesday 23 July 2002 19:39, Sergey S. Kostyliov wrote: Description: ERROR 2013: Lost connection to MySQL server during query. How-To-Repeat: select distinct s.supplier_id, s.who_pay, r.name as rname, s.name, s.nick, s.address, s.contact_person, s.email, s.fax, s.comment from supplier s, product_supplier ps, shop_product_supplier sps use index(product_supplier_id) left join route r on r.route_id=s.route_id where ps.product_supplier_id=sps.product_supplier_id and sps.shop_id=10 and ps.supplier_id=s.supplier_id order by name limit 0, 10 Result: ERROR 2013: Lost connection to MySQL server during query Note: The same results with oficial mysql-4.0.2 and latest bk snapshot, mysql was compiled with both gcc-3.1 and gcc-295.3 Unfortunately we can't test this bug report as we do not have tables to run this query with. Please check tables you have at first to eliminate corrupted table is the source of the problem and if problem persist upload them into secret directory at ftp://support.mysql.com If you are able to create small repeatable case you may send it in the mail. -- __ ___ ___ __ / |/ /_ __/ __/ __ \/ /Mr. Peter Zaitsev [EMAIL PROTECTED] / /|_/ / // /\ \/ /_/ / /__ MySQL AB, Full-Time Developer /_/ /_/\_, /___/\___\_\___/ Moscow, Russia ___/ www.mysql.com M: +7 095 725 4955 - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
Re: BUG report (select distinct...) 4.0.2 and latest bk snapshot
At first I want to thank you for a fast answer, On Tuesday 23 July 2002 21:45, Peter Zaitsev wrote: On Tuesday 23 July 2002 19:39, Sergey S. Kostyliov wrote: Description: ERROR 2013: Lost connection to MySQL server during query. snip Note: The same results with oficial mysql-4.0.2 and latest bk snapshot, mysql was compiled with both gcc-3.1 and gcc-295.3 Unfortunately we can't test this bug report as we do not have tables to run this query with. Please check tables you have at first to eliminate corrupted table is the source of the problem and if problem persist upload them into secret directory at ftp://support.mysql.com Sorry, but it doesn't looks like a table corruption. To be sure i've tested this with fresh tables created from a sql script. I can also add that this is easily reproducable on two of my boxes (UP SMP) If you are able to create small repeatable case you may send it in the mail. Unfortunately it's a kind of big test case (1.2Mb) I had uploaded a test case with name select_distinct-ssk.tar.gz to ftp://support.mysql.com/pub/mysql/secret -- Best regards, Sergey S. Kostyliov [EMAIL PROTECTED] Public PGP key: http://sysadminday.org.ru/rathamahata.asc - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
Re: BUG REPORT FOR MYSQL
Hi! - Original Message - From: Wan YU [EMAIL PROTECTED] Newsgroups: mailing.database.mysql Sent: Thursday, June 27, 2002 8:25 PM Subject: BUG REPORT FOR MYSQL Hi, I'm doing research on DBMS recently and have found some bugs in mysql's source codes.I think it will be more convenient to point out them directly than using mysqlbug.The following are my finds. mysqladmin -version output: mysqladmin Ver 8.22 Distrib 3.23.44, for pc-linux-gnu on i686 Copyright (C) 2000 MySQL AB MySQL Finland AB TCX DataKonsult AB BUGS REPORT: 1. file:innobase/os/os0sync.c function: os_event_wait_time line:237 This function uses Windows API WaitForSingleObject while passing a wrong parameter to it. Because WaitForSingleObject wants the second parameter to be quantity of milliseconds while it actually gets the quantity of seconds. The parameter to os_event_wait_time function is in microseconds. To get milliseconds we divide it by 1000. FIX RECOMMENDATION: Maybe it should be modified this way, err = WaitForSingleObject(event, time); 2. file: innobase/log/log0log.c function: log_archive_do line: 2171 There will be a deadlock obviously! These lines of code are not used in MySQL. But I do not see a deadlock either: the thread just waits that an event becomes signaled again. FIX RECOMMENTDATION: Comment this statement. Please check these places and I'm expecting your answer. Good luck, sincerely, YBETTER Regards, Heikki Innobase Oy (sql database) - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
Re: bug report with functions
Patrice,
Thursday, April 04, 2002, 4:41:24 AM, you wrote:
P MySQL Version: 3.23.49
P OS: Win 98
P Query 1: select length ('abc') returns
P You have an error in your SQL syntax near '('abc')' at
P line 1
P Query2: select length('abc') returns 3: OK
P Note the space between the 'h' and '(' in Query 1. The
P parser does not like this space...
P The same problem occurs with all the functions.
It's a well-known feature. You can run MySQL in ANSI mode to have any
number of spaces between function name and brackets, look at:
http://www.mysql.com/doc/A/N/ANSI_mode.html
P Thanks,
P Patrice Khawam.
--
For technical support contracts, goto https://order.mysql.com/
This email is sponsored by Ensita.net http://www.ensita.net/
__ ___ ___ __
/ |/ /_ __/ __/ __ \/ /Egor Egorov
/ /|_/ / // /\ \/ /_/ / /__ [EMAIL PROTECTED]
/_/ /_/\_, /___/\___\_\___/ MySQL AB / Ensita.net
___/ www.mysql.com
-
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
http://lists.mysql.com/ (the list archive)
To request this thread, e-mail [EMAIL PROTECTED]
To unsubscribe, e-mail [EMAIL PROTECTED]
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
Re: bug report: mysql_install_db hangs on execution.
Legault, Alain writes: SEND-PR: -*- send-pr -*- SEND-PR: Lines starting with `SEND-PR' will be removed automatically, as SEND-PR: will all comments (text enclosed in `' and `'). SEND-PR: Subject: Mysqld hangs on initialization with mysql_install_db. Hi! A usual cause for the above behaviour is a difference in the patch level between your OS and the one on which our binary was built. More info in our manual. -- Consider taking our support. Visit : https://order.mysql.com Regards, __ ___ ___ __ / |/ /_ __/ __/ __ \/ /Mr. Sinisa Milivojevic [EMAIL PROTECTED] / /|_/ / // /\ \/ /_/ / /__ MySQL AB, Fulltime Developer /_/ /_/\_, /___/\___\_\___/ Larnaca, Cyprus ___/ www.mysql.com - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
Re: bug report: mysql_install_db hangs on execution.
Legault, Alain writes: SEND-PR: -*- send-pr -*- SEND-PR: Lines starting with `SEND-PR' will be removed automatically, as SEND-PR: will all comments (text enclosed in `' and `'). SEND-PR: Subject: Mysqld hangs on initialization with mysql_install_db. Hi! A usual cause for the above behaviour is a difference in the patch level between your OS and the one on which our binary was built. More info in our manual. -- Consider taking our support. Visit : https://order.mysql.com Regards, __ ___ ___ __ / |/ /_ __/ __/ __ \/ /Mr. Sinisa Milivojevic [EMAIL PROTECTED] / /|_/ / // /\ \/ /_/ / /__ MySQL AB, Fulltime Developer /_/ /_/\_, /___/\___\_\___/ Larnaca, Cyprus ___/ www.mysql.com - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
Re: Bug Report
Michael Cook writes: Hi folks, Here is a bug report using the bug tool... [skip] Thanks!!! Michael == CigarPool == http://www.cigarpool.com Hi! You should check why your configure is broken. Instead of lines : configure:1592: checking whether the C++ compiler (c++ -O3 -felide- constructors -fno-exceptions -fno- rtti ) works it should be : configure:1592: checking whether the C++ compiler (c++ -O3 -felide- constructors -fno-exceptions -fno-rtti ) works -- Regards, __ ___ ___ __ / |/ /_ __/ __/ __ \/ /Mr. Sinisa Milivojevic [EMAIL PROTECTED] / /|_/ / // /\ \/ /_/ / /__ MySQL AB, Fulltime Developer /_/ /_/\_, /___/\___\_\___/ Larnaca, Cyprus ___/ www.mysql.com - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
Re: Bug Report - SELECT Does Not Recognize Column Alias
Hi Rick, - Original Message - From: Rick Emery [EMAIL PROTECTED] Description: The SELECT statement fails to recognize that an alias (mycol) was set for a column. Note the column name is created from a table alias (c1) mysql select c1.id as mycol from colors c1 right join colors c2 on c1.color=c2.color AND c1.id != c2.id where mycol is not null; ERROR 1054: Unknown column 'mycol' in 'where clause' This is actually correct and documented behaviour, see: http://www.mysql.com/doc/P/r/Problems_with_alias.html Quoted from there: [snip] ANSI SQL doesn't allow you to refer to an alias in a WHERE clause. This is because when the WHERE code is executed the column value may not yet be determined. For example, the following query is illegal: SELECT id,COUNT(*) AS cnt FROM table_name WHERE cnt 0 GROUP BY id; [snap] I have now put an explicit reference to this section in the explanation of the SELECT statement in the manual, as I'm sure you're not the first to trip over this one ;-) Thanks for your feedback! Regards, Arjen. -- MySQL Training Worldwide, http://www.mysql.com/training/ __ ___ ___ __ / |/ /_ __/ __/ __ \/ /Mr. Arjen G. Lentz [EMAIL PROTECTED] / /|_/ / // /\ \/ /_/ / /__ MySQL AB, Technical Writer /_/ /_/\_, /___/\___\_\___/ Brisbane, QLD Australia ___/ www.mysql.com - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
Re: bug report / source compile error
At 10:33 05/09/2001 +0200, abadon wrote: Hi, Hi, I have Windows NT 4.0 (build 1381/SP6a) running IIS4 Webserver ( http://www.abadon.net or 212.30.85.173 ) connected via CableModem/LAN to Internet. I have also PHP ( Version 4.0.6 )scripting engine and MySQL server ( Client API version 3.23.32 said PHP info page, but in WinMySQL admin Ver 1.3 is : Server : 3.23.41-nt Client: 3.23.36 - This means that the server is 3.23.41 release and the WinMySQLAdmin that is the client was compiled with the 3.23.36 library. I will update the libraries for the next release. but It doesen`t matter - MySQL working perfect without any problems or bugs ( info page is: http://212.30.85.173/phpinfo.php with UN info and PW guest, `cause my server is not public, only developing ...). But my problem is: I have downloaded SourceCode for MySQL ( mysql-3.23.41-win-src.zip ), unzip and open workspace with Visual C++ ( part of MS VisualStudio 6 Pro with SP 4 ) and rebuild all - without problem, excepcion one with describe: Configuration: strings - Win32 Debug Performing Custom Build Step on .\Strxmov.asm The name specified is not recognized as an internal or external command, operable program or batch file. Error executing e:\winnt\system32\cmd.exe. This means that you don't have the MS Macro Assembler Compiler in your environment to perform the custom build of strxmov.asm file. In your strings project file you have instructions for the MASM 5.0 and if you don't have it, your options are: - Change the strings.dsp and strings dsw files by the files you find in \strings\NOMASM directory. In this case you won't compile the strings stuff with the assembler. - Get the Masm 6.x from Microsoft and change the custom command. You find instructions about at: http://msdn.microsoft.com/vstudio/sp/vs6sp5/faq.asp - If you have the MASM 6.x: - Right click over the strings project and click Set as Active Project. - Right click again and click Settings. - Open the strings tree. - Click over the Strings.asm file and at right side click the tab Custom Build. In the windows Commands, change the line: masm -Mx -t -DDOS386 -DM_I386 $(InputPath),$(Outdir)\$(InputName).obj,,, by the line below: ml /Cx /nologo /DDOS386 /DM_I386 /Zm /coff /c /Fo $(Outdir)\$(InputName).obj $(InputPath) - Do the same with the file Strxmov.asm. - Change the assembler command for the Win32 debug and release trees. Regards, Miguel mysqld.exe - 1 error(s), 0 warning(s) I haven`t idea what`s that: bug or is something wrong with my machine or IDE ( my knowledge is not so perfect... )... regards ps - I haven`t any problems with other sources codes, like Macromedia SWF flash source, etc sorry to my bad english language... Slevec Brane, Slovenia mailto:[EMAIL PROTECTED] Here is complete log: Deleting intermediate files and output files for project 'heap - Win32 Debug'. Deleting intermediate files and output files for project 'isam - Win32 Debug'. Deleting intermediate files and output files for project 'merge - Win32 Debug'. Deleting intermediate files and output files for project 'mysys - Win32 Debug'. Deleting intermediate files and output files for project 'regex - Win32 Debug'. Deleting intermediate files and output files for project 'strings - Win32 Debug'. Deleting intermediate files and output files for project 'dbug - Win32 Debug'. Deleting intermediate files and output files for project 'zlib - Win32 Debug'. Deleting intermediate files and output files for project 'mysqlclient - Win32 Debug'. Deleting intermediate files and output files for project 'mysql - Win32 Debug'. Deleting intermediate files and output files for project 'mysqladmin - Win32 Debug'. Deleting intermediate files and output files for project 'mysqldump - Win32 Debug'. Deleting intermediate files and output files for project 'mysqlimport - Win32 Debug'. Deleting intermediate files and output files for project 'MySqlManager - Win32 Debug'. Deleting intermediate files and output files for project 'mysqlshow - Win32 Debug'. Deleting intermediate files and output files for project 'libmySQL - Win32 Debug'. Deleting intermediate files and output files for project 'myTest - Win32 Debug'. Deleting intermediate files and output files for project 'thr_test - Win32 Debug'. Deleting intermediate files and output files for project 'replace - Win32 Debug'. Deleting intermediate files and output files for project 'myisam - Win32 Debug'. Deleting intermediate files and output files for project 'myisammrg - Win32 Debug'. Deleting intermediate files and output files for project 'innobase - Win32 Debug'. Deleting intermediate files and output files for project 'bdb - Win32 Debug'. Deleting intermediate files and output files for project 'mysqld - Win32 Debug'. Configuration: heap - Win32 Debug Compiling... _check.c _rectest.c
Re: Bug report.
Hi! What InnoDB version you are using? A bad rollback bug was fixed in version 3.23.39. Regards, Heikki At 05:40 PM 8/4/01 +0300, you wrote: Content-Type: message/rfc822 Content-Description: forwarded message Content-Transfer-Encoding: 7bit MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Subject: Bug report. From: Cal Evans [EMAIL PROTECTED] To: Mysql [EMAIL PROTECTED] Date: Sat, 4 Aug 2001 09:25:55 -0500 I have a reproducible but it's not easy to reproduce. It involves a complex transaction that gets rolled back instead of committed. Cal Innobase: Assertion failure in thread 8201 in file trx0roll.c line 887 Innobase: we intentionally generate a memory trap. Innobase: Send a bug report to [EMAIL PROTECTED] mysqld got signal 11; The manual section 'Debugging a MySQL server' tells you how to use a stack trace and/or the core file to produce a readable backtrace that may help in finding out why mysqld died. Attempting backtrace. You can use the following information to find out where mysqld died. If you see no messages after this, something went terribly wrong... Stack range sanity check OK, backtrace follows: 0x4007c552 0x8178fea 0x813d2b7 0x813dc9e 0x8177851 0x8179310 0x811aaec 0x81122b1 0x80d3233 0x80d4889 0x80cfc39 0x80cf16e Stack trace successful, trying to get some variables. Some pointers may be invalid and cause the dump to abort... thd-query at 0x83540c0 = rollback thd-thread_id = 1 Successfully dumped variables, if you ran with --log, take a look at the details of what thread 1 did to cause the crash. In some cases of really bad corruption, this value may be invalid Please use the information above to create a repeatable test case for the crash, and send it to [EMAIL PROTECTED] Cal http://www.calevans.com - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php Content-Type: text/plain; charset=us-ascii Content-Description: message body and .signature Content-Transfer-Encoding: 7bit Something for you ... -- Regards, __ ___ ___ __ / |/ /_ __/ __/ __ \/ /Mr. Sinisa Milivojevic [EMAIL PROTECTED] / /|_/ / // /\ \/ /_/ / /__ MySQL AB, FullTime Developer /_/ /_/\_, /___/\___\_\___/ Larnaca, Cyprus ___/ www.mysql.com - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
RE: Bug report.
Hi, Sorry to have bothered everyone. I was using .38. I just noticed that and am currently building .40. Cal http://www.calevans.com -Original Message- From: Heikki Tuuri [mailto:[EMAIL PROTECTED]] Sent: Saturday, August 04, 2001 9:59 AM To: Sinisa Milivojevic; [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: Re: Bug report. Hi! What InnoDB version you are using? A bad rollback bug was fixed in version 3.23.39. Regards, Heikki At 05:40 PM 8/4/01 +0300, you wrote: Content-Type: message/rfc822 Content-Description: forwarded message Content-Transfer-Encoding: 7bit MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Subject: Bug report. From: Cal Evans [EMAIL PROTECTED] To: Mysql [EMAIL PROTECTED] Date: Sat, 4 Aug 2001 09:25:55 -0500 I have a reproducible but it's not easy to reproduce. It involves a complex transaction that gets rolled back instead of committed. Cal Innobase: Assertion failure in thread 8201 in file trx0roll.c line 887 Innobase: we intentionally generate a memory trap. Innobase: Send a bug report to [EMAIL PROTECTED] mysqld got signal 11; The manual section 'Debugging a MySQL server' tells you how to use a stack trace and/or the core file to produce a readable backtrace that may help in finding out why mysqld died. Attempting backtrace. You can use the following information to find out where mysqld died. If you see no messages after this, something went terribly wrong... Stack range sanity check OK, backtrace follows: 0x4007c552 0x8178fea 0x813d2b7 0x813dc9e 0x8177851 0x8179310 0x811aaec 0x81122b1 0x80d3233 0x80d4889 0x80cfc39 0x80cf16e Stack trace successful, trying to get some variables. Some pointers may be invalid and cause the dump to abort... thd-query at 0x83540c0 = rollback thd-thread_id = 1 Successfully dumped variables, if you ran with --log, take a look at the details of what thread 1 did to cause the crash. In some cases of really bad corruption, this value may be invalid Please use the information above to create a repeatable test case for the crash, and send it to [EMAIL PROTECTED] Cal http://www.calevans.com - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php Content-Type: text/plain; charset=us-ascii Content-Description: message body and .signature Content-Transfer-Encoding: 7bit Something for you ... -- Regards, __ ___ ___ __ / |/ /_ __/ __/ __ \/ /Mr. Sinisa Milivojevic [EMAIL PROTECTED] / /|_/ / // /\ \/ /_/ / /__ MySQL AB, FullTime Developer /_/ /_/\_, /___/\___\_\___/ Larnaca, Cyprus ___/ www.mysql.com - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
Re: Bug report: FULLTEXT index corrupts the index with too many TEXT fields
I'm back now, and have tested the 3.23.40. It works like a charm :-) Nice work! Now I only wait for the Win32 binary to be released. I didn't think there were any delays between the releasins anymore? - Carsten - Original Message - From: Sergei Golubchik [EMAIL PROTECTED] To: Carsten Gehling [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Friday, July 20, 2001 1:49 PM Subject: Re: Bug report: FULLTEXT index corrupts the index with too many TEXT fields Hi! 3.23 (but 4.0 hasn't that bug either). Will be 2.23.40 soon. And have nice trip, btw. On Jul 20, Carsten Gehling wrote: Which dev. tree is that? 3.23 or 4.0? - Carsten (who hasn't left yet ;-) - Original Message - From: Sergei Golubchik [EMAIL PROTECTED] Subject: Re: Bug report: FULLTEXT index corrupts the index with too many Hi! Ok, confirmed (finally :-) ) My fault was that I was using our latest developmnet tree. When I've tried this on 3.23.39 as went public, the bug appeared. So, looks like the bug was fixed even before it was found :-) Probably, it is somehow related to over bug I've fixed since 3.23.39 release. On Jul 20, Carsten Gehling wrote: I'm going to Spain today and cannot respond to any questions in the next week. I was going to wait with this until I got home again, but what the heck ;-) Run the following script through your MySQL on an empty database with mysql -uusername -ppassword dbname scriptname and the last command should produce the following error: ERROR 1034 at line 31: Incorrect key file for table: 'visitkort'. Try to repair it Regards, Sergei -- MySQL Development Team __ ___ ___ __ / |/ /_ __/ __/ __ \/ / Sergei Golubchik [EMAIL PROTECTED] / /|_/ / // /\ \/ /_/ / /__ MySQL AB, http://www.mysql.com/ /_/ /_/\_, /___/\___\_\___/ Osnabrueck, Germany ___/ Regards, Sergei -- MySQL Development Team __ ___ ___ __ / |/ /_ __/ __/ __ \/ / Sergei Golubchik [EMAIL PROTECTED] / /|_/ / // /\ \/ /_/ / /__ MySQL AB, http://www.mysql.com/ /_/ /_/\_, /___/\___\_\___/ Osnabrueck, Germany ___/ - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
Re: Bug report: FULLTEXT index corrupts the index with too many TEXT fields
Carsten Gehling writes: I'm back now, and have tested the 3.23.40. It works like a charm :-) Nice work! Now I only wait for the Win32 binary to be released. I didn't think there were any delays between the releasins anymore? - Carsten Thanks for the compliments. Win32 binaries will be soon. Some InnoDB problems have to be solved first. -- Regards, __ ___ ___ __ / |/ /_ __/ __/ __ \/ /Mr. Sinisa Milivojevic [EMAIL PROTECTED] / /|_/ / // /\ \/ /_/ / /__ MySQL AB, FullTime Developer /_/ /_/\_, /___/\___\_\___/ Larnaca, Cyprus ___/ www.mysql.com - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
Re: Bug report: FULLTEXT index corrupts the index with too many TEXT fields
I'm going to Spain today and cannot respond to any questions in the next week. I was going to wait with this until I got home again, but what the heck ;-) Run the following script through your MySQL on an empty database with mysql -uusername -ppassword dbname scriptname and the last command should produce the following error: ERROR 1034 at line 31: Incorrect key file for table: 'visitkort'. Try to repair it I've let 3 people besides myself test it, and they all get the same error. It has now been tested on: Win2k server SP2, MySQL 3.23.32 Win2k server SP2, MySQL 3.23.39 Win2k Pro (Danish), MySQL 3.23.33 (normal version) Win2k Pro SP2 (English), MySQL 3.23.38-MAX Debian GNU/Linux, MySQL 3.23.39 (bniary .deb package) Some other Linux (didn't get the distro name), MySQL 3.23.39 All of the above produces the error. So something must be wrong. Sincerily, - Carsten Here's the script: ## CREATE TABLE `visitkort` ( `id` int(10) unsigned NOT NULL auto_increment, `kategori_id` int(10) unsigned NOT NULL default '0', `aktiv` tinyint(3) unsigned NOT NULL default '0', `navn` varchar(60) NOT NULL default '', `adresse` varchar(150) NOT NULL default '', `postnr` varchar(5) NOT NULL default '', `tlf` varchar(20) NOT NULL default '', `fax` varchar(20) NOT NULL default '', `email` varchar(60) NOT NULL default '', `password` varchar(20) NOT NULL default '', `url` varchar(150) NOT NULL default '', `beskrivelse` varchar(200) NOT NULL default '', `visitkort` tinyint(3) unsigned NOT NULL default '0', `skabelon` tinyint(3) unsigned NOT NULL default '0', `logo` tinyint(3) unsigned NOT NULL default '0', `billede` tinyint(3) unsigned NOT NULL default '0', `tekst1` text NOT NULL, `tekst2` text NOT NULL, `tekst3` text NOT NULL, `tekst4` text NOT NULL, PRIMARY KEY (`id`), FULLTEXT KEY `ft` (`navn`,`beskrivelse`,`tekst1`,`tekst2`,`tekst3`,`tekst4`) ) TYPE=MyISAM; insert into visitkort (kategori_id) values (108); update visitkort set navn = 'test5' where id = last_insert_id(); update visitkort set tekst1 = 'bla bla' where id = last_insert_id(); ## - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail mysql-unsubscribe-##L=##[EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
Re: Bug report: FULLTEXT index corrupts the index with too many TEXT fields
Thanks for your bug report. I am sure Sergei will have the answer before you come back from Spain ... -- Regards, __ ___ ___ __ / |/ /_ __/ __/ __ \/ /Mr. Sinisa Milivojevic [EMAIL PROTECTED] / /|_/ / // /\ \/ /_/ / /__ MySQL AB, FullTime Developer /_/ /_/\_, /___/\___\_\___/ Larnaca, Cyprus ___/ www.mysql.com - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
Re: Bug report: FULLTEXT index corrupts the index with too many TEXT fields
Hi! Ok, confirmed (finally :-) ) My fault was that I was using our latest developmnet tree. When I've tried this on 3.23.39 as went public, the bug appeared. So, looks like the bug was fixed even before it was found :-) Probably, it is somehow related to over bug I've fixed since 3.23.39 release. On Jul 20, Carsten Gehling wrote: I'm going to Spain today and cannot respond to any questions in the next week. I was going to wait with this until I got home again, but what the heck ;-) Run the following script through your MySQL on an empty database with mysql -uusername -ppassword dbname scriptname and the last command should produce the following error: ERROR 1034 at line 31: Incorrect key file for table: 'visitkort'. Try to repair it Regards, Sergei -- MySQL Development Team __ ___ ___ __ / |/ /_ __/ __/ __ \/ / Sergei Golubchik [EMAIL PROTECTED] / /|_/ / // /\ \/ /_/ / /__ MySQL AB, http://www.mysql.com/ /_/ /_/\_, /___/\___\_\___/ Osnabrueck, Germany ___/ - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
Re: Bug report: FULLTEXT index corrupts the index with too many TEXT fields
BTW: As I've stated earlier, the error goes away, if you either remove the FULLTEXT index or let the affected fields accept NULL values. - Carsten - Original Message - From: Carsten Gehling [EMAIL PROTECTED] To: Sergei Golubchik [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Friday, July 20, 2001 12:06 PM Subject: Re: Bug report: FULLTEXT index corrupts the index with too many TEXT fields I'm going to Spain today and cannot respond to any questions in the next week. I was going to wait with this until I got home again, but what the heck ;-) Run the following script through your MySQL on an empty database with mysql -uusername -ppassword dbname scriptname and the last command should produce the following error: ERROR 1034 at line 31: Incorrect key file for table: 'visitkort'. Try to repair it I've let 3 people besides myself test it, and they all get the same error. It has now been tested on: Win2k server SP2, MySQL 3.23.32 Win2k server SP2, MySQL 3.23.39 Win2k Pro (Danish), MySQL 3.23.33 (normal version) Win2k Pro SP2 (English), MySQL 3.23.38-MAX Debian GNU/Linux, MySQL 3.23.39 (bniary .deb package) Some other Linux (didn't get the distro name), MySQL 3.23.39 All of the above produces the error. So something must be wrong. Sincerily, - Carsten Here's the script: ## CREATE TABLE `visitkort` ( `id` int(10) unsigned NOT NULL auto_increment, `kategori_id` int(10) unsigned NOT NULL default '0', `aktiv` tinyint(3) unsigned NOT NULL default '0', `navn` varchar(60) NOT NULL default '', `adresse` varchar(150) NOT NULL default '', `postnr` varchar(5) NOT NULL default '', `tlf` varchar(20) NOT NULL default '', `fax` varchar(20) NOT NULL default '', `email` varchar(60) NOT NULL default '', `password` varchar(20) NOT NULL default '', `url` varchar(150) NOT NULL default '', `beskrivelse` varchar(200) NOT NULL default '', `visitkort` tinyint(3) unsigned NOT NULL default '0', `skabelon` tinyint(3) unsigned NOT NULL default '0', `logo` tinyint(3) unsigned NOT NULL default '0', `billede` tinyint(3) unsigned NOT NULL default '0', `tekst1` text NOT NULL, `tekst2` text NOT NULL, `tekst3` text NOT NULL, `tekst4` text NOT NULL, PRIMARY KEY (`id`), FULLTEXT KEY `ft` (`navn`,`beskrivelse`,`tekst1`,`tekst2`,`tekst3`,`tekst4`) ) TYPE=MyISAM; insert into visitkort (kategori_id) values (108); update visitkort set navn = 'test5' where id = last_insert_id(); update visitkort set tekst1 = 'bla bla' where id = last_insert_id(); ## - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail mysql-unsubscribe-##L=##[EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail mysql-unsubscribe-##L=##[EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
Re: Bug report: FULLTEXT index corrupts the index with too many TEXT fields
Hi, I've just tested with MySQL 4.0, no error, but strange result : mysql insert into visitkort (kategori_id) values (108); Query OK, 1 row affected (0.00 sec) mysql update visitkort set navn = 'test5' where id = last_insert_id(); Query OK, 1 row affected (0.00 sec) Rows matched: 1 Changed: 1 Warnings: 0 mysql update visitkort set tekst1 = 'bla bla' where id = last_insert_id(); Query OK, 1 row affected (0.00 sec) Rows matched: 1 Changed: 1 Warnings: 0 The latest update seems to have been successful, but if you look at the table you can see the tekst1 field has not been updated : ++-+---+---+-++-+-+---+- -+-+-+---+--+--+-+-- --++++ | id | kategori_id | aktiv | navn | adresse | postnr | tlf | fax | email | password | url | beskrivelse | visitkort | skabelon | logo | billede | tekst1 | tekst2 | tekst3 | tekst4 | ++-+---+---+-++-+-+---+- -+-+-+---+--+--+-+-- --++++ | 1 | 108 | 0 | test5 | || | | | | | | 0 |0 |0 | 0 || ||| ++-+---+---+-++-+-+---+- -+-+-+---+--+--+-+-- --++++ Regards, Jocelyn Fournier Presence-PC - Original Message - From: Carsten Gehling [EMAIL PROTECTED] To: Sergei Golubchik [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Friday, July 20, 2001 12:06 PM Subject: Re: Bug report: FULLTEXT index corrupts the index with too many TEXT fields I'm going to Spain today and cannot respond to any questions in the next week. I was going to wait with this until I got home again, but what the heck ;-) Run the following script through your MySQL on an empty database with mysql -uusername -ppassword dbname scriptname and the last command should produce the following error: ERROR 1034 at line 31: Incorrect key file for table: 'visitkort'. Try to repair it I've let 3 people besides myself test it, and they all get the same error. It has now been tested on: Win2k server SP2, MySQL 3.23.32 Win2k server SP2, MySQL 3.23.39 Win2k Pro (Danish), MySQL 3.23.33 (normal version) Win2k Pro SP2 (English), MySQL 3.23.38-MAX Debian GNU/Linux, MySQL 3.23.39 (bniary .deb package) Some other Linux (didn't get the distro name), MySQL 3.23.39 All of the above produces the error. So something must be wrong. Sincerily, - Carsten Here's the script: ## CREATE TABLE `visitkort` ( `id` int(10) unsigned NOT NULL auto_increment, `kategori_id` int(10) unsigned NOT NULL default '0', `aktiv` tinyint(3) unsigned NOT NULL default '0', `navn` varchar(60) NOT NULL default '', `adresse` varchar(150) NOT NULL default '', `postnr` varchar(5) NOT NULL default '', `tlf` varchar(20) NOT NULL default '', `fax` varchar(20) NOT NULL default '', `email` varchar(60) NOT NULL default '', `password` varchar(20) NOT NULL default '', `url` varchar(150) NOT NULL default '', `beskrivelse` varchar(200) NOT NULL default '', `visitkort` tinyint(3) unsigned NOT NULL default '0', `skabelon` tinyint(3) unsigned NOT NULL default '0', `logo` tinyint(3) unsigned NOT NULL default '0', `billede` tinyint(3) unsigned NOT NULL default '0', `tekst1` text NOT NULL, `tekst2` text NOT NULL, `tekst3` text NOT NULL, `tekst4` text NOT NULL, PRIMARY KEY (`id`), FULLTEXT KEY `ft` (`navn`,`beskrivelse`,`tekst1`,`tekst2`,`tekst3`,`tekst4`) ) TYPE=MyISAM; insert into visitkort (kategori_id) values (108); update visitkort set navn = 'test5' where id = last_insert_id(); update visitkort set tekst1 = 'bla bla' where id = last_insert_id(); ## - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail mysql-unsubscribe-##L=##[EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail mysql-unsubscribe-##L=##[EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
Re: Bug report: FULLTEXT index corrupts the index with too many TEXT fields
Which dev. tree is that? 3.23 or 4.0? - Carsten (who hasn't left yet ;-) - Original Message - From: Sergei Golubchik [EMAIL PROTECTED] To: Carsten Gehling [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Friday, July 20, 2001 1:22 PM Subject: Re: Bug report: FULLTEXT index corrupts the index with too many TEXT fields Hi! Ok, confirmed (finally :-) ) My fault was that I was using our latest developmnet tree. When I've tried this on 3.23.39 as went public, the bug appeared. So, looks like the bug was fixed even before it was found :-) Probably, it is somehow related to over bug I've fixed since 3.23.39 release. On Jul 20, Carsten Gehling wrote: I'm going to Spain today and cannot respond to any questions in the next week. I was going to wait with this until I got home again, but what the heck ;-) Run the following script through your MySQL on an empty database with mysql -uusername -ppassword dbname scriptname and the last command should produce the following error: ERROR 1034 at line 31: Incorrect key file for table: 'visitkort'. Try to repair it Regards, Sergei -- MySQL Development Team __ ___ ___ __ / |/ /_ __/ __/ __ \/ / Sergei Golubchik [EMAIL PROTECTED] / /|_/ / // /\ \/ /_/ / /__ MySQL AB, http://www.mysql.com/ /_/ /_/\_, /___/\___\_\___/ Osnabrueck, Germany ___/ - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
Re: Bug report: FULLTEXT index corrupts the index with too many TEXT fields
Hi! 3.23 (but 4.0 hasn't that bug either). Will be 2.23.40 soon. And have nice trip, btw. On Jul 20, Carsten Gehling wrote: Which dev. tree is that? 3.23 or 4.0? - Carsten (who hasn't left yet ;-) - Original Message - From: Sergei Golubchik [EMAIL PROTECTED] Subject: Re: Bug report: FULLTEXT index corrupts the index with too many Hi! Ok, confirmed (finally :-) ) My fault was that I was using our latest developmnet tree. When I've tried this on 3.23.39 as went public, the bug appeared. So, looks like the bug was fixed even before it was found :-) Probably, it is somehow related to over bug I've fixed since 3.23.39 release. On Jul 20, Carsten Gehling wrote: I'm going to Spain today and cannot respond to any questions in the next week. I was going to wait with this until I got home again, but what the heck ;-) Run the following script through your MySQL on an empty database with mysql -uusername -ppassword dbname scriptname and the last command should produce the following error: ERROR 1034 at line 31: Incorrect key file for table: 'visitkort'. Try to repair it Regards, Sergei -- MySQL Development Team __ ___ ___ __ / |/ /_ __/ __/ __ \/ / Sergei Golubchik [EMAIL PROTECTED] / /|_/ / // /\ \/ /_/ / /__ MySQL AB, http://www.mysql.com/ /_/ /_/\_, /___/\___\_\___/ Osnabrueck, Germany ___/ Regards, Sergei -- MySQL Development Team __ ___ ___ __ / |/ /_ __/ __/ __ \/ / Sergei Golubchik [EMAIL PROTECTED] / /|_/ / // /\ \/ /_/ / /__ MySQL AB, http://www.mysql.com/ /_/ /_/\_, /___/\___\_\___/ Osnabrueck, Germany ___/ - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
RE: Bug report: FULLTEXT index corrupts the index with too many TEXT fields
Hi Where can we get V4.0? Thanks Simon -Original Message- From: Fournier Jocelyn [Presence-PC] [mailto:[EMAIL PROTECTED]] Sent: 20 July 2001 12:30 To: Carsten Gehling; Sergei Golubchik Cc: [EMAIL PROTECTED] Subject: Re: Bug report: FULLTEXT index corrupts the index with too many TEXT fields Hi, I've just tested with MySQL 4.0, no error, but strange result : mysql insert into visitkort (kategori_id) values (108); Query OK, 1 row affected (0.00 sec) mysql update visitkort set navn = 'test5' where id = last_insert_id(); Query OK, 1 row affected (0.00 sec) Rows matched: 1 Changed: 1 Warnings: 0 mysql update visitkort set tekst1 = 'bla bla' where id = last_insert_id(); Query OK, 1 row affected (0.00 sec) Rows matched: 1 Changed: 1 Warnings: 0 The latest update seems to have been successful, but if you look at the table you can see the tekst1 field has not been updated : ++-+---+---+-++-+-+---+- -+-+-+---+--+--+-+-- --++++ | id | kategori_id | aktiv | navn | adresse | postnr | tlf | fax | email | password | url | beskrivelse | visitkort | skabelon | logo | billede | tekst1 | tekst2 | tekst3 | tekst4 | ++-+---+---+-++-+-+---+- -+-+-+---+--+--+-+-- --++++ | 1 | 108 | 0 | test5 | || | | | | | | 0 |0 |0 | 0 || ||| ++-+---+---+-++-+-+---+- -+-+-+---+--+--+-+-- --++++ Regards, Jocelyn Fournier Presence-PC - Original Message - From: Carsten Gehling [EMAIL PROTECTED] To: Sergei Golubchik [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Friday, July 20, 2001 12:06 PM Subject: Re: Bug report: FULLTEXT index corrupts the index with too many TEXT fields I'm going to Spain today and cannot respond to any questions in the next week. I was going to wait with this until I got home again, but what the heck ;-) Run the following script through your MySQL on an empty database with mysql -uusername -ppassword dbname scriptname and the last command should produce the following error: ERROR 1034 at line 31: Incorrect key file for table: 'visitkort'. Try to repair it I've let 3 people besides myself test it, and they all get the same error. It has now been tested on: Win2k server SP2, MySQL 3.23.32 Win2k server SP2, MySQL 3.23.39 Win2k Pro (Danish), MySQL 3.23.33 (normal version) Win2k Pro SP2 (English), MySQL 3.23.38-MAX Debian GNU/Linux, MySQL 3.23.39 (bniary .deb package) Some other Linux (didn't get the distro name), MySQL 3.23.39 All of the above produces the error. So something must be wrong. Sincerily, - Carsten Here's the script: ## CREATE TABLE `visitkort` ( `id` int(10) unsigned NOT NULL auto_increment, `kategori_id` int(10) unsigned NOT NULL default '0', `aktiv` tinyint(3) unsigned NOT NULL default '0', `navn` varchar(60) NOT NULL default '', `adresse` varchar(150) NOT NULL default '', `postnr` varchar(5) NOT NULL default '', `tlf` varchar(20) NOT NULL default '', `fax` varchar(20) NOT NULL default '', `email` varchar(60) NOT NULL default '', `password` varchar(20) NOT NULL default '', `url` varchar(150) NOT NULL default '', `beskrivelse` varchar(200) NOT NULL default '', `visitkort` tinyint(3) unsigned NOT NULL default '0', `skabelon` tinyint(3) unsigned NOT NULL default '0', `logo` tinyint(3) unsigned NOT NULL default '0', `billede` tinyint(3) unsigned NOT NULL default '0', `tekst1` text NOT NULL, `tekst2` text NOT NULL, `tekst3` text NOT NULL, `tekst4` text NOT NULL, PRIMARY KEY (`id`), FULLTEXT KEY `ft` (`navn`,`beskrivelse`,`tekst1`,`tekst2`,`tekst3`,`tekst4`) ) TYPE=MyISAM; insert into visitkort (kategori_id) values (108); update visitkort set navn = 'test5' where id = last_insert_id(); update visitkort set tekst1 = 'bla bla' where id = last_insert_id(); ## - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail mysql-unsubscribe-##L=##[EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread
Re: Bug report: FULLTEXT index corrupts the index with too many TEXT fields
Take a look at : http://www.mysql.com/doc/I/n/Installing_source_tree.html - Original Message - From: Simon Green [EMAIL PROTECTED] To: 'Fournier Jocelyn [Presence-PC]' [EMAIL PROTECTED]; Carsten Gehling [EMAIL PROTECTED]; Sergei Golubchik [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Friday, July 20, 2001 2:55 PM Subject: RE: Bug report: FULLTEXT index corrupts the index with too many TEXT fields Hi Where can we get V4.0? Thanks Simon -Original Message- From: Fournier Jocelyn [Presence-PC] [mailto:[EMAIL PROTECTED]] Sent: 20 July 2001 12:30 To: Carsten Gehling; Sergei Golubchik Cc: [EMAIL PROTECTED] Subject: Re: Bug report: FULLTEXT index corrupts the index with too many TEXT fields Hi, I've just tested with MySQL 4.0, no error, but strange result : mysql insert into visitkort (kategori_id) values (108); Query OK, 1 row affected (0.00 sec) mysql update visitkort set navn = 'test5' where id = last_insert_id(); Query OK, 1 row affected (0.00 sec) Rows matched: 1 Changed: 1 Warnings: 0 mysql update visitkort set tekst1 = 'bla bla' where id = last_insert_id(); Query OK, 1 row affected (0.00 sec) Rows matched: 1 Changed: 1 Warnings: 0 The latest update seems to have been successful, but if you look at the table you can see the tekst1 field has not been updated : ++-+---+---+-++-+-+---+- -+-+-+---+--+--+-+ -- --++++ | id | kategori_id | aktiv | navn | adresse | postnr | tlf | fax | email | password | url | beskrivelse | visitkort | skabelon | logo | billede | tekst1 | tekst2 | tekst3 | tekst4 | ++-+---+---+-++-+-+---+- -+-+-+---+--+--+-+ -- --++++ | 1 | 108 | 0 | test5 | || | | | | | | 0 |0 |0 | 0 || ||| ++-+---+---+-++-+-+---+- -+-+-+---+--+--+-+ -- --++++ Regards, Jocelyn Fournier Presence-PC - Original Message - From: Carsten Gehling [EMAIL PROTECTED] To: Sergei Golubchik [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Friday, July 20, 2001 12:06 PM Subject: Re: Bug report: FULLTEXT index corrupts the index with too many TEXT fields I'm going to Spain today and cannot respond to any questions in the next week. I was going to wait with this until I got home again, but what the heck ;-) Run the following script through your MySQL on an empty database with mysql -uusername -ppassword dbname scriptname and the last command should produce the following error: ERROR 1034 at line 31: Incorrect key file for table: 'visitkort'. Try to repair it I've let 3 people besides myself test it, and they all get the same error. It has now been tested on: Win2k server SP2, MySQL 3.23.32 Win2k server SP2, MySQL 3.23.39 Win2k Pro (Danish), MySQL 3.23.33 (normal version) Win2k Pro SP2 (English), MySQL 3.23.38-MAX Debian GNU/Linux, MySQL 3.23.39 (bniary .deb package) Some other Linux (didn't get the distro name), MySQL 3.23.39 All of the above produces the error. So something must be wrong. Sincerily, - Carsten Here's the script: ## CREATE TABLE `visitkort` ( `id` int(10) unsigned NOT NULL auto_increment, `kategori_id` int(10) unsigned NOT NULL default '0', `aktiv` tinyint(3) unsigned NOT NULL default '0', `navn` varchar(60) NOT NULL default '', `adresse` varchar(150) NOT NULL default '', `postnr` varchar(5) NOT NULL default '', `tlf` varchar(20) NOT NULL default '', `fax` varchar(20) NOT NULL default '', `email` varchar(60) NOT NULL default '', `password` varchar(20) NOT NULL default '', `url` varchar(150) NOT NULL default '', `beskrivelse` varchar(200) NOT NULL default '', `visitkort` tinyint(3) unsigned NOT NULL default '0', `skabelon` tinyint(3) unsigned NOT NULL default '0', `logo` tinyint(3) unsigned NOT NULL default '0', `billede` tinyint(3) unsigned NOT NULL default '0', `tekst1` text NOT NULL, `tekst2` text NOT NULL, `tekst3` text NOT NULL, `tekst4` text NOT NULL, PRIMARY KEY (`id`), FULLTEXT KEY `ft` (`navn`,`beskrivelse`,`tekst1`,`tekst2`,`tekst3`,`tekst4`) ) TYPE=MyISAM; insert into visitkort (kategori_id) values (108); update visitkort set navn = 'test5' where id = last_insert_id(); update visitkort set tekst1 = 'bla bla' where id = last_insert_id(); ## - Before posting, please check
Re: Bug report: FULLTEXT index corrupts the index with too many TEXT fields
Hi! On Jul 19, Carsten Gehling wrote: Finally I was able to produce a complete step-by-step to corrupt the index ;-) mysql insert into visitkort (kategori_id) values (108); mysql select last_insert_id(); mysql update visitkort set navn = 'test5' where id = 1; mysql update visitkort set tekst1 = 'bla bla' where id = 1; ERROR 1034: Incorrect key file for table: 'visitkort'. Try to repair it Sorry, but everything works ok for me: mysql update visitkort set tekst1 = 'bla bla' where id = 1; Query OK, 1 row affected (0.00 sec) Rows matched: 1 Changed: 1 Warnings: 0 Regards, Sergei -- MySQL Development Team __ ___ ___ __ / |/ /_ __/ __/ __ \/ / Sergei Golubchik [EMAIL PROTECTED] / /|_/ / // /\ \/ /_/ / /__ MySQL AB, http://www.mysql.com/ /_/ /_/\_, /___/\___\_\___/ Osnabrueck, Germany ___/ - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
Re: Bug report: FULLTEXT index corrupts the index with too many TEXT fields
Finally I was able to produce a complete step-by-step to corrupt the index ;-) Do the following in the mySQL console (with e.g. a fresh and empty table): mysql insert into visitkort (kategori_id) values (108); Query OK, 1 row affected (0.01 sec) mysql select last_insert_id(); +--+ | last_insert_id() | +--+ |1 | +--+ 1 row in set (0.00 sec) mysql update visitkort set navn = 'test5' where id = 1; Query OK, 1 row affected (0.00 sec) Rows matched: 1 Changed: 1 Warnings: 0 mysql update visitkort set tekst1 = 'bla bla' where id = 1; ERROR 1034: Incorrect key file for table: 'visitkort'. Try to repair it After this, myisamchk reports the following: D:\mysql\data\testmyisamchk --extend-check visitkort Checking MyISAM file: visitkort Data records: 1 Deleted blocks: 0 myisamchk: warning: Table is marked as crashed myisamchk: warning: 1 clients is using or hasn't closed the table properly - check file-size - check key delete-chain - check record delete-chain - check index reference - check data record references index: 1 - check data record references index: 2 - check data record references index: 3 - check data record references index: 4 - check data record references index: 5 - check data record references index: 6 - check records and index references MyISAM-table 'visitkort' is usable but should be fixed I guess this isn't the expected behavior of mySQL ;-) It should be noted, that the above behavior does not occur if I drop the FULLTEXT index. Without this index, the errors are gone and table works fine. I've also tried to remove all other indexes except the FULLTEXT and the primary key, and the error is still there. So it is definitely a problem within the FULLTEXT index. - Carsten - Original Message - From: Sergei Golubchik [EMAIL PROTECTED] To: Carsten Gehling [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Monday, July 16, 2001 6:26 PM Subject: Re: Bug report: FULLTEXT index corrupts the index with too many TEXT fields Hi! On Jul 16, Carsten Gehling wrote: Description: A specific table (see How-To-Repeat) with a FULLTEXT index causes errors in the MYI file when inserting new rows. 1) Create the following table: CREATE TABLE `visitkort` ( [skip] ) TYPE=MyISAM; 2) Insert a row with the following statement: 3) Run myisamchk with the option --extend-check and you get the following myisamchk: warning: 1 clients is using or hasn't closed the table properly The error does not occur, if you drop the FULLTEXT index Ok, I was able to repeat this, still I do not think it's a bug. Message given by myisamchk is perfectly legal - you should not expect MySQL to close the table immidiately when the client closes the connection. MySQL can keep the table open to speedup access to it from, e.g., next connection. MySQL will close the table on FLUSH TABLE, or when the pool of opened tables is exceeded. if you will add 2.5) flush table the error message will dissapear. if you will shutdown MySQL instead, you'll get no error, either. if you will issue CHECK TABLE visitkort EXTENDED instead of using external program myisamchk, again there will be no error message. So, looks like everything is ok. In you first message (without test case) you've also added The result of this is, that if anyone is trying to update the same record afterwards, the index is corrupted. I wasn't able to reproduce that. If you have a test case for this, please, let me know. Regards, Sergei -- MySQL Development Team __ ___ ___ __ / |/ /_ __/ __/ __ \/ / Sergei Golubchik [EMAIL PROTECTED] / /|_/ / // /\ \/ /_/ / /__ MySQL AB, http://www.mysql.com/ /_/ /_/\_, /___/\___\_\___/ Osnabrueck, Germany ___/ - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
Solution (but only a temporary one) Re: Bug report: FULLTEXT index corrupts the index with too many TEXT fields
After the latest post, curiosity got the better of me (which is always good in a debug situation). I tried to change all 6 fields that compose the FULLTEXT index, so that they accept NULL values. The result? The error is gone. Is this a valid solution however? I've never been a great fan of the NULL value in RDBMS' - I regard it as a necessary evil to be used sparsely. So it would be great if I did not have to convert my text fields (text varchar) into accepting NULL. - Carsten - Original Message - From: Sergei Golubchik [EMAIL PROTECTED] To: Carsten Gehling [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Monday, July 16, 2001 6:26 PM Subject: Re: Bug report: FULLTEXT index corrupts the index with too many TEXT fields Hi! On Jul 16, Carsten Gehling wrote: Description: A specific table (see How-To-Repeat) with a FULLTEXT index causes errors in the MYI file when inserting new rows. 1) Create the following table: CREATE TABLE `visitkort` ( [skip] ) TYPE=MyISAM; 2) Insert a row with the following statement: 3) Run myisamchk with the option --extend-check and you get the following myisamchk: warning: 1 clients is using or hasn't closed the table properly The error does not occur, if you drop the FULLTEXT index Ok, I was able to repeat this, still I do not think it's a bug. Message given by myisamchk is perfectly legal - you should not expect MySQL to close the table immidiately when the client closes the connection. MySQL can keep the table open to speedup access to it from, e.g., next connection. MySQL will close the table on FLUSH TABLE, or when the pool of opened tables is exceeded. if you will add 2.5) flush table the error message will dissapear. if you will shutdown MySQL instead, you'll get no error, either. if you will issue CHECK TABLE visitkort EXTENDED instead of using external program myisamchk, again there will be no error message. So, looks like everything is ok. In you first message (without test case) you've also added The result of this is, that if anyone is trying to update the same record afterwards, the index is corrupted. I wasn't able to reproduce that. If you have a test case for this, please, let me know. Regards, Sergei -- MySQL Development Team __ ___ ___ __ / |/ /_ __/ __/ __ \/ / Sergei Golubchik [EMAIL PROTECTED] / /|_/ / // /\ \/ /_/ / /__ MySQL AB, http://www.mysql.com/ /_/ /_/\_, /___/\___\_\___/ Osnabrueck, Germany ___/ - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
Re: Bug report: FULLTEXT index corrupts the index with too many TEXT fields
Hi! On Jul 16, Carsten Gehling wrote: Description: A specific table (see How-To-Repeat) with a FULLTEXT index causes errors in the MYI file when inserting new rows. 1) Create the following table: CREATE TABLE `visitkort` ( [skip] ) TYPE=MyISAM; 2) Insert a row with the following statement: 3) Run myisamchk with the option --extend-check and you get the following myisamchk: warning: 1 clients is using or hasn't closed the table properly The error does not occur, if you drop the FULLTEXT index Ok, I was able to repeat this, still I do not think it's a bug. Message given by myisamchk is perfectly legal - you should not expect MySQL to close the table immidiately when the client closes the connection. MySQL can keep the table open to speedup access to it from, e.g., next connection. MySQL will close the table on FLUSH TABLE, or when the pool of opened tables is exceeded. if you will add 2.5) flush table the error message will dissapear. if you will shutdown MySQL instead, you'll get no error, either. if you will issue CHECK TABLE visitkort EXTENDED instead of using external program myisamchk, again there will be no error message. So, looks like everything is ok. In you first message (without test case) you've also added The result of this is, that if anyone is trying to update the same record afterwards, the index is corrupted. I wasn't able to reproduce that. If you have a test case for this, please, let me know. Regards, Sergei -- MySQL Development Team __ ___ ___ __ / |/ /_ __/ __/ __ \/ / Sergei Golubchik [EMAIL PROTECTED] / /|_/ / // /\ \/ /_/ / /__ MySQL AB, http://www.mysql.com/ /_/ /_/\_, /___/\___\_\___/ Osnabrueck, Germany ___/ - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
Re: bug report on WinMySQLadmin 1.1
Werner Stuerenburg writes: _ Win98 4.10.98, AMD Duron, 128 MB RAM MySQL 3.23.39 running on localhost _ Query is DELETE FROM staticStrings WHERE ruri LIKE 'staticAnzeigen%' _ Error is Lost connection to MySQL server during query _ -- Herzlich Werner Stuerenburg Hi! The above behavour can be caused by corrupted table. If however, the above DELETE always crashes our latest 3.23.39 binary, you should prepare a repeatable test case and send it to [EMAIL PROTECTED] A complete bug report is done in the following manner: 1) First check the reference manual and the mail archive ! We try very hard to keep the manual up to date so most questions can usually be solved by looking it up. Write in the mail that you have checked the reference manual and mail archive so others know that you have tried to solve the problem yourself. 2) ALWAYS use mysqlbug when posting questions about a MySQL version you are using! mysqlbug is for bug reports AND questions. 3) Send the bug report to the right mailing list. (See http://www.mysql.com/documentation/lists.html). If you are unsure you should use [EMAIL PROTECTED] 4) Include a full example for the problem, including a full test case with all responses/error messages. -- Regards, __ ___ ___ __ / |/ /_ __/ __/ __ \/ /Mr. Sinisa Milivojevic [EMAIL PROTECTED] / /|_/ / // /\ \/ /_/ / /__ MySQL AB, FullTime Developer /_/ /_/\_, /___/\___\_\___/ Larnaca, Cyprus ___/ www.mysql.com - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
Re: bug report
At 00:13 10/06/2001 +0900, atsushi wrote: Hi, The problem reported happens on Win9x and ME platform because mysqld.exe was compiled accidentally with a __NT__ define for the InnoDB library. Use instead the mysqld-max.exe server on these OSs. This issue is already fixed for the next release. Regards, Miguel hello, I've encountered the following message after I've set inodb_file_path. C:\WINDOWSmysqld Innobase: Assertion failure in thread 4293055721 in file M:\mysql-3.23\innobase\ os\os0file.c line 187 Innobase: we intentionally generate a memory trap. Innobase: Send a bug report to [EMAIL PROTECTED] 010602 7:39:48 D:\HTTPD\MYSQL\BIN\MYSQLD.EXE: Got signal 11. Aborting! 010602 7:39:49 Aborting InnoDB: Warning: shutting down not properly started database 010602 7:39:55 D:\HTTPD\MYSQL\BIN\MYSQLD.EXE: Shutdown Complete My computer's spec is pentiumII 366khz with 128kb memory, windows98 servicepack1, apache1.3.20, mysql3.23. I'm now using mysql without innobase so I always see the message, 'inodb_file_path is not set'. Is this ok to use mysqld? Or am I supposed to use mysql after inodb_file_path is set? I don't know what to do. also I don't know what country this message will go. Atsushi Nakasugi in Japan. - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php -- For technical support contracts, goto https://order.mysql.com/ __ ___ ___ __ / |/ /_ __/ __/ __ \/ /Mr. Miguel A. Solórzano [EMAIL PROTECTED] / /|_/ / // /\ \/ /_/ / /__ MySQL AB, FullTime Developer /_/ /_/\_, /___/\___\_\___/ Mogi das Cruzes - São Paulo, Brazil ___/ www.mysql.com - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
Re: Bug report
George Mihalcea writes:
Hello!
I compiled mysql 3.23.38 with support for innodb tables.
The server is a dual PIII 850, with 1 GB RAM, 1 SCSI disk.
OS is Slackware current . Kernel version is 2.4.4 , no patches.
I created 4 tablespaces of 1000M each.
I took a dump from another mysql server (with myisam tables), I changed type
to innodb in dump files and I tried to create the databases and tables in this
new server.
The dump has 2GB.
First, I tried with the big dump file, then with one file for each database
(about 2000 databases with the same structure).
When I tried with the big file, the mysql database crashed after about half of
the file, he tryed to restart, crashed again, he tried to restart an so on...
I had to delete all directories and files and restart with the default mysql
and test databases.
The seconf time, every database had its own dump. Mysql crashed after 1700
databases.
If I try to continue with the other databases remaining, it crashes again.
I attached the log mysql error log file and my.cnf config file.
What should I do? Is any of the parameters in my.cnf wrong ?
Should I stay to MyISAM tables ?
Thanks,
George Mihalcea.
Hi!
Seems like the error log file was stripped out, so we did not see it.
Did you have 1700 databases or 1700 tables. If that number is number
of databases , how many tables do you have ??
Can you repeat it all, with one variable values changed. Notably the
following one:
innodb_data_file_path =
ibdata1:2000M;ibdata2:2000M;ibdata3:2000M;ibdata4:2000M
Regards,
Sinisa
__ _ _ ___ == MySQL AB
/*/\*\/\*\ /*/ \*\ /*/ \*\ |*| Sinisa Milivojevic
/*/ /*/ /*/ \*\_ |*| |*||*| mailto:[EMAIL PROTECTED]
/*/ /*/ /*/\*\/*/ \*\|*| |*||*| Larnaca, Cyprus
/*/ /*/ /*/\*\_/*/ \*\_/*/ |*|
/*/^^^\*\^^^
/*/ \*\Developers Team
-
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
http://lists.mysql.com/ (the list archive)
To request this thread, e-mail [EMAIL PROTECTED]
To unsubscribe, e-mail [EMAIL PROTECTED]
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
Re: Bug report
George, this is the bug that slipped into the rollback code in .38. You can download a patch from my website http://www.innobase.fi/bugfixes.html You are running out of tablespace when doing the table import. MyISAM tables take a lot more space when converted to the InnoDB type. Make your data files bigger. If you encounter more problems, please write to me. Regards, Heikki Innobase Oy At 02:25 PM 5/24/01 +0300, you wrote: Content-Type: message/rfc822 Content-Description: forwarded message Content-Transfer-Encoding: 7bit Subject: Bug report From: George Mihalcea [EMAIL PROTECTED] To: [EMAIL PROTECTED] Date: Thu, 24 May 2001 10:49:05 +0300 Organization: NetBridge Investments SRL Sender: [EMAIL PROTECTED] MIME-Version: 1.0 Content-Type: multipart/mixed; boundary=42287FF6A78805E1B8015642 Hello! I compiled mysql 3.23.38 with support for innodb tables. The server is a dual PIII 850, with 1 GB RAM, 1 SCSI disk. OS is Slackware current . Kernel version is 2.4.4 , no patches. I created 4 tablespaces of 1000M each. I took a dump from another mysql server (with myisam tables), I changed type to innodb in dump files and I tried to create the databases and tables in this new server. The dump has 2GB. First, I tried with the big dump file, then with one file for each database (about 2000 databases with the same structure). When I tried with the big file, the mysql database crashed after about half of the file, he tryed to restart, crashed again, he tried to restart an so on... I had to delete all directories and files and restart with the default mysql and test databases. The seconf time, every database had its own dump. Mysql crashed after 1700 databases. If I try to continue with the other databases remaining, it crashes again. I attached the log mysql error log file and my.cnf config file. What should I do? Is any of the parameters in my.cnf wrong ? Should I stay to MyISAM tables ? Thanks, George Mihalcea. Attachment Converted: C:\EUDORA\logerr1.gz # Example mysql config file for large systems. # # This is for large system with memory = 512M where the system runs mainly # MySQL. # # You can copy this file to # /etc/mf.cnf to set global options, # mysql-data-dir/my.cnf to set server-specific options (in this # installation this directory is /var/lib/mysql) or # ~/.my.cnf to set user-specific options. # # One can in this file use all long options that the program supports. # If you want to know which options a program support, run the program # with --help option. # The following options will be passed to all MySQL clients [client] #password = your_password port = 3306 socket = /var/lib/mysql/mysql.sock # Here follows entries for some specific programs # The MySQL server [mysqld] port = 3306 socket = /var/lib/mysql/mysql.sock skip-locking set-variable = key_buffer=256M set-variable = max_allowed_packet=1M set-variable = table_cache=1 set-variable = sort_buffer=1M set-variable = record_buffer=1M set-variable = myisam_sort_buffer_size=64M set-variable = thread_cache=4 set-variable = max_connections=400 # Try number of CPU's*2 for thread_concurrency set-variable = thread_concurrency=4 log-bin server-id = 1 # Uncomment the following if you are using BDB tables #set-variable = bdb_cache_size=64M #set-variable = bdb_max_lock=10 # Uncomment the following if you are using Innobase tables innodb_data_home_dir = /var/lib/mysql/ innodb_log_group_home_dir = /var/lib/mysql/ innodb_log_arch_dir = /var/lib/mysql/ innodb_data_file_path = ibdata1:1000M;ibdata2:1000M;ibdata3:1000M;ibdata4:1000M set-variable = innodb_mirrored_log_groups=1 set-variable = innodb_log_files_in_group=3 set-variable = innodb_log_file_size=50M set-variable = innodb_log_buffer_size=8M innodb_flush_log_at_trx_commit=1 innodb_log_archive=1 set-variable = innodb_buffer_pool_size=400M set-variable = innodb_additional_mem_pool_size=50M set-variable = innodb_file_io_threads=4 set-variable = innodb_lock_wait_timeout=50 # Point the following paths to different dedicated disks tmpdir = /tmp/ #log-update= /path-to-dedicated-directory/hostname [mysqldump] quick set-variable = max_allowed_packet=16M [mysql] no-auto-rehash # Remove the next comment character if you are not familiar with SQL #safe-updates [isamchk] set-variable = key_buffer=128M set-variable = sort_buffer=128M set-variable = read_buffer=2M set-variable = write_buffer=2M [myisamchk] set-variable = key_buffer=128M set-variable = sort_buffer=128M set-variable = read_buffer=2M set-variable = write_buffer=2M [mysqlhotcopy] interactive-timeout - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try:
Re: bug report
Can you try this with a more recent MySQL version? I cannot reproduce it here, on FreeBSD 4.3 running MySQL 3.23.38. G'luck, Peter -- This sentence contains exactly threee erors. On Tue, May 22, 2001 at 08:32:24PM +0300, Tarog Adrian wrote: Hello, I think me and my fellows here at office, found a bug in mysql. The system is: RedHat 7.0, kernel 2.2.16, on Celeron 700MHz mysql version 3.23.22 Here is the script: ( cat EOF connect test; create table test (i numeric(4), j numeric(4)); insert into test (i,j) values (1, 1); insert into test (i,j) values (1, 2); insert into test (i,j) values (1, 3); insert into test (i,j) values (2, 1); insert into test (i,j) values (2, 2); select * from test; select i, min(j), max(j) from test group by i; EOF ) | mysql -p and here is the result: i j 1 1 1 2 1 3 2 1 2 2 i min(j) max(j) 1 0 3 2 0 2 the interesting part is that if I replace create table test (i numeric(4), j numeric(4)) with create table test (i integer, j integer) , then the result is ok We have tested this script on another machine with Pentium 100MHz and RH7.0, and the result is the same. I hope this bug report will be usefull. Looking forward for your reply, - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
Re: bug report
That is pretty old. 3.23.38 works fine. Tarog Adrian wrote: Hello, I think me and my fellows here at office, found a bug in mysql. The system is: RedHat 7.0, kernel 2.2.16, on Celeron 700MHz mysql version 3.23.22 Here is the script: ( cat EOF connect test; create table test (i numeric(4), j numeric(4)); insert into test (i,j) values (1, 1); insert into test (i,j) values (1, 2); insert into test (i,j) values (1, 3); insert into test (i,j) values (2, 1); insert into test (i,j) values (2, 2); select * from test; select i, min(j), max(j) from test group by i; EOF ) | mysql -p and here is the result: i j 1 1 1 2 1 3 2 1 2 2 i min(j) max(j) 1 0 3 2 0 2 the interesting part is that if I replace create table test (i numeric(4), j numeric(4)) with create table test (i integer, j integer) , then the result is ok We have tested this script on another machine with Pentium 100MHz and RH7.0, and the result is the same. I hope this bug report will be usefull. Looking forward for your reply, Adrian Tarog System Engineer SC JOLIDON SRL - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php -- Gerald L. Clark [EMAIL PROTECTED] - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
Re: Bug Report: 3.23.37: Innobase crashes on large table
Thanks for the hint. I'll try it with more tablespace. The indexes have been optimized pretty much. I have to check whether I can send you the table layout. Just for your information. 3.23.38 has the same problem. Heikki Tuuri wrote: Frank, there is obviously a bug in the insert buffer code of InnoDB. I will look into it. The assertion failure indicates that there was not enough free space on an index record page for a record cached in the insert buffer. Your log files are ok. The size of log files does not constrain the size of an InnoDB transaction. The constraint is the size of your tablespace. When I look at your table size I suspect that InnoDB has run out of file space during the table load. You have 27 indexes on the table and InnoDB does not do any index compression. The size of an index record in InnoDB is the size of the primary key + the size of the index columns + 6 bytes additional overhead. In addition, B-tree pages are typically only 70 % full. During a large import also the rollback segment takes space in the tablespace. 7 million * 30 bytes * 1.5 = 300 MB. 27 * 300 MB = 8 GB. It is probable that you ran out of tablespace. You should make your tablspace bigger and monitor with SHOW TABLE STATUS how much space InnoDB uses. (See the InnoDB manual at www.innobase.fi). Some suggestions: do not create indexes whose selectivity is small: for example if a column can have only 2 different values, it usually does not pay to create an index. If you have a primary key of length 6 bytes, create a primary key to the table. If the length of the primary key is 10 bytes, try creating the table without a primary key. Try loading the table a part at a time. You may create an InnoDB table with same definitions as the MyISAM table. Then do several INSERT INTO innodbtable SELECT myisamtable WHERE yourkey something AND yourkey something-else; If you could email me the CREATE TABLE you use for the InnoDB table, it would be easier for me to track the insert buffer bug. Regards, Heikki Tuuri Innobase Oy --=-jUldtxkxbNmI4+gJVNJEContent-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi, I'm trying to load a large table with 7 million records, 50 columns and 27 indexes into an innodb table. Works fine for MyISAM. Compressed size of the data file is about 280MB (830MB uncompressed) and 1.5 GB for the index file. Platform is RedHat Linux 6.2 with kernel 2.2.16-3 and MySQL is 3.23.37 compiled with egcs-2.91.66 for i686 from the standard MySQL source RPM. The machine is a dual CPU Pentium machine with 512 MB RAM and 2 IDE drives (30GB and 40GB). For the InnoDB tables I have 6 data files with 1GB on 2 disks and 3 log files a 50MB. I've also tried it with 5 log files a 1.5GB.From /etc/my.cnf: # # Innobase options#innodb_data_file_path =3D vol1/ibdata/ibdata00:1024M;vol2/ibdata/ibdata01:1024M;vol1/ibdata/ibdat= a02:1024M;vol2/ibdata/ibdata03:1024M;vol1/ibdata/ibdata04:1024M;vol2/ibdata= /ibdata05:1024Minnodb_data_home_dir =3D / set-variable =3D innodb_mirrored_log_groups=3D1 innodb_log_group_home_dir =3D /vol2/iblogs set-variable =3D innodb_log_files_in_group=3D3 set-variable =3D innodb_log_file_size=3D50M set-variable =3D innodb_log_buffer_size=3D8M innodb_flush_log_at_trx_commit=3D1innodb_log_arch_dir =3D /vol2/iblogs innodb_log_archive=3D0set-variable =3D innodb_buffer_pool_size=3D400M set-variable =3D innodb_additional_mem_pool_size=3D20M set-variable =3D innodb_file_io_threads=3D4 set-variable =3D innodb_lock_wait_timeout=3D50 Tried to load it with LOAD DATA INFILE from a FIFO and to convert it from a MyISAM table with ALTER TABLE foo TYPE=3Dinnodb;. Both produced the same result.After some time MySQL dies and then the rollback begins. This is what I see in the .err file: Innobase: Assertion failure in thread 3076 in file ibuf0ibuf.c line2264 Innobase: we intentionally generate a memory trap. Innobase: Send a bug report to [EMAIL PROTECTED] mysqld got signal 11; The manual section 'Debugging a MySQL server' tells you how to use a stack trace and/or the core file to produce a readable backtrace that may help in finding out why mysqld died. Attempting backtrace. You can use the following information to findout where mysqld died. If you see no messages after this, somethingwent terribly wrong... Cannot determine thread, ebp=3D0xbf3ff070, backtrace may not becorrect. Stack range sanity check OK, backtrace follows:0x823244a0x81700fb 0x8170a1e0x81a59890x81c13a80x81600060x82308560x825736a New value of ebp failed sanity check, terminating backtrace! Ibuf insert fails; page free 26, dtuple size 28Bitmap bits 3 Is there a way of turning the transactional logging off during the load of a table? I know that I'm out on my own then but this table is loaded only every once in a
Re: Bug Report: 3.23.37: Innobase crashes on large table
On Wed, May 16, 2001 at 10:58:18PM +0200, Frank Schroeder wrote: Is there a way of turning the transactional logging off during the load of a table? I know that I'm out on my own then but this table is loaded only every once in a while. Am I running out of space on the log/or data files? If InnoDB doesn't already handle this, it's probably a good idea not to run ALTER TABLE as a big transaction. It's slow and probably not necessary. I ran across this with Gemini testing, and NuSphere modified things so that ALTER TABLEs don't hit the recover log anymore. (After all, what use is a half altered table?) InnoDB, however, may be sufficiently different (with mutli-versioning) that it's not as much of an issue. Jeremy -- Jeremy D. Zawodny, [EMAIL PROTECTED] Technical Yahoo - Yahoo Finance Desk: (408) 349-7878Fax: (408) 349-5454Cell: (408) 439-9951 MySQL 3.23.29: up 133 days, processed 825,899,259 queries (71/sec. avg) - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
Re: Bug report
Oops, I read the file size wrong in the printout. It was only 300 MB. Then we can suspect that you ran out of disk space. But knowing the MySQL version would help. Regards, Heikki ... Eugene, does your operating system support over 2 GB files? Which MySQL version you are running? What is the opeerating system? I guess the problem is that the OS does not support over 2 GB files. You should create smaller data files. I will add to os0file.c a more informative error message than an assertion failure :). Regards, Heikki http://www.innobase.fi InnoDB: The first specified data file /space/work1/karpov/data/ibdata1 did not exist:InnoDB: a new database to be created! InnoDB: Setting file /space/work1/karpov/data/ibdata1 size to 26214400 InnoDB: Database physically writes the file full: wait... InnoDB: Data file /space/work1/karpov/data/ibdata2 did not exist: new to be createdInnoDB: Setting file /space/work1/karpov/data/ibdata2 size to 38797312 InnoDB: Database physically writes the file full: wait... InnoDB: Data file /space/work1/karpov/data/ibdata3 did not exist: new to be created InnoDB: Setting file /space/work1/karpov/data/ibdata3 size to 104857600 InnoDB: Database physically writes the file full: wait... InnoDB: Data file /space/work1/karpov/data/ibdata4 did not exist: new to be created InnoDB: Setting file /space/work1/karpov/data/ibdata4 size to 314572800 InnoDB: Database physically writes the file full: wait... Innobase: Assertion failure in thread 1 in file os0file.c line 205 Innobase: we intentionally generate a memory trap. Innobase: Send a bug report to [EMAIL PROTECTED] mysqld got signal 11; The manual section 'Debugging a MySQL server' tells you how to use a stack trace and/or the core file to produce a readable backtrace that may help in finding out why mysqld died. B.R. Eugene - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
Re: Bug report
Max file size is 300M, not 2G. Isn't it? B.R. Eugene On Tue, 15 May 2001, Heikki Tuuri wrote: Eugene, does your operating system support over 2 GB files? Which MySQL version you are running? What is the opeerating system? I guess the problem is that the OS does not support over 2 GB files. You should create smaller data files. I will add to os0file.c a more informative error message than an assertion failure :). Regards, Heikki http://www.innobase.fi InnoDB: The first specified data file /space/work1/karpov/data/ibdata1 did not exist:InnoDB: a new database to be created! InnoDB: Setting file /space/work1/karpov/data/ibdata1 size to 26214400 InnoDB: Database physically writes the file full: wait... InnoDB: Data file /space/work1/karpov/data/ibdata2 did not exist: new to be createdInnoDB: Setting file /space/work1/karpov/data/ibdata2 size to 38797312 InnoDB: Database physically writes the file full: wait... InnoDB: Data file /space/work1/karpov/data/ibdata3 did not exist: new to be created InnoDB: Setting file /space/work1/karpov/data/ibdata3 size to 104857600 InnoDB: Database physically writes the file full: wait... InnoDB: Data file /space/work1/karpov/data/ibdata4 did not exist: new to be created InnoDB: Setting file /space/work1/karpov/data/ibdata4 size to 314572800 InnoDB: Database physically writes the file full: wait... Innobase: Assertion failure in thread 1 in file os0file.c line 205 Innobase: we intentionally generate a memory trap. Innobase: Send a bug report to [EMAIL PROTECTED] mysqld got signal 11; The manual section 'Debugging a MySQL server' tells you how to use a stack trace and/or the core file to produce a readable backtrace that may help in finding out why mysqld died. B.R. Eugene B.R. Eugene - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
Re: Bug report
mysql Ver 11.15 Distrib 3.23.37, for sun-solaris2.7 (sparc) SunOS 5.7 Generic_106541-02 sun4u sparc SUNW,Ultra-5_10 On Tue, 15 May 2001, Heikki Tuuri wrote: Hi! Ok, the error turned out to be out of disk space. But for some reason the error handling code in os0file.c did not recognize the error number given by the operating system, it tests for ENOSPC. I will change the error handling code so that it prints the operating system error message number and does not assert. It still would be very helpful if you told the operating system and MySQL versions. Regards, Heikki http://www.innobase.fi At 06:00 PM 5/15/01 +0400, you wrote: Max file size is 300M, not 2G. Isn't it? B.R. Eugene On Tue, 15 May 2001, Heikki Tuuri wrote: Eugene, does your operating system support over 2 GB files? Which MySQL version you are running? What is the opeerating system? I guess the problem is that the OS does not support over 2 GB files. You should create smaller data files. I will add to os0file.c a more informative error message than an assertion failure :). Regards, Heikki http://www.innobase.fi InnoDB: The first specified data file /space/work1/karpov/data/ibdata1 did not exist:InnoDB: a new database to be created! InnoDB: Setting file /space/work1/karpov/data/ibdata1 size to 26214400 InnoDB: Database physically writes the file full: wait... InnoDB: Data file /space/work1/karpov/data/ibdata2 did not exist: new to be createdInnoDB: Setting file /space/work1/karpov/data/ibdata2 size to 38797312 InnoDB: Database physically writes the file full: wait... InnoDB: Data file /space/work1/karpov/data/ibdata3 did not exist: new to be created InnoDB: Setting file /space/work1/karpov/data/ibdata3 size to 104857600 InnoDB: Database physically writes the file full: wait... InnoDB: Data file /space/work1/karpov/data/ibdata4 did not exist: new to be created InnoDB: Setting file /space/work1/karpov/data/ibdata4 size to 314572800 InnoDB: Database physically writes the file full: wait... Innobase: Assertion failure in thread 1 in file os0file.c line 205 Innobase: we intentionally generate a memory trap. Innobase: Send a bug report to [EMAIL PROTECTED] mysqld got signal 11; The manual section 'Debugging a MySQL server' tells you how to use a stack trace and/or the core file to produce a readable backtrace that may help in finding out why mysqld died. B.R. Eugene B.R. Eugene B.R. Eugene - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
Re: bug report
Hi Try select from_days(to_days(curdate())-1); +-+ | from_days(to_days(curdate())-1) | +-+ | 2001-04-30 | +-+ 1 row in set (0.00 sec) Simon On Tuesday 01 May 2001 14:45, Aurelian Dumitru wrote: Please record the following bug identified on the MySQL server: 1. Hardware: SUN Ultra 10 2. Operating system: Sun Solaris 2.7 2. MySQL server version: 3.23.33 3. Error description: - The following SQL statement returns incorrect results when is executed using the 'mysql' client: SELECT @myvar := ( CURRENT_DATE - 1) ; - I ran this query every day. It worked fine untill May 1st, 2001, when the above query returned the following value: 20010500 . It should have returned 20010430. Aurelian Dumitru [EMAIL PROTECTED] - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php -- Simon Windsor CricInfo http://www.cricinfo.com/ Tel: +44 (0) 1249 700744 Fax: +44 (0) 1249 700725 Email: mailto:[EMAIL PROTECTED] This email message is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message. Thank you for your cooperation and assistance. - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
Re: bug report
Aurelian Dumitru [EMAIL PROTECTED] wrote: Please record the following bug identified on the MySQL server: 1. Hardware: SUN Ultra 10 2. Operating system: Sun Solaris 2.7 2. MySQL server version: 3.23.33 3. Error description: - The following SQL statement returns incorrect results when is executed using the 'mysql' client: SELECT @myvar := ( CURRENT_DATE - 1) ; - I ran this query every day. It worked fine untill May 1st, 2001 I gues every day didn't include April 1, 2001 b/c that won't work either. , when the above query returned the following value: 20010500 . It should have returned 20010430. No, it returned the right value. current_date returns a date of the format '2001-05-01'. When you do arithmetic on it, it's converted to an integer. 20010501 - 1 = 20010500 so it gave the currect value. If you want to subtract one day from a date do this: SELECT DATE_SUB( current_date, INTERVAL 1 DAY ); -- Steve Werby President, Befriend Internet Services LLC http://www.befriend.com/ - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
Re: bug report
For over a year the topic of mathematical operations on date values
has been disussed. It has never been possible to perform such math
on a date value without using DATE_ADD or converting the to days or
seconds first.
Why is this now all the sudden a reasonable bug?
Aurelian:
I suggest that you use DATE_ADD, I'm quite sure what you have found
is not a bug
20010501 - 1 = 20010500
MySQL sees CURRENT_DATE as the value 20010501 and performs your subtraction
as requested, if you want to subtract a day from today I suggest
DATE_ADD( CURRENT_DATE, INTERVAL -1 DAY )
Or the previously suggested TO_DAYS, FROM_DAYS method.
Sinisa Milivojevic wrote:
Aurelian Dumitru writes:
Please record the following bug identified on the MySQL server:
1. Hardware: SUN Ultra 10
2. Operating system: Sun Solaris 2.7
2. MySQL server version: 3.23.33
3. Error description:
- The following SQL statement returns incorrect results when is executed
using the 'mysql' client: SELECT @myvar := ( CURRENT_DATE - 1) ;
- I ran this query every day. It worked fine untill May 1st, 2001, when the
above query returned the following value: 20010500 . It should have returned
20010430.
Aurelian Dumitru
[EMAIL PROTECTED]
Hi!
Thank you for a repeatable bug report.
Regards,
Sinisa
__ _ _ ___ == MySQL AB
/*/\*\/\*\ /*/ \*\ /*/ \*\ |*| Sinisa Milivojevic
/*/ /*/ /*/ \*\_ |*| |*||*| mailto:[EMAIL PROTECTED]
/*/ /*/ /*/\*\/*/ \*\|*| |*||*| Larnaca, Cyprus
/*/ /*/ /*/\*\_/*/ \*\_/*/ |*|
/*/^^^\*\^^^
/*/ \*\Developers Team
-
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
http://lists.mysql.com/ (the list archive)
To request this thread, e-mail [EMAIL PROTECTED]
To unsubscribe, e-mail [EMAIL PROTECTED]
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
-
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
http://lists.mysql.com/ (the list archive)
To request this thread, e-mail [EMAIL PROTECTED]
To unsubscribe, e-mail [EMAIL PROTECTED]
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
Re: bug report
Steve Ruby writes:
For over a year the topic of mathematical operations on date values
has been disussed. It has never been possible to perform such math
on a date value without using DATE_ADD or converting the to days or
seconds first.
Why is this now all the sudden a reasonable bug?
Aurelian:
I suggest that you use DATE_ADD, I'm quite sure what you have found
is not a bug
20010501 - 1 = 20010500
MySQL sees CURRENT_DATE as the value 20010501 and performs your subtraction
as requested, if you want to subtract a day from today I suggest
DATE_ADD( CURRENT_DATE, INTERVAL -1 DAY )
Or the previously suggested TO_DAYS, FROM_DAYS method.
You are right, of course !
Regards,
Sinisa
__ _ _ ___ == MySQL AB
/*/\*\/\*\ /*/ \*\ /*/ \*\ |*| Sinisa Milivojevic
/*/ /*/ /*/ \*\_ |*| |*||*| mailto:[EMAIL PROTECTED]
/*/ /*/ /*/\*\/*/ \*\|*| |*||*| Larnaca, Cyprus
/*/ /*/ /*/\*\_/*/ \*\_/*/ |*|
/*/^^^\*\^^^
/*/ \*\Developers Team
-
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
http://lists.mysql.com/ (the list archive)
To request this thread, e-mail [EMAIL PROTECTED]
To unsubscribe, e-mail [EMAIL PROTECTED]
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
Re: bug report
Hello Aurelian, I do the same thing but use the following code and it works fine. SELECT @myvar := DATE_SUB( CURRENT_DATE, INTERVAL 1 DAY) ; Edward 5/1/2001 6:45:19 AM, Aurelian Dumitru [EMAIL PROTECTED] wrote: Please record the following bug identified on the MySQL server: 1. Hardware: SUN Ultra 10 2. Operating system: Sun Solaris 2.7 2. MySQL server version: 3.23.33 3. Error description: - The following SQL statement returns incorrect results when is executed using the 'mysql' client: SELECT @myvar := ( CURRENT_DATE - 1) ; - I ran this query every day. It worked fine untill May 1st, 2001, when the above query returned the following value: 20010500 . It should have returned 20010430. Aurelian Dumitru [EMAIL PROTECTED] - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
Re: bug report
Andrew Schmidt writes:
Description:
tough one to describe. the step by step example shows all
basicly once a table gets more than 1 row and doing a select with no
result will yield a blank date... gah please see the example =)
How-To-Repeat:
create database tmpdb;
use tmpdb;
create table test (foo int);
insert into test values (1);
select NOW(), count(*) from test where foo in (2);
+-+--+
| NOW() | count(*) |
+-+--+
| 2001-04-20 17:21:29 |0 |
+-+--+
insert into test values (1);
select NOW(), count(*) from test where foo in (2);
+---+--+
| NOW() | count(*) |
+---+--+
| |0 |
+---+--+
notice the date field is blank.
Fix:
how to correct or work around the problem, if known (multiple lines)
Submitter-Id: submitter ID
Originator:Andrew Schmidt
Organization:
organization of PR author (multiple lines)
MySQL support: [none | licence | email support | extended email support ]
Synopsis: synopsis of the problem (one line)
Severity: [ non-critical | serious | critical ] (one line)
Priority: [ low | medium | high ] (one line)
Category: mysql
Class: [ sw-bug | doc-bug | change-request | support ] (one line)
Release: mysql-3.23.37 (Source distribution)
Environment:
machine, os, target, libraries (multiple lines)
System: FreeBSD wrk-112.tor1.targetnet.pvt 4.2-STABLE-20010112-JPSNAP
FreeBSD 4.
2-STABLE-20010112-JPSNAP #0: Thu Jan 11 20:06:54 GMT 2001
[EMAIL PROTECTED]
reebsd.org:/usr/src/sys/compile/GENERIC i386
Some paths: /usr/bin/perl /usr/bin/make /usr/local/bin/gmake /usr/bin/gcc
/usr/
bin/cc
GCC: Using builtin specs.
gcc version 2.95.2 19991024 (release)
Compilation info: CC='gcc' CFLAGS='' CXX='c++' CXXFLAGS='' LDFLAGS=''
LIBC:
-r--r--r-- 1 root wheel 1169222 Jan 11 14:28 /usr/lib/libc.a
lrwxrwxrwx 1 root wheel 9 Jan 19 13:01 /usr/lib/libc.so - libc.so.4
-r--r--r-- 1 root wheel 559420 Jan 11 14:28 /usr/lib/libc.so.4
Configure command:
./configure --localstatedir=/usr/local/var/db/mysql --withou
t-perl --without-debug --without-readline --without-bench --enable-assembler
--e
nable-thread-safe-client
Perl: This is perl, version 5.005_03 built for i386-freebsd
Hi!
Thank you for a repeatable bug report.
Regards,
Sinisa
__ _ _ ___ == MySQL AB
/*/\*\/\*\ /*/ \*\ /*/ \*\ |*| Sinisa Milivojevic
/*/ /*/ /*/ \*\_ |*| |*||*| mailto:[EMAIL PROTECTED]
/*/ /*/ /*/\*\/*/ \*\|*| |*||*| Larnaca, Cyprus
/*/ /*/ /*/\*\_/*/ \*\_/*/ |*|
/*/^^^\*\^^^
/*/ \*\Developers Team
-
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
http://lists.mysql.com/ (the list archive)
To request this thread, e-mail [EMAIL PROTECTED]
To unsubscribe, e-mail [EMAIL PROTECTED]
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
Re: bug report
Verified. this is a bug empty table or 1 record returns expected result, insert one more record and the result of now() is empty. mysql select now(), count(*) from t where a in (2); | now() | count(*) | | 2001-04-21 08:12:03 |0 | 1 row in set (0.00 sec) mysql insert into t (a) values (1); mysql select now(), count(*) from t where a in (2); | now() | count(*) | | |0 | 1 row in set (0.01 sec) verified on version 3.23.32-debug (w2k) binary. - Original Message - From: "Andrew Schmidt" [EMAIL PROTECTED] To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Friday, April 20, 2001 11:31 PM Subject: bug report Description: tough one to describe. the step by step example shows all basicly once a table gets more than 1 row and doing a select with no result will yield a blank date... gah please see the example =) How-To-Repeat: create database tmpdb; use tmpdb; create table test (foo int); insert into test values (1); select NOW(), count(*) from test where foo in (2); +-+--+ | NOW() | count(*) | +-+--+ | 2001-04-20 17:21:29 |0 | +-+--+ insert into test values (1); select NOW(), count(*) from test where foo in (2); +---+--+ | NOW() | count(*) | +---+--+ | |0 | +---+--+ notice the date field is blank. Fix: how to correct or work around the problem, if known (multiple lines) Submitter-Id: submitter ID Originator:Andrew Schmidt Organization: organization of PR author (multiple lines) MySQL support: [none | licence | email support | extended email support ] Synopsis: synopsis of the problem (one line) Severity: [ non-critical | serious | critical ] (one line) Priority: [ low | medium | high ] (one line) Category: mysql Class: [ sw-bug | doc-bug | change-request | support ] (one line) Release: mysql-3.23.37 (Source distribution) Environment: machine, os, target, libraries (multiple lines) System: FreeBSD wrk-112.tor1.targetnet.pvt 4.2-STABLE-20010112-JPSNAP FreeBSD 4. 2-STABLE-20010112-JPSNAP #0: Thu Jan 11 20:06:54 GMT 2001 [EMAIL PROTECTED] reebsd.org:/usr/src/sys/compile/GENERIC i386 Some paths: /usr/bin/perl /usr/bin/make /usr/local/bin/gmake /usr/bin/gcc /usr/ bin/cc GCC: Using builtin specs. gcc version 2.95.2 19991024 (release) Compilation info: CC='gcc' CFLAGS='' CXX='c++' CXXFLAGS='' LDFLAGS='' LIBC: -r--r--r-- 1 root wheel 1169222 Jan 11 14:28 /usr/lib/libc.a lrwxrwxrwx 1 root wheel 9 Jan 19 13:01 /usr/lib/libc.so - libc.so.4 -r--r--r-- 1 root wheel 559420 Jan 11 14:28 /usr/lib/libc.so.4 Configure command: ./configure --localstatedir=/usr/local/var/db/mysql --withou t-perl --without-debug --without-readline --without-bench --enable-assembler --e nable-thread-safe-client Perl: This is perl, version 5.005_03 built for i386-freebsd - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
Re: bug report - docs
On Sun, Apr 08, 2001 at 12:22:32PM -0500, Rodrigo Zerlotti wrote: Description: INSTALL-BIN file has errors: shell chown -R mysql /usr/local/mysql/var it should be chown -R mysql /usr/local/mysql/data instead "var" Thanks, Rodrigo. I have fixed it now. Tim -- __ ___ ___ __ / |/ /_ __/ __/ __ \/ /Tim Smith [EMAIL PROTECTED] / /|_/ / // /\ \/ /_/ / /__ MySQL AB, Development Team /_/ /_/\_, /___/\___\_\___/ Boone, NC USA ___/ www.mysql.com - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
Re: Bug Report -- Stack Trace Necessary
Daren Cotter writes:
Sorry to post AGAIN, but I have new info. I was monitoring the Error Log,
and when I run the query that crashes MySQL, I get the following error:
mysqld got signal 11;
The manual section 'Debugging a MySQL server' tells you how to use a
stack trace and/or the core file to produce a readable backtrace that may
help in finding out why mysqld died
Attemping backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong
stack range sanity check, ok, backtrace follows
0x4008407e
0x8098525
0x80972ba
0x808c6b3
0x80aa19b
0x80d7c73
0x80d6b17
0x80cf2da
0x80b5e6b
0x80b9015
0x80b52d3
0x80b4949
stack trace successful
Number of processes running now: 0
010312 19:08:50 mysqld restarted
/usr/libexec/mysqld: ready for connections
I attempted to run my own Stack Trace, but when I try to create a symbol
file like the manual says, I get an error:
%: nm -n libexec/mysqld /tmp/mysqld.sym
nm: /usr/libexec/mysqld: no symbols
I'm really on ends with this. The only thing I can possibly think it may be,
is that on my previous server, the table types were ISAM, and on the new
server, the table types are MyISAM. I notice the error on queries that work
with the TIMESTAMP field, so is there possibly some incompatibility with
this, and if so, how can I fix it?
This is one query that is causing the error:
SELECT (lots of info that is not causing error),
CONCAT(SUBSTRING(MONTHNAME(signup_date),1,3), ' ', DAYOFMONTH(signup_date),
', ', YEAR(signup_date)) as signup_date,
CONCAT(SUBSTRING(MONTHNAME(last_update),1,3), ' ', DAYOFMONTH(last_update),
', ', YEAR(last_update), ' ', HOUR(last_update), ':', MINUTE(last_update))
AS last_update, CONCAT(SUBSTRING(MONTHNAME(last_login),1,3), ' ',
DAYOFMONTH(last_login), ', ', YEAR(last_login), ' ', HOUR(last_login), ':',
MINUTE(last_login)) AS last_login, (more info not causing error) FROM
members WHERE member_id = 10010
I know that certain info is not causing the error, as I modified the query
and it worked fine.
Hi!
If running the above query always causes segmentation fault, please
upload your members MyISAM table (xipped), with the above query to :
ftp://support.mysql.com/pub/mysql/Incoming
so that we can test it.
Many thanks in advance.
Regards,
Sinisa
__ _ _ ___ == MySQL AB
/*/\*\/\*\ /*/ \*\ /*/ \*\ |*| Sinisa Milivojevic
/*/ /*/ /*/ \*\_ |*| |*||*| mailto:[EMAIL PROTECTED]
/*/ /*/ /*/\*\/*/ \*\|*| |*||*| Larnaca, Cyprus
/*/ /*/ /*/\*\_/*/ \*\_/*/ |*|
/*/^^^\*\^^^
/*/ \*\Developers Team
-
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
http://lists.mysql.com/ (the list archive)
To request this thread, e-mail [EMAIL PROTECTED]
To unsubscribe, e-mail [EMAIL PROTECTED]
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
