Re: MySQL Daylight Savings Time Patch
Ryan Stille wrote: Paul DuBois wrote: At 4:40 PM -0600 2/20/07, Ryan Stille wrote: Is there an easy way to test to see if MySQL already has the proper tables loaded? -Ryan Yes, reload them. :-) After that, they're current! ... My timezone tables appear to be empty. At least the time_zone_name and time_zone_transition tables are for sure. I was under the impression I needed to update these tables, but if its working fine without them, then. it must be looking to the OS for timezone info? -Ryan Probably should have included some more info about my setup. I'm on 4.1.20-1 on Linux. -Ryan -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: MySQL Daylight Savings Time Patch
Paul DuBois wrote: At 4:40 PM -0600 2/20/07, Ryan Stille wrote: Is there an easy way to test to see if MySQL already has the proper tables loaded? -Ryan Yes, reload them. :-) After that, they're current! ... My timezone tables appear to be empty. At least the time_zone_name and time_zone_transition tables are for sure. I was under the impression I needed to update these tables, but if its working fine without them, then. it must be looking to the OS for timezone info? -Ryan -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
InnoDB: Assertion failure
Hi. a few days ago, i posted and error mysql, and now i am getting this one: The machine has: 2 CPU Pentium III 700 Mhz Aprox. 4 GB RAM. Redhat 7.2 Mysql version: 4.0.14-standard-log Kernel: Kernel 2.4.18-17.7 (highmem) i`ve searching in google, and i found this king of logs so many times, but i did not found a possible cause to this. Please, if someone have and idea it would be great! Michael.- 070222 23:46:36 InnoDB: Assertion failure in thread 94232 in file mem0pool.c line 493 InnoDB: Failing assertion: 0 InnoDB: We intentionally generate a memory trap. InnoDB: Send a detailed bug report to mysql@lists.mysql.com mysqld got signal 11; This could be because you hit a bug. It is also possible that this binary or one of the libraries it was linked against is corrupt, improperly built,or misconfigured. This error can also be caused by malfunctioning hardware. We will try our best to scrape up some info that will hopefully help diagnose the problem, but since we have already crashed, something is definitely wrong and this may fail. key_buffer_size=402653184 read_buffer_size=2093056 max_used_connections=550 max_connections=800 threads_connected=132 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 3666809 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. thd=0x88f6e40 Attempting backtrace. You can use the following information to find out where mysqld died. If you see no messages after this, something went terribly wrong... Cannot determine thread, fp=0xbfcbe708, backtrace may not be correct. Stack range sanity check OK, backtrace follows: 0x807474f 0x82a0ad8 0x824321c 0x8241c21 0x814af0d 0x814fd3e 0x80d33e7 0x80d6bab -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
columns_priv : how it works ? [ MySQL 4.1 ]
hello, There is something I obviously missed, can't figure out what, since it seems so simple. as user root (of mysql), mysql> use mysql; I can see : mysql> select * from columns_priv where User='demandeur' order by Column_name; and I get : +--+---+--+---++-+---+ |Host |Db |User |Table_name |Column_name |time |Column_priv| +--+---+--+---++-+---+ |localhost |people |demandeur |current|HOMEDIR |19h30|Select | ... now, as user 'demandeur', on the Db 'people' I got : mysql> use people; mysql> select HOMEDIR from current; ERROR 1142 (42000): SELECT command denied to user 'demandeur'@'localhost' for table 'current' This is not what I would expect from the "Column_priv". What is wrong ? (I have done any way "flush privileges;" ) cheers ! _-¯-_-¯-_-¯-_-¯-_ Gilles Missonnier IAP - [EMAIL PROTECTED] 01 44 32 81 36 -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: Restore Question
In news:[EMAIL PROTECTED], [EMAIL PROTECTED] <[EMAIL PROTECTED]> typed: > After creating a new mysql db from the script, should I have first > restored the old mysql database, then the user databases? You should first restore mysql database just to be on the safe side, but I don't think the import of other databases would fail if you did otherwise. > 2. Somewhere I saw that I still needed to create the InnoDB shared > tablespace. What does InnoDB use this for? For the production > system, I need to estimate what size to start with. InnoDB stores there some internal structures and undo logs. Unless there are large or lenghty transactions performed in your database, you shouldn't need much space for the shared tablespace. You may also consider allowing this tablespace to extend automatically if more space is required, which is generally a good idea. > 3. I restored the original mysql database as mysql_old, so I have > access to the old grant tables. Any suggestions for how to recover > the user permissions without redoing all the steps? The simplest solution is to stop the database, remove the contents of datadir/mysql directory and move there all the files from datadir/mysql_old (or copy preserving owner/group/permissions). Then start the server agin. Maciek -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: copy data from prod to test - when database name is not the same name
mysql -h... -u... -p... -e"CREATE DATABASE IF NOT EXISTS mysql_TEST;" mysqldump -h... -u... -p... --routines --triggers Mysql_prod | mysql -h... -u... -p... -Dmysql_TEST - Original Message - From: "Charles Brown" <[EMAIL PROTECTED]> To: mysql@lists.mysql.com Sent: Friday, February 23, 2007 10:48:27 AM (GMT-0500) Auto-Detected Subject: copy data from prod to test - when database name is not the same name Hello All, We have two mysql environment PROD and TEST. I would like to copy data from PROD to TEST. The PROD database name is Mysql_prod and the TEST database name is mysql_TEST. Using mysqldump or any applicable utility can someone show me how to migrate my production data from prod to test. The only thing that is different is the database name. The tables are all the same. Thanks in advance This message is intended only for the use of the Addressee and may contain information that is PRIVILEGED and CONFIDENTIAL. If you are not the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, please erase all copies of the message and its attachments and notify us immediately. Thank you. -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED] -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
copy data from prod to test - when database name is not the same name
Hello All, We have two mysql environment PROD and TEST. I would like to copy data from PROD to TEST. The PROD database name is Mysql_prod and the TEST database name is mysql_TEST. Using mysqldump or any applicable utility can someone show me how to migrate my production data from prod to test. The only thing that is different is the database name. The tables are all the same. Thanks in advance This message is intended only for the use of the Addressee and may contain information that is PRIVILEGED and CONFIDENTIAL. If you are not the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, please erase all copies of the message and its attachments and notify us immediately. Thank you. -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: [LICENSING] why so hazy? Comparing to Samba.
Jim, At 01:58 AM 2/23/2007, Jim Winstead wrote: On Thu, Feb 22, 2007 at 11:33:47PM -0600, mos wrote: > That's just one guy's opinion. :) And quite misinformed, unfortunately. The pricing is what I am getting off of your web site. So if I am misinformed, then it is MySQL AB that is misinforming people. I have your database competitors telling me that MySQL license is $595 *per year* because they keep misreading your web page. It's not just me. The whole database community is confused as to the pricing for MySQL AB. And let's not even get into your licensing interpretations. $595 is the per-server price for MySQL Enterprise, which includes support, the network monitoring and advisory service, and more. It is not the OEM pricing. You may notice that we don't publish OEM pricing, precisely because it is far too easy for someone to think they just need to multiply some base price times some theoretical number of units. So why can't they??? Does someone in MySQL AB sales have to wave some mojo over the licensing application before you can come up with a number for the customer? Why not have an OEM breakdown of prices for 1-9 units, 10-99 units etc.? That's how other database firms work. They are up front with their pricing. Why keep people in the dark of MySQL AB pricing? It seems to me like you change the prices from one individual to another for the same quantity of OEM licenses otherwise you would publish the prices. If you are an ISV looking to license MySQL for distribution with your application, contact the MySQL sales team. They are happy to work with you to fit find the pricing model that makes the most sense. (Or, of course, you can just open source your application.) Great. Let's see. I have this one customer for my application and I need one OEM MySQL license. What's it going to cost me? Hmm. Could it be $595? People can't figure out what to charge for their commercial application until they determine what your licensing will cost them. They might sell only 5 applications per month, and then next year it could be 20. Then it could be back down to 5 per month. If your pricing is pegged to the quantity over a certain time period, then their profit margins will be going up and down like a yo-yo. That's no way to run a business. And I hope we can now consider this horse to be sufficiently dead. When you start publishing accurate pricing on your website, then it can be considered dead. And you wonder why people prefer to use other royalty free databases (Firebird, PostgreSQL) for commercial applications? You're losing a lot of customers with this licensing subterfuge. Sheesh. :( Mike -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Restore Question
We're in the process of changing our InnoDB databases to file-per-table. I started last night with our test server. It went pretty smoothly, except for one stupid mistake on my part. I backed up all databases, deleted he data and log files, re-created the MySQL database from the script, then restored all the user databases. Everything is fine, except of course I'm missing all the users. So my questions are: 1. I had to create the new mysql database in order to get the server to start without error ([ERROR] Fatal error: Can't open and lock privilege tables: Table 'mysql.host' doesn't exist).After creating a new mysql db from the script, should I have first restored the old mysql database, then the user databases? 2. Somewhere I saw that I still needed to create the InnoDB shared tablespace. What does InnoDB use this for? For the production system, I need to estimate what size to start with. 3. I restored the original mysql database as mysql_old, so I have access to the old grant tables. Any suggestions for how to recover the user permissions without redoing all the steps? Thanks, Donna
Re: [LICENSING] why so hazy? Comparing to Samba.
Why you always talk about *client* fee ?? what about the server? Sincerily, I'm see MySQL is not the best option for a commercial application (you don´t distribute you application with GPL lincense). Postgresql is a excellent DB using BSD license and the last version improve the speed reponse. Someones thinks the license of Mysql isn´t confusing .. It is!!!. In my country so much people think Mysql is free ... I say them "It's no free ... It's open source". Two study cases: 1. If I design a desktop application for use with MySQL but I'm not distribute any MySQL client or server and It's my client who install the server and client ... apply any fee? 2. If I use MySQL on a commercial home page ... apply any fee?? thanks, RAUL DUQUE Bogotá, Colombia - Original Message - From: "Jim Winstead" <[EMAIL PROTECTED]> To: "mos" <[EMAIL PROTECTED]> Cc: Sent: Friday, February 23, 2007 2:58 AM Subject: Re: [LICENSING] why so hazy? Comparing to Samba. On Thu, Feb 22, 2007 at 11:33:47PM -0600, mos wrote: That's just one guy's opinion. :) And quite misinformed, unfortunately. $595 is the per-server price for MySQL Enterprise, which includes support, the network monitoring and advisory service, and more. It is not the OEM pricing. You may notice that we don't publish OEM pricing, precisely because it is far too easy for someone to think they just need to multiply some base price times some theoretical number of units. If you are an ISV looking to license MySQL for distribution with your application, contact the MySQL sales team. They are happy to work with you to fit find the pricing model that makes the most sense. (Or, of course, you can just open source your application.) And I hope we can now consider this horse to be sufficiently dead. Jim Winstead MySQL Inc. -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED] -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: backup stratergy
Hi Juan, Thanks a lot for the quick reply. Any idea how much it would cost for ibbackup for innodb. Will mysql be providing this with any of their new release. regards anandkl On 2/23/07, Juan Eduardo Moreno <[EMAIL PROTECTED]> wrote: Ananda, For Innodb the best is Innodb Hot Backup ( www.innodb.com (US$) ) For MyISAM you can use a simple backup ( copy/paste) of your files. Also, you can do snapshots using mysqldump. Also, you can use Zmanda ( www.zmanda.com). Regards, Juan Eduardo On 2/23/07, Ananda Kumar < [EMAIL PROTECTED]> wrote: > > Hi All, > Can you please direct me to any good documentation for a good backup and > > recovery stratergy for MyISAM and INNODB in mysql. > > regards > anandkl >
Re: backup stratergy
Ananda, For Innodb the best is Innodb Hot Backup ( www.innodb.com (US$) ) For MyISAM you can use a simple backup ( copy/paste) of your files. Also, you can do snapshots using mysqldump. Also, you can use Zmanda ( www.zmanda.com). Regards, Juan Eduardo On 2/23/07, Ananda Kumar <[EMAIL PROTECTED]> wrote: Hi All, Can you please direct me to any good documentation for a good backup and recovery stratergy for MyISAM and INNODB in mysql. regards anandkl
Re: unauthenticated user
In news:[EMAIL PROTECTED], Jerome Macaranas <[EMAIL PROTECTED]> wrote: > Would it be possible to prevent reverse lookup? Im using the latest > GA version.. Please read the manual section on how MySQL uses DNS. Maciek -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
backup stratergy
Hi All, Can you please direct me to any good documentation for a good backup and recovery stratergy for MyISAM and INNODB in mysql. regards anandkl
Re: [LICENSING] why so hazy? Comparing to Samba.
On Thu, Feb 22, 2007 at 11:33:47PM -0600, mos wrote: > That's just one guy's opinion. :) And quite misinformed, unfortunately. $595 is the per-server price for MySQL Enterprise, which includes support, the network monitoring and advisory service, and more. It is not the OEM pricing. You may notice that we don't publish OEM pricing, precisely because it is far too easy for someone to think they just need to multiply some base price times some theoretical number of units. If you are an ISV looking to license MySQL for distribution with your application, contact the MySQL sales team. They are happy to work with you to fit find the pricing model that makes the most sense. (Or, of course, you can just open source your application.) And I hope we can now consider this horse to be sufficiently dead. Jim Winstead MySQL Inc. -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
