ND_refresh (to await any thread that is waiting for all instances of
a table to be closed)."
-Sheeri
On 5/17/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
Hi,
If you "open" a table using,
HANDLER tablename OPEN;
and then (in another MySQL command windows), execute,
fl
Hi,
If you "open" a table using,
HANDLER tablename OPEN;
and then (in another MySQL command windows), execute,
flush tables with read lock;
The flush tables "hangs" until you execute a
HANDLER tablename CLOSE;
command.
Is this a bug? Can anyone explain this?
Many
In the " 4.0.20-standard-log" version of mysql, will the " FLUSH TABLES WITH READ
LOCK" statement work to quiesce a database consisting of Innodb tables?
Thanks,
---
Kato D. Haws
Arizona State Un
Hello,
Still on this database consistency problem with FLUSH TABLES WITH
READ LOCK... I've tried upgrading to MySQL 4.0.5a binary distribution
(instead of source), but the problem does not disappear.
So I've made a little test. I open too shells.
-> Shell 1:
I launch the MySQL
Hello Victoria,
> You need to do it with 2 sessions.
>
> According MySQL manual:
>
> If you are using a Veritas filesystem, you can do:
>
>1. From a client (or Perl), execute: FLUSH TABLES WITH READ LOCK.
>2. From another shell, execute: mount vxfs snapshot.
>
Antoine,
Thursday, November 28, 2002, 4:17:48 PM, you wrote:
A> Sorry to insist, but nobody has any clues about this ?
A> I can supply further info if needed.
A> Is the "FLUSH TABLES WITH READ LOCK" functionality well tested ?
A> Having corrupted backups is annoying, and
Sorry to insist, but nobody has any clues about this ?
I can supply further info if needed.
Is the "FLUSH TABLES WITH READ LOCK" functionality well tested ?
Having corrupted backups is annoying, and I can't really
take the system down for a 4-hour tape backup... ;(
M
Hi,
I am using FLUSH TABLES WITH READ LOCK to get consistent
snapshots of my database without shutting it down.
The setup is :
- bi-P4 Xeon with Redhat 7.3
- 2.4.19 kernel with properly patched LVM (compiled from source)
- MySQL server 4.0.4 (compiled from source)
- ext3 filesystem on a 44 GB
