BUG:ALTER TABLE (MySQL 4.1)

am 24.01.2003 19:49:01 von Gelu Gogancea

Hi,
I guess is as a bug in ALTER TABLE with MySQL 4.1,compiled from BK TREE on
2003-01-22.
Table schema :
CREATE TABLE cmdlivrare(IDCMD INT(9) NOT NULL PRIMARY KEY DEFAULT 2000,mUser
CHAR(16),Dep CHAR(4),IDCLI INT(16),FactExt CHAR(20),LivrFinish
SMALLINT(1),DataIntro DATE,DataIese
DATE,INDEX(Dep),INDEX(FactExt),INDEX(IDCLI),INDEX(mUser),IND EX(LivrFinish),I
NDEX(DataIntro),INDEX(DataIese));

I wish to alter this table and modify the definition of IDCMD to "IDCMD
INT(9) AUTO_INCREMENT NOT NULL PRIMARY KEY DEFAULT 30000"
For this i do :
alter table cmdlivrare modify IDCMD INT(9) AUTO_INCREMENT NOT NULL PRIMARY
KEY DEFAULT 30000;

MySQL daemon got signal 11.

MySQL log "said":
============================================================ ================
=================================
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=402653184
read_buffer_size=2093056
sort_buffer_size=2097144
max_used_connections=0
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 =
802415 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

thd=0x865b0a0
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=0xbe7fd6f8, backtrace may not be correct.
Stack range sanity check OK, backtrace follows:
0x8114078
0x40039951
0x816785a
0x8167167
0x81807ac
0x8182370
0x8121257
0x8124c45
0x811f8a7
0x811f4fe
0x811ee79
0x4003376e
0x402687da
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 0x865e3c8 = alter table cmdlivrare modify IDCMD INT(9)
AUTO_INCREMENT NOT NULL PRIMARY KEY DEFAULT 30000
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, 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.
============================================================ ================
=================================

resolve_stack_dump succesfully does :

0x8114078 handle_segfault + 416
0x40039951 _end + 936099857
0x816785a _Z11pack_fieldsiR4ListI12create_fieldE + 170
0x8167167
_Z16rea_create_tableP3THDPcP24st_ha_create_informationR4List I12create_fieldE
jP6st_key + 883
0x81807ac
_Z18mysql_create_tableP3THDPKcS2_P24st_ha_create_information R4ListI12create_
fieldERS5_I3KeyEbbj + 2500
0x8182370
_Z17mysql_alter_tableP3THDPcS1_P24st_ha_create_informationP1 3st_table_listR4
ListI12create_fieldERS6_I3KeyERS6_I10Alter_dropERS6 + 2736
0x8121257 _Z21mysql_execute_commandP3THD + 2803
0x8124c45 _Z11mysql_parseP3THDPcj + 221
0x811f8a7 _Z16dispatch_command19enum_server_commandP3THDPcj + 879
0x811f4fe _Z10do_commandP3THD + 110
0x811ee79 handle_one_connection + 813
0x4003376e _end + 936074798
0x402687da _end + 938389146

I has the bad inspiration to compile without debug option.I try to recompile
now and i will try to study to see what happened.

Regards,

Gelu
_____________________________________________________
G.NET SOFTWARE COMPANY

Permanent e-mail address : gg@gonetsoftware.com
gelugogancea@yahoo.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
To unsubscribe, e-mail
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php

Re: BUG:ALTER TABLE (MySQL 4.1)

am 24.01.2003 21:07:30 von Gelu Gogancea

....like usually i forget some details:
Table type is MyISAM and was created with MySQL ver 3.23.47
But if i create the table with ver.4.1 the behaviour is the same.

Regards,

Gelu
_____________________________________________________
G.NET SOFTWARE COMPANY

Permanent e-mail address : gg@gonetsoftware.com
gelugogancea@yahoo.com
----- Original Message -----
From: "Gelu Gogancea"
To: ;
Sent: Friday, January 24, 2003 8:49 PM
Subject: BUG:ALTER TABLE (MySQL 4.1)

