At 11:42 -0400 4/17/04, Mark Susol|Ultimate Creative Media wrote:
> The general answer to your question, if you're willing to cooperate
with the server, is to lock the tables from within the server so that
no other clients can modify them, and use FLUSH TABLES to flush any
changes to disk. Whi
> The general answer to your question, if you're willing to cooperate
> with the server, is to lock the tables from within the server so that
> no other clients can modify them, and use FLUSH TABLES to flush any
> changes to disk. While the lock remains in place, copy the table
> files. Then unlo
At 0:03 -0400 4/16/04, Mark Susol|Ultimate Creative Media wrote:
Did I really ask that tough a question? Anyone?
I'm not sure you're asking an answerable question. Consider this requirement
that you give below:
> So what do I need to do before running any backup scripts to ensure the
> tables wi
Did I really ask that tough a question? Anyone?
On 4/15/04 7:38 PM, "Mark Susol | Ultimate Creative Media"
<[EMAIL PROTECTED]> wrote:
> I've found a nice shell script to use to backup my server's MySQL databases.
> https://sourceforge.net/projects/automysqlbackup/
>
> However, when I tried this
hello.
You can read lock whole database's tables like this :
FLUSH TABLES WITH READ LOCK ;
and unlock with
UNLOCK TABLES ;
- Original Message -
From: "Franz, Fa. PostDirekt MA" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, February 05, 2003 10:35 PM
Subject: locking tab
.
- Original Message -
From: "Alexander Keremidarski" <[EMAIL PROTECTED]>
Newsgroups: mailing.database.mysql
Sent: Thursday, May 23, 2002 1:54 AM
Subject: Re: Locking TABLES for myisamchk, please help!!
> Mark wrote:
> > Wednesday, May 22, 2002, 9:23:02 AM, louie w
Mark wrote:
> Wednesday, May 22, 2002, 9:23:02 AM, louie wrote:
> Personally, I find the behavior of myisasmchk to be a bit "beta" when it
> comes live tables. It would be real easy for myisasmchk to refuse to run
> when mysqld is running. That should be a built-in precaution. I can
> understand
Wednesday, May 22, 2002, 9:23:02 AM, louie wrote:
lm> Hi, i was thingking about locking the tables first so no connection
lm> could write so i can do myisamchk. Is this process safe?
lm> Procedures:
lm> 1. lockdb
lm> 2. run myisamchk -r or -o
lm> 3. unlock db
lm> Btw, mysqld is running. I want
louie,
Wednesday, May 22, 2002, 9:23:02 AM, you wrote:
lm> Hi, i was thingking about locking the tables first so no connection
lm> could write so i can do myisamchk. Is this process safe?
lm> Procedures:
lm> 1. lockdb
lm> 2. run myisamchk -r or -o
lm> 3. unlock db
lm> Btw, mysqld is running. I
> What error occurs if i try to access (read or write) a table that was
locked
> (LOCK TABLES mytable WRITE) by another thread?
My belief is that you do not get an error. The thread attempting to access
the
locked table is stalled until the lock is released. If the lock is never
released, you
To avoid the "Fatal Embrace" where two users each lock a table, and
then attempt to read the table the other locked, you must lock
all table you intend to use for the duration of the lock.
The manual clearly states that a subsequent lock or unlock command
will first unlock all the tables you curre
11 matches
Mail list logo
