Re: 3.23.31 gives FULLTEXT problems on sparc64 Linux
Hello The error says: "Can't read indexpage from filepos: -1". [...] Thank you for reporting this. This will be fixed in a next release. But it was really not a big problem - the table was not really corrupted. [...] Thanks for the fix and the explanation! cheers -- TS - 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: 3.23.31 gives FULLTEXT problems on sparc64 Linux
Hi!
Sorry for delay :-(
On Jan 24, Tibor Simko wrote:
Hello
I wrote:
After upgrading to 3.23.31, FULLTEXT selects give often "error -1
from table handler" for me. [...]
Sergei Golubchik [EMAIL PROTECTED] wrote:
Thanks for a bug report! This would be fixed in a nex release.
Thanks. In 3.23.32 the test case I submitted apparently works better,
but bad things still happen, like the following table corruption:
DROP TABLE IF EXISTS t1;
CREATE TABLE t1 (
id mediumint unsigned NOT NULL auto_increment,
tag char(6) NOT NULL default '',
value text NOT NULL default '',
PRIMARY KEY (id),
KEY kt(tag),
KEY kv(value(15)),
FULLTEXT KEY kvf(value)
) TYPE=MyISAM;
INSERT INTO t1 (tag,value) VALUES ('foobar','baz');
CHECK TABLE t1;
The error says: "Can't read indexpage from filepos: -1". Moreover,
myisachk isn't able to repair it! (neither -r nor -o).
Tested on both sparc64-linux (sun4u) and sparc-solaris2.6 (sun4m).
cheers
--
TS
Thank you for reporting this.
This will be fixed in a next release.
But it was really not a big problem - the table was not really corrupted.
myisamchk thought it was because there was empty index and non-empty
table - something that should never happen with normal index.
The bug was fixed by making myisamchk to treat such a situation
as normal.
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: 3.23.31 gives FULLTEXT problems on sparc64 Linux
Hello
I wrote:
After upgrading to 3.23.31, FULLTEXT selects give often "error -1
from table handler" for me. [...]
Sergei Golubchik [EMAIL PROTECTED] wrote:
Thanks for a bug report! This would be fixed in a nex release.
Thanks. In 3.23.32 the test case I submitted apparently works better,
but bad things still happen, like the following table corruption:
DROP TABLE IF EXISTS t1;
CREATE TABLE t1 (
id mediumint unsigned NOT NULL auto_increment,
tag char(6) NOT NULL default '',
value text NOT NULL default '',
PRIMARY KEY (id),
KEY kt(tag),
KEY kv(value(15)),
FULLTEXT KEY kvf(value)
) TYPE=MyISAM;
DROP TABLE IF EXISTS t2;
CREATE TABLE t2 (
id_t2 mediumint unsigned NOT NULL default '0',
id_t1 mediumint unsigned NOT NULL default '0',
field_number tinyint unsigned NOT NULL default '0',
PRIMARY KEY (id_t2,id_t1,field_number),
KEY id_t1(id_t1)
) TYPE=MyISAM;
INSERT INTO t1 (tag,value) VALUES ('foobar','baz');
INSERT INTO t2 VALUES (1,1,1);
CHECK TABLE t1;
The error says: "Can't read indexpage from filepos: -1". Moreover,
myisachk isn't able to repair it! (neither -r nor -o).
Tested on both sparc64-linux (sun4u) and sparc-solaris2.6 (sun4m).
cheers
--
TS
-
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
3.23.31 gives FULLTEXT problems on sparc64 Linux
Hello
After upgrading to 3.23.31, FULLTEXT selects give often "error -1 from
table handler" for me. The error log says "ft_read_first: Got error
-1 when reading table foo". I think I have not seen those for older
3.23.x versions (x=28 or so), at least not that frequently.
A small example to reproduce the error:
DROP TABLE IF EXISTS t1;
CREATE TABLE t1 (
id mediumint unsigned NOT NULL auto_increment,
tag char(6) NOT NULL default '',
value text NOT NULL default '',
PRIMARY KEY (id),
KEY kt(tag),
KEY kv(value(15)),
FULLTEXT KEY kvf(value)
) TYPE=MyISAM;
DROP TABLE IF EXISTS t2;
CREATE TABLE t2 (
id_t2 mediumint unsigned NOT NULL default '0',
id_t1 mediumint unsigned NOT NULL default '0',
field_number tinyint unsigned NOT NULL default '0',
PRIMARY KEY (id_t2,id_t1,field_number),
KEY id_t1(id_t1)
) TYPE=MyISAM;
INSERT INTO t1 (tag,value) VALUES ('foo123','bar1');
INSERT INTO t2 VALUES (2231626,64280,0);
INSERT INTO t1 (tag,value) VALUES ('foo123','bar2');
INSERT INTO t2 VALUES (2231626,64281,0);
SELECT DISTINCT t2.id_t2
FROM t2, t1
WHERE MATCH (t1.value) AGAINST ('baz')
AND t1.id = t2.id_t1;
The error occurs during final SELECT. I've seen it only for FULLTEXT
searches; if I use e.g. "WHERE t1.value LIKE 'baz%' in that statement,
everything works fine.
P.S. Self-compiled 3.23.31 on sparc64 Linux (Debian stable).
cheers
--
TS
-
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: 3.23.31 gives FULLTEXT problems on sparc64 Linux
Hi!
On Jan 19, Tibor Simko wrote:
Hello
After upgrading to 3.23.31, FULLTEXT selects give often "error -1 from
table handler" for me. The error log says "ft_read_first: Got error
-1 when reading table foo". I think I have not seen those for older
3.23.x versions (x=28 or so), at least not that frequently.
A small example to reproduce the error:
DROP TABLE IF EXISTS t1;
CREATE TABLE t1 (
id mediumint unsigned NOT NULL auto_increment,
tag char(6) NOT NULL default '',
value text NOT NULL default '',
PRIMARY KEY (id),
KEY kt(tag),
KEY kv(value(15)),
FULLTEXT KEY kvf(value)
) TYPE=MyISAM;
DROP TABLE IF EXISTS t2;
CREATE TABLE t2 (
id_t2 mediumint unsigned NOT NULL default '0',
id_t1 mediumint unsigned NOT NULL default '0',
field_number tinyint unsigned NOT NULL default '0',
PRIMARY KEY (id_t2,id_t1,field_number),
KEY id_t1(id_t1)
) TYPE=MyISAM;
INSERT INTO t1 (tag,value) VALUES ('foo123','bar1');
INSERT INTO t2 VALUES (2231626,64280,0);
INSERT INTO t1 (tag,value) VALUES ('foo123','bar2');
INSERT INTO t2 VALUES (2231626,64281,0);
SELECT DISTINCT t2.id_t2
FROM t2, t1
WHERE MATCH (t1.value) AGAINST ('baz')
AND t1.id = t2.id_t1;
The error occurs during final SELECT. I've seen it only for FULLTEXT
searches; if I use e.g. "WHERE t1.value LIKE 'baz%' in that statement,
everything works fine.
P.S. Self-compiled 3.23.31 on sparc64 Linux (Debian stable).
cheers
--
TS
Thanks for a bug report!
This would be fixed in a nex release.
Regards,
Sergei
--
MySQL Development Team
__ ___ ___ __
/ |/ /_ __/ __/ __ \/ / Sergei Golubchik [EMAIL PROTECTED]
/ /|_/ / // /\ \/ /_/ / /__ MySQL AB, http://www.mysql.com/
/_/ /_/\_, /___/\___\_\___/ Helsinki, Finland (till Sunday)
___/
-
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
