nsert and select that caused the table to be locked.
>
> Are there mysql configurations that you can suggest other than skip-locking
> to at least fix the issue?
>
> Thanks,
> Mon
>
>
>
> From: Nilton Moura
> To: mysql@lists.mysql.com
>
on, September 13, 2010 1:07:38 AM
> Subject: Re: skip locking
>
> Received.
>
>
>
> On Sunday, September 12, 2010 09:32:12 am monloi perez wrote:
>> Hi All,
>>
>> Sorry if I posted on the wrong list.
>>
>> I've had this issue with my previous server
Any idea on this?
-Mon
From: Michael Satterwhite
To: mysql@lists.mysql.com
Sent: Mon, September 13, 2010 1:07:38 AM
Subject: Re: skip locking
Received.
On Sunday, September 12, 2010 09:32:12 am monloi perez wrote:
> Hi All,
>
> Sorry if I post
Received.
On Sunday, September 12, 2010 09:32:12 am monloi perez wrote:
> Hi All,
>
> Sorry if I posted on the wrong list.
>
> I've had this issue with my previous server already, seems like
> skip-locking configuration does not seem to work on myisam tables.
>
> Also what is the difference b
On Tue, Sep 09, 2003 at 01:30:51AM -0500, Matt W wrote:
>
> > Jeremy D. Zawodny | Perl, Web, MySQL, Linux Magazine, Yahoo!
> > <[EMAIL PROTECTED]> | http://jeremy.zawodny.com/
> >
> > MySQL 4.0.15-Yahoo-SMP: up 1 days, processed 47,861,708 queries (374/sec. avg)
>
> Off topic: Been wonderi
Hi!
On Sep 09, Daniel Kasak wrote:
> Paul DuBois wrote:
>
> >At 12:00 +1000 9/9/03, Daniel Kasak wrote:
> >
> >>It's been suggested that I add 'enable-locking' to the [mysqld]
> >>section of my.cnf.
> >
> >
> >You might want to reconsider. It's disabled by default on all systems
> >as of MySQL
- Original Message -
From: "Jeremy Zawodny"
Sent: Monday, September 08, 2003 11:33 PM
Subject: Re: --skip-locking and 'enable locking' in my.cnf
> On Mon, Sep 08, 2003 at 10:42:33PM -0500, Paul DuBois wrote:
> >
> > See:
> >
> > http://ww
On Mon, Sep 08, 2003 at 10:42:33PM -0500, Paul DuBois wrote:
>
> See:
>
> http://www.mysql.com/doc/en/System.html
>
> Note the part about Linux.
Paul, you might update that page. It's extoling the virtues of the
2.2 kernel and SMP. But 2.4 is clearly superior in that department.
And the 2GB f
At 13:25 +1000 9/9/03, Daniel Kasak wrote:
Paul DuBois wrote:
At 12:00 +1000 9/9/03, Daniel Kasak wrote:
It's been suggested that I add 'enable-locking' to the [mysqld]
section of my.cnf.
You might want to reconsider. It's disabled by default on all systems
as of MySQL 4, and was disable by d
Paul DuBois wrote:
At 12:00 +1000 9/9/03, Daniel Kasak wrote:
It's been suggested that I add 'enable-locking' to the [mysqld]
section of my.cnf.
You might want to reconsider. It's disabled by default on all systems
as of MySQL 4, and was disable by default before that on Linux.
I see.
I had
At 12:00 +1000 9/9/03, Daniel Kasak wrote:
Hi all.
I'm using MySQL-4.0.14, compiled by Gentoo's ebuild script.
Somewhere along the line, I've picked up a '--skip-locking' flag
that I can't find the source of.
It's not in the /etc/init.d/mysql script. It's not in my my.cnf.
Gentoo has a start-sto
louie,
Friday, July 12, 2002, 12:06:07 PM, you wrote:
lm> http://www.mysql.com/doc/C/r/Crash_recovery.html
lm> Is this very reliable? Coz im planning to remove the --skip-locking options.
On some OS, like Linux, Windows, Solaris skip-locking is ON by
default.
Why do you want remove --skip-lock
o: "Rolf Hopkins" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Thursday, February 08, 2001 3:03
Subject: Re: --skip-locking on Redhat 6.1 Linux
> Rolf Hopkins [[EMAIL PROTECTED]] wrote:
> > Firstly, I'm curious as to why you need --skip-locking in the first
pla
Original Message -
> From: "Hardy Merrill" <[EMAIL PROTECTED]>
> To: "Rolf Hopkins" <[EMAIL PROTECTED]>
> Cc: <[EMAIL PROTECTED]>
> Sent: Wednesday, February 07, 2001 23:15
> Subject: Re: --skip-locking on Redhat 6.1 Linux
>
>
> > Ro
#x27;s accessing the DB, is a cron job. Can you time
it so that your flush-logs occur between this daemon process?
- Original Message -
From: "Hardy Merrill" <[EMAIL PROTECTED]>
To: "Rolf Hopkins" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Wedn
Rolf, I'm invoking safe_mysqld with --skip-locking and
--log-update=update_log, among other options. If I run
mysqladmin flush-logs while database updates are occurring,
the update logs sometimes get confused - the scheme I have
is basically
mysqladmin flush-logs
mv name_of_old_update_log
can: yes
should: That's up to you but personally I wouldn't
- Original Message -
From: "Hardy Merrill" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, February 07, 2001 3:31
Subject: --skip-locking on Redhat 6.1 Linux
> Can/should MySQL be started *without* --skip-locking o
17 matches
Mail list logo
