maria-discuss team mailing list archive
Mailing list archive
Re: PBXT issues
No idea what is happening here. I would have to investigate to find
out. Please contact me directly. Maybe it would be possible for me to
get access to your test machine. Then I could take a look.
On May 6, 2010, at 8:52 PM, Alexandre Almeida wrote:
Do you any clue why I get this during select?
| RAUL MOREIRA
The statement was: select cep, count(0) from telpbxt group by cep;
Please, be noticed the query are showing wrong data. The first
column is ZIP Code (only numbers) and it's showing city name,
customer name and bourough... These columns are not referenced in
this simple query.
Another weird things is: the query just stopped without error nor
presenting the time, rows, etc.
Ooops, the table structure is:
CREATE TABLE `telpbxt` (
`cpf` bigint(20) DEFAULT NULL,
`log` varchar(100) DEFAULT NULL,
`endereco` varchar(100) DEFAULT NULL,
`comp1` varchar(100) DEFAULT NULL,
`comp2` varchar(100) DEFAULT NULL,
`bairro` varchar(100) DEFAULT NULL,
`cidade` varchar(100) DEFAULT NULL,
`cep` varchar(100) DEFAULT NULL,
`ddd` varchar(100) DEFAULT NULL,
`telefone` varchar(100) DEFAULT NULL
) ENGINE=PBXT DEFAULT CHARSET=latin1 AVG_ROW_LENGTH=94
I have 10.3 mio rows. I know I know this varchar(100) sucks... a lot!
Thanks for you help.
Em 06/05/2010, às 03:32, Paul McCullagh escreveu:
On May 5, 2010, at 7:02 PM, Michael Widenius wrote:
"Paul" == Paul McCullagh <paul.mccullagh@xxxxxxxxxxxxx> writes:
Paul> PBXT can help you out with this. Do the following:
Paul> (1) Load the telpbxt table with a few 1000 rows (or use
Paul> since telpbxt already has too many rows in it).
Paul> (2) In mysql client enter: CHECK TABLE telpbxt2; (note: do
not do this
Paul> on a table with millions of rows. It will take very long to
Paul> (3) Check the MySQL error log, you should see something like
Paul> output below.
Paul> CHECK TABLE: ./test/telpbxt
Paul> Record buffer size = 1024
Paul> Fixed length rec. len. = 1020
Paul> Handle data record size = 638
Paul> Min/max header size = 14/26
Paul> Min/avg/max record size = 19/624/1019
Paul> Avg row len set for tab = not specified
Paul> Rows fixed length = NO
Paul> Maximum fixed size = 16384
Paul> Paste the output in an e-mail, and I will show you what to
use for the
Would it be hard for PBXT to as part of the CHECK TABLE add:
Optimial create AVG_ROW_LENGTH: ?
Currently CHECK TABLE prints:
Average comp. rec. len. = 200
This is the closest to your suggestion of an "Optimal create
AVG_ROW_LENGTH", there is at the moment.
But, this value is not necessarily optimal.
Exactly what is optimal depends on a few additional factors, like
whether you want to optimize for size or caching behavior.
What I can do is add more information to help in this decision
making process, and output a "Recommended AVG_ROW_LENGTH".
Then I can change OPTIMIZE TABLE to automatically set this value,
if no explicit AVG_ROW_LENGTH has been set yet.