> Hi,
> I guess is as a bug in ALTER TABLE with MySQL 4.1,compiled from BK TREE on
> 2003-01-22.
> Table schema :
> CREATE TABLE cmdlivrare(IDCMD INT(9) NOT NULL PRIMARY KEY DEFAULT
2000,mUser
> CHAR(16),Dep CHAR(4),IDCLI INT(16),FactExt CHAR(20),LivrFinish
> SMALLINT(1),DataIntro DATE,DataIese
>
DATE,INDEX(Dep),INDEX(FactExt),INDEX(IDCLI),INDEX(mUser),IND EX(LivrFinish),I
> NDEX(DataIntro),INDEX(DataIese));
>
> I wish to alter this table and modify the definition of IDCMD to "IDCMD
> INT(9) AUTO_INCREMENT NOT NULL PRIMARY KEY DEFAULT 30000"
> For this i do :
> alter table cmdlivrare modify IDCMD INT(9) AUTO_INCREMENT NOT NULL
PRIMARY
> KEY DEFAULT 30000;
>
> MySQL daemon got signal 11.
>
> MySQL log "said":
>
============================================================ ================
> =================================
> 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=402653184
> read_buffer_size=2093056
> sort_buffer_size=2097144
> max_used_connections=0
> 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 =
> 802415 K
> bytes of memory
> Hope that's ok; if not, decrease some variables in the equation.
>
> thd=0x865b0a0
> 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=0xbe7fd6f8, backtrace may not be correct.
> Stack range sanity check OK, backtrace follows:
> 0x8114078
> 0x40039951
> 0x816785a
> 0x8167167
> 0x81807ac
> 0x8182370
> 0x8121257
> 0x8124c45
> 0x811f8a7
> 0x811f4fe
> 0x811ee79
> 0x4003376e
> 0x402687da
> 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 0x865e3c8 = alter table cmdlivrare modify IDCMD INT(9)
> AUTO_INCREMENT NOT NULL PRIMARY KEY DEFAULT 30000
> 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, 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.
>
============================================================ ================
> =================================
>
> resolve_stack_dump succesfully does :
>
> 0x8114078 handle_segfault + 416
> 0x40039951 _end + 936099857
> 0x816785a _Z11pack_fieldsiR4ListI12create_fieldE + 170
> 0x8167167
>
_Z16rea_create_tableP3THDPcP24st_ha_create_informationR4List I12create_fieldE
> jP6st_key + 883
> 0x81807ac
>
_Z18mysql_create_tableP3THDPKcS2_P24st_ha_create_information R4ListI12create_
> fieldERS5_I3KeyEbbj + 2500
> 0x8182370
>
_Z17mysql_alter_tableP3THDPcS1_P24st_ha_create_informationP1 3st_table_listR4
> ListI12create_fieldERS6_I3KeyERS6_I10Alter_dropERS6 + 2736
> 0x8121257 _Z21mysql_execute_commandP3THD + 2803
> 0x8124c45 _Z11mysql_parseP3THDPcj + 221
> 0x811f8a7 _Z16dispatch_command19enum_server_commandP3THDPcj + 879
> 0x811f4fe _Z10do_commandP3THD + 110
> 0x811ee79 handle_one_connection + 813
> 0x4003376e _end + 936074798
> 0x402687da _end + 938389146
>
>
> I has the bad inspiration to compile without debug option.I try to
recompile
> now and i will try to study to see what happened.
>
> Regards,
>
> Gelu
> _____________________________________________________
> G.NET SOFTWARE COMPANY
>
> Permanent e-mail address : gg@gonetsoftware.com
> gelugogancea@yahoo.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
To unsubscribe, e-mail
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php

Re: BUG:ALTER TABLE (MySQL 4.1)

am 25.01.2003 01:22:04 von Georg Richter

On Friday 24 January 2003 19:49, Gelu Gogancea wrote:
> Hi,
> I guess is as a bug in ALTER TABLE with MySQL 4.1,compiled from BK TREE on
> 2003-01-22.
> Table schema :
> CREATE TABLE cmdlivrare(IDCMD INT(9) NOT NULL PRIMARY KEY DEFAULT
> 2000,mUser CHAR(16),Dep CHAR(4),IDCLI INT(16),FactExt CHAR(20),LivrFinish
> SMALLINT(1),DataIntro DATE,DataIese
> DATE,INDEX(Dep),INDEX(FactExt),INDEX(IDCLI),INDEX(mUser),IND EX(LivrFinish),
>I NDEX(DataIntro),INDEX(DataIese));
>
> I wish to alter this table and modify the definition of IDCMD to "IDCMD
> INT(9) AUTO_INCREMENT NOT NULL PRIMARY KEY DEFAULT 30000"
> For this i do :
> alter table cmdlivrare modify IDCMD INT(9) AUTO_INCREMENT NOT NULL PRIMARY
> KEY DEFAULT 30000;
>
> MySQL daemon got signal 11.

Hi,

Just tested it with latest bk pull, and it doesn't crash.
It displays correctly the error "Multiple primary key defined" for the alter
table query.

Regards

Georg

------------------------------------------------------------ ---------
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 bugs-thread13579@lists.mysql.com
To unsubscribe, e-mail

Re: BUG:ALTER TABLE (MySQL 4.1)

am 25.01.2003 02:48:14 von Sergei Golubchik

Hi!

