Hi All,
I have used MySQL 5.1.29 and I would like to ask a question related to InnoDB
and row_format=COMPACT and OPTIMIZE
Why when trying to run OPTMIZE on InnoDB table with row_format=compact
it displays Table does not support optimize, doing recreate + analyze instead
?
Hi ALL,
I have been using 5.1.24-rc and partitioning by range.
I have noticed that while doing a set of SELECT
statements on one of the partitions (e.g. p1) and at
the same time doing an ALTER TABLE with drop or add a
different partition (e.g. ALTER TABLE DROP or ADD
PARTITION p10) all the
are performed as soon as the
partitioning operation has completed
Is that true also for the InnoDB storage engine ?
What does Reads from such tables are relatively
unaffected; implies, please ?
Thanks,
Mariella
--- Mariella Petrini [EMAIL PROTECTED]
wrote:
Hi ALL,
I have been using 5.1.24
Hi All,
Is there any plan to release a binary version for
mysql-5.1.23-maria-alpha for Linux 64 for AMD ?
Thanks in advance for your help,
Mariella
Looking for last minute shopping deals?
Find them
Hi,
Do you know an approximate date ?
Thanks,
Mariella
--- Sergei Golubchik [EMAIL PROTECTED] wrote:
Hi!
On Feb 14, Mariella Petrini wrote:
Hi All,
Is there any plan to release a binary version for
mysql-5.1.23-maria-alpha for Linux 64 for AMD ?
Yes.
Regards / Mit vielen
Hi ALL,
I have compiled MySLQ 5.1.23-rc for Linux 64bit
./configure CC=gcc CFLAGS=-DBIG_JOINS=1 -O3 CXX=g++
CXXFLAGS=-DBIG_JOINS=1 -felide-constructors
-fno-exceptions -fno-rtti -O3
--prefix=/app/mysql-5.1.23-rc
--localstatedir=/app/mysql-5.1.23-rc/data
--libexecdir=/app/mysql-5.1.23-rc/bin
Hi All,
I would like to be able to use MySQL 5.1.21 with
the PBXT engine.
I have compiled MySQL 5.1.21 64 bits on Debian 4.0
with linux 2.6 with the options specified in the
README that comes with the PBXT source code.
I have copied the binary of the pbxt library into the
lib/mysql directory
-recursive] Error 1
--- Vladimir Shebordaev
[EMAIL PROTECTED] wrote:
Mariella,
try to disable building static binaries, please
don't use
--enable-static configure option, you'd better use
--disable-static instead.
In the hope it helps.
Regards,
Vladimir
Mariella Petrini пиÑеÑ
I have re-run and job and I was able to repeat the
problem.
Find attached the mysql server error log with all the
tarces.
Could you please help ?
Thanks,
Mariella
--- Mariella Petrini [EMAIL PROTECTED]
wrote:
Hi All,
I have started using MySQL 6.0.2 with Falcon on
Linux
with Debian
table or not tough...
--
Mathieu Bruneau
aka ROunofF
===
GPG keys available @ http://rounoff.darktech.org
Mariella Petrini a �crit :
I have re-run and job and I was able to repeat the
problem.
Find attached the mysql server error log with all the
tarces.
Could you please help ?
Thanks
Hi All,
I have started using MySQL 6.0.2 with Falcon on Linux
with Debian 4.
I have compiled the source code for 64 bit executable.
The system is an Intel 2 cpus 4 cores each, with 8 GB
of RAM.
I have started creating tables (without partitioning)
whit engine type Falcon. After having created
Hi All,
I have been using MySQL 5.1.x with InnoDB and Raw
Devices.
[mysqld]
innodb_data_home_dir=
innodb_data_file_path=/dev/hdd1:3Gnewraw;/dev/hdd2:2Gnewraw
...
[mysqld]
innodb_data_home_dir=
innodb_data_file_path=/dev/hdd1:5Graw;/dev/hdd2:2Graw
Is there any way to specifiy the
Hi,
Is there way with MySQL 5.0.45 on Linux Debian to
specify tmpdir (in my.cnf) to a directory on a RAMFS
filesystem.
I have tried but MySQL did not even start (it
generated an error saying that it could not write
)
Thanks in advance for your help.
I look forward to hearing from you,
,
Mariella Petrini wrote:
Hi,
I have been using 5.0.32 MySQL on Debian.
Everything worked properly.
DRBD has been added and configure with MySQL and
restarted.
The tables used are InnoDB type and use
auto_increment.
After that during INSERTs and UPDATEs innodb
started
Hi,
I have been working with MySQL 5.1.20 (64 bits
compiled on Mac OS for MacPro Intel Xeon Quad-Core
qith 2 processors and 8GB of RAM) and MySQL 5.0.41 (32
bits).
While running some of the select statements
(independently of the storage engine used, either
InnoDB or MyISAM) I have noticed that
Hi,
I have been using 5.0.32 MySQL on Debian.
Everything worked properly.
DRBD has been added and configure with MySQL and
restarted.
The tables used are InnoDB type and use
auto_increment.
After that during INSERTs and UPDATEs innodb started
to roll back
for table lock on AUTO_INC
How could
Dear All,
I would like to know if there are short time plans (and eventually when
approximately it will be) to include partitioning in the next MySQL stable
release.
Thanks in advance for your help.
I look forward to hearing from you,
Mariella
-
You
Hi ALL,
I would like to use INNODB with raw devices for tablespace in the
innodb_data_file_path both on MySQL 5.0.x and MySQL 5.1.x.
Is it possible to use DRBD (Distributed Raw Block Device)
with InnoDB and raw devices.
If yes, which are the constraints ?
Thanks in advance for your
Hi,
After having compiled (debug and optimized version) of MySQL 5.1.14 on
Itanium-2 using icc, I have run
mysql_install_db --user=...
and started mysqld_safe in both scenarios (debug and optimized). In both
cases mysqld starts without any errors.
Unfortunaly when
Dear All,
I am trying to compile MySQL 5.0.27 and 5.1.14 on a shared memory processors
system with 128 processors IA-64 Itanium-2.
I have downloaded the binary version of MySQL-max 5.0.27 Linux IA64 and I have
installed and configured it with no problems.
I need to install also the
20 matches
Mail list logo