Any answers for the question below ?
Is there a DST patch for MySql 4.0.20? Thanks.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Friday, February 09, 2007 9:30 AM
To: mysql@lists.mysql.com
Subject: MySQL Daylight Savings Time Patch
Is there a DST patch
and
10, Windows XP, and Mac OS X 10.4, and almost certainly others.
HTH,
Dan
On 2/20/07, Chris White [EMAIL PROTECTED] wrote:
Sun, Jennifer wrote:
Any answers for the question below ?
Is there a DST patch for MySql 4.0.20? Thanks.
-Original Message-
From
Hi,
We are running mysql-4.0.22 on Gentoo Linux. We do regular mysqlhotcopy of all
databases and do regular flush logs for transaction logs.
However, My flush logs failed since yesterday,
the mysqladmin flush-logs gave me error: /usr/bin/mysqladmin: refresh failed;
error: 'Unknown error'
When
The command is issued from mysql command line. Is there any parameters or options I
can use without locking the table?
-Original Message-
From: Marc Slemko [mailto:[EMAIL PROTECTED]
Sent: Thursday, September 02, 2004 2:24 PM
To: Sun, Jennifer
Cc: [EMAIL PROTECTED]
Subject: Re: tuning
To: [EMAIL PROTECTED]
Subject: RE: tuning suggestion for large query
At 04:13 PM 9/1/2004, Sun, Jennifer wrote:
Thanks Mike.
Seems like even with handler, the big query process is still consuming all
my RAM and swap and being killed with error
'VM: killing process mysql
__alloc_pages: 0-order allocation
]
Sent: Thursday, September 02, 2004 2:41 PM
To: Sun, Jennifer
Cc: [EMAIL PROTECTED]
Subject: Re: tuning suggestion for large query
Due to the nature of myisam tables, when you are doing a query then
the table will be locked for writes. Reads will still be permitted
until another write request
Hi,
We have a job that do 'select * from big-table' on a staging mysql database, then dump
to data warehouse, it is scheduled to run once a day, but may be run manually. Also we
have several other small OLTP database on the same server.
When the big job run, it would use all the physical mem
Thanks Mike.
Seems like even with handler, the big query process is still consuming all my RAM and
swap and being killed with error
'VM: killing process mysql
__alloc_pages: 0-order allocation failed (gfp=0x1d2/0)'
I would like to find a startup parameter either for client or server to limit