On Jan 24, Gelu Gogancea wrote:
> Hi,
> I guess is as a bug in ALTER TABLE with MySQL 4.1,compiled from BK TREE on
> 2003-01-22.
> Table schema :
> CREATE TABLE cmdlivrare(IDCMD INT(9) NOT NULL PRIMARY KEY DEFAULT 2000,mUser
> CHAR(16),Dep CHAR(4),IDCLI INT(16),FactExt CHAR(20),LivrFinish
> SMALLINT(1),DataIntro DATE,DataIese
> DATE,INDEX(Dep),INDEX(FactExt),INDEX(IDCLI),INDEX(mUser),IND EX(LivrFinish),I
> NDEX(DataIntro),INDEX(DataIese));
>
> I wish to alter this table and modify the definition of IDCMD to "IDCMD
> INT(9) AUTO_INCREMENT NOT NULL PRIMARY KEY DEFAULT 30000"
> For this i do :
> alter table cmdlivrare modify IDCMD INT(9) AUTO_INCREMENT NOT NULL PRIMARY
> KEY DEFAULT 30000;

No crash for me on a recent bk tree (Jan 24, that is).
Try a fresh pull.

Regards,
Sergei

--
MySQL Development Team
__ ___ ___ ____ __
/ |/ /_ __/ __/ __ \/ / Sergei Golubchik
/ /|_/ / // /\ \/ /_/ / /__ 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
To unsubscribe, e-mail
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php

Re: BUG:ALTER TABLE (MySQL 4.1)

am 25.01.2003 02:48:14 von Sergei Golubchik

Re: BUG:ALTER TABLE (MySQL 4.1)

am 25.01.2003 13:13:11 von Gelu Gogancea

Hi Sergei,
I just finish to compile the latest source code (Jan 25) from
http://mysql.bkbits.net/mysql-4.1
The problem persist.
Georg has right i was trying to alter table when the primary key was already
defined and i was trying:

ALTER TABLE cmdlivrare MODIFY IDCMD INT(9) AUTO_INCREMENT;

From mysqld.log:
thd=0x865c0e0
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=0xbe7fd7d8, backtrace may not be correct.
Stack range sanity check OK, backtrace follows:
0x8114188
0x40039951
0x8167b06
0x8167413
0x8180a14
0x81825d8
0x812138f
0x8124d7d
0x811f9a7
0x811f612
0x811ef8d
0x4003376e
0x402687da
New value of fp=(nil) failed sanity check, terminating stack trace!
........
Some pointers may be invalid and cause the dump to abort...
thd->query at 0x865f408 = alter table cmdlivrare modify IDCMD INT(9)
AUTO_INCREMENT

....and from resolve_stack_dump:

0x8114188 handle_segfault + 416
0x40039951 _end + 936095697
0x8167b06 _Z11pack_fieldsiR4ListI12create_fieldE + 170
0x8167413
_Z16rea_create_tableP3THDPcP24st_ha_create_informationR4List I12create_fieldE
jP6st_key + 883
0x8180a14
_Z18mysql_create_tableP3THDPKcS2_P24st_ha_create_information R4ListI12create_
fieldERS5_I3KeyEbbj + 2500
0x81825d8
_Z17mysql_alter_tableP3THDPcS1_P24st_ha_create_informationP1 3st_table_listR4
ListI12create_fieldERS6_I3KeyERS6_I10Alter_dropERS6 + 2736
0x812138f _Z21mysql_execute_commandP3THD + 2803
0x8124d7d _Z11mysql_parseP3THDPcj + 221
0x811f9a7 _Z16dispatch_command19enum_server_commandP3THDPcj + 859
0x811f612 _Z10do_commandP3THD + 110
0x811ef8d handle_one_connection + 813
0x4003376e _end + 936070638
0x402687da _end + 938384986

Best regards,

Gelu
_____________________________________________________
G.NET SOFTWARE COMPANY

Permanent e-mail address : gg@gonetsoftware.com
gelugogancea@yahoo.com
----- Original Message -----
From: "Sergei Golubchik"
To: "Gelu Gogancea"
Cc: ;
Sent: Saturday, January 25, 2003 3:48 AM
Subject: Re: BUG:ALTER TABLE (MySQL 4.1)

> Hi!
>
> On Jan 24, Gelu Gogancea wrote:
> > Hi,
> > I guess is as a bug in ALTER TABLE with MySQL 4.1,compiled from BK TREE
on
> > 2003-01-22.
> > Table schema :
> > CREATE TABLE cmdlivrare(IDCMD INT(9) NOT NULL PRIMARY KEY DEFAULT
2000,mUser
> > CHAR(16),Dep CHAR(4),IDCLI INT(16),FactExt CHAR(20),LivrFinish
> > SMALLINT(1),DataIntro DATE,DataIese
> >
DATE,INDEX(Dep),INDEX(FactExt),INDEX(IDCLI),INDEX(mUser),IND EX(LivrFinish),I
> > NDEX(DataIntro),INDEX(DataIese));
> >
> > I wish to alter this table and modify the definition of IDCMD to "IDCMD
> > INT(9) AUTO_INCREMENT NOT NULL PRIMARY KEY DEFAULT 30000"
> > For this i do :
> > alter table cmdlivrare modify IDCMD INT(9) AUTO_INCREMENT NOT NULL
PRIMARY
> > KEY DEFAULT 30000;
>
> No crash for me on a recent bk tree (Jan 24, that is).
> Try a fresh pull.
>
> Regards,
> Sergei
>
> --
> MySQL Development Team
> __ ___ ___ ____ __
> / |/ /_ __/ __/ __ \/ / Sergei Golubchik
> / /|_/ / // /\ \/ /_/ / /__ 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
> To unsubscribe, e-mail
> 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
To unsubscribe, e-mail
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php

Re: BUG:ALTER TABLE (MySQL 4.1)

am 25.01.2003 13:13:11 von Gelu Gogancea

Re: BUG:ALTER TABLE (MySQL 4.1)

am 25.01.2003 17:20:41 von Sinisa Milivojevic

Gelu Gogancea writes:
> Hi Sergei,
> I just finish to compile the latest source code (Jan 25) from
> http://mysql.bkbits.net/mysql-4.1
> The problem persist.
> Georg has right i was trying to alter table when the primary key was already
> defined and i was trying:
>
> ALTER TABLE cmdlivrare MODIFY IDCMD INT(9) AUTO_INCREMENT;
>
> >From mysqld.log:
>
> Best regards,
>
> Gelu
> _____________________________________________________
> G.NET SOFTWARE COMPANY
>

Hi!

Was it an empty table ir it had rows.

Was it corrupt prior to being ALTERed ??

Please send us a dump of the table or if it is big, upload it to the
usual place.

--
__ ___ ___ ____ __
/ |/ /_ __/ __/ __ \/ / Mr. Sinisa Milivojevic
/ /|_/ / // /\ \/ /_/ / /__ MySQL AB, Fulltime Developer
/_/ /_/\_, /___/\___\_\___/ Larnaca, Cyprus
<___/ www.mysql.com

Join MySQL Users Conference and Expo:
http://www.mysql.com/events/uc2003/

------------------------------------------------------------ ---------
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 bugs-thread13590@lists.mysql.com
To unsubscribe, e-mail

Re: BUG:ALTER TABLE (MySQL 4.1)

am 25.01.2003 17:20:41 von Sinisa Milivojevic

Re: BUG:ALTER TABLE (MySQL 4.1)

am 25.01.2003 18:28:42 von Gelu Gogancea

Hi Sinisa,
I guess is no need because the problem it's solved now.I don't wish to
happened like the last time...and now, i'm little more carrefully.
You have right.The data on table was corrupt becuase of previous source code
(bk pull on Jan 22).I make ten's of test whith this code based on this
problem.
Today (Jan 25) i make pull again (Sergei suggest me today) and now it work
well after when i fixed the table.

Best regards,

Gelu
_____________________________________________________
G.NET SOFTWARE COMPANY

Permanent e-mail address : gg@gonetsoftware.com
gelugogancea@yahoo.com
----- Original Message -----
From: "Sinisa Milivojevic"
To:
Cc: ; ;
Sent: Saturday, January 25, 2003 6:20 PM
Subject: Re: BUG:ALTER TABLE (MySQL 4.1)

> Gelu Gogancea writes:
> > Hi Sergei,
> > I just finish to compile the latest source code (Jan 25) from
> > http://mysql.bkbits.net/mysql-4.1
> > The problem persist.
> > Georg has right i was trying to alter table when the primary key was
already
> > defined and i was trying:
> >
> > ALTER TABLE cmdlivrare MODIFY IDCMD INT(9) AUTO_INCREMENT;
> >
> > >From mysqld.log:
> >
> > Best regards,
> >
> > Gelu
> > _____________________________________________________
> > G.NET SOFTWARE COMPANY
> >
>
> Hi!
>
> Was it an empty table ir it had rows.
>
> Was it corrupt prior to being ALTERed ??
>
> Please send us a dump of the table or if it is big, upload it to the
> usual place.
>
> --
> __ ___ ___ ____ __
> / |/ /_ __/ __/ __ \/ / Mr. Sinisa Milivojevic
> / /|_/ / // /\ \/ /_/ / /__ MySQL AB, Fulltime Developer
> /_/ /_/\_, /___/\___\_\___/ Larnaca, Cyprus
> <___/ www.mysql.com
>
> Join MySQL Users Conference and Expo:
> http://www.mysql.com/events/uc2003/
>
>

------------------------------------------------------------ ---------
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
To unsubscribe, e-mail
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php

Re: BUG:ALTER TABLE (MySQL 4.1)

am 25.01.2003 18:28:42 von Gelu Gogancea