Re: Mysql to Postgresql
2011/2/22 Adarsh Sharma adarsh.sha...@orkash.com: Dear all, Today I need to back up a mysql database and restore in Postgresql database but I don't know how to achieve this accurately. Have a look at: mysqldump --compatible=postgresql command: http://dev.mysql.com/doc/refman/5.1/en/mysqldump.html#option_mysqldump_compatible Anyway, most of the times you will need a more manual migration, with human intervention (custom scripts) and migrating the data through something like CSV (SELECT... INTO OUTFILE). -- Jaime Crespo MySQL Java Instructor Software Developer Warp Networks http://warp.es -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org
Re: mysql vs postgresql -- is this list accurate?
On Mon, 6 Sep 2010 06:36:02 -0400 (EDT), Robert P. J. Day rpj...@crashcourse.ca wrote: no, i don't want to start a flame war, i just want some feedback on a current list of mysql drawbacks WRT postgresql. in the context of a fully open-source, java based ECM product, there is a FAQ entry that summarizes why the developers would prefer their users to use postgresql as opposed to mysql: http://www.nuxeo.org/xwiki/bin/view/FAQ/WhyAvoidMySQL There are a few odd criticisms, such as the limitation on VARCHAR fields (haven't they discovered TEXT/BLOB types?). Also, some of their expectations seem very specific to their own implementation (I've personally never had to do 15 levels of cascade delete). But within the particular context they describe, I'd say that overall they are being fair. Many, many other CMSs are very succesful with MySQL implementations, so if you already have a marked preference for working with MySQL, you might want to look at other products before making a decision. Having read that page, I know I would. / Carsten -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org
Re: MySQL versus PostgreSQL for GPS Data
Jim Ginn wrote: Not sure why you you need the trucks location 'every second' ie: 31,536,000 rows per year per truck ? doing every 30 seconds seems more manageable at 1,051,200 rows per year per truck? Maybe better at 60 seconds? OpenGGD is also designed to deliver GPS data in real time; we have customers that sometimes want to track their trucks in real time, that's why we think the worst scenario could be one position per second. Juan Karlos 2009/3/18 Jim Ginn j...@oats.com Juan: We've had success with spatial indexes and mysql on our sites however our numbers are smaller: http://brokersnetwork.com (200,000+ records) http://yearlyrentals.com (200,000+ records) http://avalonrealestate.com/map.php (4,400+ records) ... Not sure why you you need the trucks location 'every second' ie: 31,536,000 rows per year per truck ? doing every 30 seconds seems more manageable at 1,051,200 rows per year per truck? Maybe better at 60 seconds? Jim Juan, On Wed, Mar 18, 2009 at 11:14 AM, Juan Pereira juankarlos.open...@gmail.com wrote: Hello, I'm currently developing a program for centralizing the vehicle fleet GPS information -http://openggd.sourceforge.net-, written in C++. The database should have these requirements: - The schema for this kind of data consists of several arguments -latitude, longitude, time, speed. etc-, none of them is a text field. - The database also should create a table for every truck -around 100 trucks-. - There won't be more than 86400 * 365 rows per table -one GPS position every second along one year-. - There won't be more than 10 simultaneously read-only queries. The question is: Which DBMS do you think is the best for this kind of application? PostgreSQL or MySQL? I think it depends on exactly what you want to do with the data. MySQL has fairly poor support for spatial types but you can achieve a lot just manipulating normal data types. Postgres (which i know nothing about) appears to have better spatial support via postgis http://dev.mysql.com/doc/refman/5.0/en/spatial-extensions.html http://postgis.refractions.net/documentation/manual-1.3/ In terms of data size you should not have a problem, I think you need to look at how you are going to query the tables. Cheers, Ewen Thanks in advance Juan Karlos. -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=...@oats.com
Re: MySQL versus PostgreSQL for GPS Data
Juan: Still seems excessive but in that case, ignore inserts that have no change in lat / lon ... Jim Jim Ginn wrote: Not sure why you you need the trucks location 'every second' ie: 31,536,000 rows per year per truck ? doing every 30 seconds seems more manageable at 1,051,200 rows per year per truck? Maybe better at 60 seconds? OpenGGD is also designed to deliver GPS data in real time; we have customers that sometimes want to track their trucks in real time, that's why we think the worst scenario could be one position per second. Juan Karlos 2009/3/18 Jim Ginn j...@oats.com Juan: We've had success with spatial indexes and mysql on our sites however our numbers are smaller: http://brokersnetwork.com (200,000+ records) http://yearlyrentals.com (200,000+ records) http://avalonrealestate.com/map.php (4,400+ records) ... Not sure why you you need the trucks location 'every second' ie: 31,536,000 rows per year per truck ? doing every 30 seconds seems more manageable at 1,051,200 rows per year per truck? Maybe better at 60 seconds? Jim Juan, On Wed, Mar 18, 2009 at 11:14 AM, Juan Pereira juankarlos.open...@gmail.com wrote: Hello, I'm currently developing a program for centralizing the vehicle fleet GPS information -http://openggd.sourceforge.net-, written in C++. The database should have these requirements: - The schema for this kind of data consists of several arguments -latitude, longitude, time, speed. etc-, none of them is a text field. - The database also should create a table for every truck -around 100 trucks-. - There won't be more than 86400 * 365 rows per table -one GPS position every second along one year-. - There won't be more than 10 simultaneously read-only queries. The question is: Which DBMS do you think is the best for this kind of application? PostgreSQL or MySQL? I think it depends on exactly what you want to do with the data. MySQL has fairly poor support for spatial types but you can achieve a lot just manipulating normal data types. Postgres (which i know nothing about) appears to have better spatial support via postgis http://dev.mysql.com/doc/refman/5.0/en/spatial-extensions.html http://postgis.refractions.net/documentation/manual-1.3/ In terms of data size you should not have a problem, I think you need to look at how you are going to query the tables. Cheers, Ewen Thanks in advance Juan Karlos. -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=...@oats.com -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org
Re: MySQL versus PostgreSQL for GPS Data
Juan I don't think it really matters, doesn't look like you'll need any features which are only available in one or the other! The main issue you will have is supporting the application and the RDBMS so go for the one you are most comfortable with and can support/configure best. Regards John Hello, I'm currently developing a program for centralizing the vehicle fleet GPS information -http://openggd.sourceforge.net-, written in C++. The database should have these requirements: - The schema for this kind of data consists of several arguments -latitude, longitude, time, speed. etc-, none of them is a text field. - The database also should create a table for every truck -around 100 trucks-. - There won't be more than 86400 * 365 rows per table -one GPS position every second along one year-. - There won't be more than 10 simultaneously read-only queries. The question is: Which DBMS do you think is the best for this kind of application? PostgreSQL or MySQL? Thanks in advance Juan Karlos. __ This email has been scanned by Netintelligence http://www.netintelligence.com/email -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org
Re: MySQL versus PostgreSQL for GPS Data
Juan, On Wed, Mar 18, 2009 at 11:14 AM, Juan Pereira juankarlos.open...@gmail.com wrote: Hello, I'm currently developing a program for centralizing the vehicle fleet GPS information -http://openggd.sourceforge.net-, written in C++. The database should have these requirements: - The schema for this kind of data consists of several arguments -latitude, longitude, time, speed. etc-, none of them is a text field. - The database also should create a table for every truck -around 100 trucks-. - There won't be more than 86400 * 365 rows per table -one GPS position every second along one year-. - There won't be more than 10 simultaneously read-only queries. The question is: Which DBMS do you think is the best for this kind of application? PostgreSQL or MySQL? I think it depends on exactly what you want to do with the data. MySQL has fairly poor support for spatial types but you can achieve a lot just manipulating normal data types. Postgres (which i know nothing about) appears to have better spatial support via postgis http://dev.mysql.com/doc/refman/5.0/en/spatial-extensions.html http://postgis.refractions.net/documentation/manual-1.3/ In terms of data size you should not have a problem, I think you need to look at how you are going to query the tables. Cheers, Ewen Thanks in advance Juan Karlos. -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org
Re: MySQL versus PostgreSQL for GPS Data
Juan: We've had success with spatial indexes and mysql on our sites however our numbers are smaller: http://brokersnetwork.com (200,000+ records) http://yearlyrentals.com (200,000+ records) http://avalonrealestate.com/map.php (4,400+ records) ... Not sure why you you need the trucks location 'every second' ie: 31,536,000 rows per year per truck ? doing every 30 seconds seems more manageable at 1,051,200 rows per year per truck? Maybe better at 60 seconds? Jim Juan, On Wed, Mar 18, 2009 at 11:14 AM, Juan Pereira juankarlos.open...@gmail.com wrote: Hello, I'm currently developing a program for centralizing the vehicle fleet GPS information -http://openggd.sourceforge.net-, written in C++. The database should have these requirements: - The schema for this kind of data consists of several arguments -latitude, longitude, time, speed. etc-, none of them is a text field. - The database also should create a table for every truck -around 100 trucks-. - There won't be more than 86400 * 365 rows per table -one GPS position every second along one year-. - There won't be more than 10 simultaneously read-only queries. The question is: Which DBMS do you think is the best for this kind of application? PostgreSQL or MySQL? I think it depends on exactly what you want to do with the data. MySQL has fairly poor support for spatial types but you can achieve a lot just manipulating normal data types. Postgres (which i know nothing about) appears to have better spatial support via postgis http://dev.mysql.com/doc/refman/5.0/en/spatial-extensions.html http://postgis.refractions.net/documentation/manual-1.3/ In terms of data size you should not have a problem, I think you need to look at how you are going to query the tables. Cheers, Ewen Thanks in advance Juan Karlos. -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=...@oats.com -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org
RE: MySQL vs PostgreSQL
Perhaps a quick search at a list archive will give you the answers you are looking for. This was discussed at length about 6 months ago and the messages are still at gmane. Just page through and you will find many messages with just this subject. http://search.gmane.org/search.php?group=gmane.comp.db.mysql.generalque ry=postgres Regards David Logan Database Administrator HP Managed Services 148 Frome Street, Adelaide 5000 Australia +61 8 8408 4273 - Work +61 417 268 665 - Mobile +61 8 8408 4259 - Fax -Original Message- From: ninjajs [mailto:[EMAIL PROTECTED] Sent: Tuesday, 15 March 2005 8:20 PM To: mysql@lists.mysql.com Subject: MySQL vs PostgreSQL Hi, What do you think about MySQL vs PostgreSQL ? Thanks. -- 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: MySQL vs PostgreSQL
On Tue, 15 Mar 2005 18:49:38 +0900 ninjajs [EMAIL PROTECTED] wrote: What do you think about MySQL vs PostgreSQL ? Both are great products and have their ups and downs. On a MySQL list you will not get an un-biases answer to this question. If you really want to know what people on the MySQL list think of PG, search the archives (as already recommended). If you also want to know what PG folks think of MySQL, they have list archives as well. Both are easy enough to install (with MySQL being slightly easier on the newbie scale) that you can just install them both, and evaluate for yourself. Have fun, Josh -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: mysql vs postgresql
At 05:45 PM 2/24/2005, you wrote: hi, just want to know the main benefits of mysql over postgresql. thanks, Payam Shabanian Payam, The differences between the products are narrowing, especially with MySQL 5.0 which is still in beta. If I could sum it up in 1 sentence then MySQL is typically faster and Postgresql has more features. But if you have a commercial application, the main difference is economics. You can distribute your Postgresql application for free whether it is a commercial application or a free application. You can distribute your MySQL application without purchasing a MySQL license only under the GPL (you need to release your source code). If you distribute your application outside of the GPL you will need a MySQL license for each copy you distribute (which is around $500). Even if you distribute your MySQL application for free (even inside your company), you will need to distribute your source otherwise you need a license for each copy. Some interesting links: http://sunsite.mff.cuni.cz/MIRRORS/ftp.mysql.com/doc/en/MySQL-PostgreSQL_features.html http://www.mysql.com/company/legal/licensing/faq.html http://www.databasejournal.com/features/mysql/article.php/3288951 Mike -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: mysql vs postgresql
On Fri, 25 Feb 2005 11:21:26 -0600, mos wrote: http://sunsite.mff.cuni.cz/MIRRORS/ftp.mysql.com/doc/en/MySQL-PostgreSQL_features.html There is a reason this page was removed from the MySQL site: some of it was never correct in the first place, and the rest was severly outdated. Don't you think it is childish to link to documentation from 2003? Jochem -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: mysql vs postgresql
On Fri, Feb 25, 2005 at 06:43:50PM +0100, Jochem van Dieten [EMAIL PROTECTED] wrote: Don't you think it is childish to link to documentation from 2003? I've never seen a child do anything like you describe. -Rich -- Rich Lafferty --+--- Ottawa, Ontario, Canada| Save the Pacific Northwest Tree Octopus! http://www.lafferty.ca/|http://zapatopi.net/treeoctopus.html [EMAIL PROTECTED] ---+--- -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: mysql vs postgresql
Hello. You should search in archives for such questions. For example see threads at: http://lists.mysql.com/mysql/160972 http://lists.mysql.com/mysql/170673 shabanip [EMAIL PROTECTED] wrote: hi, just want to know the main benefits of mysql over postgresql. thanks, Payam Shabanian -- For technical support contracts, goto https://order.mysql.com/?ref=ensita This email is sponsored by Ensita.NET http://www.ensita.net/ __ ___ ___ __ / |/ /_ __/ __/ __ \/ /Gleb Paharenko / /|_/ / // /\ \/ /_/ / /__ [EMAIL PROTECTED] /_/ /_/\_, /___/\___\_\___/ MySQL AB / Ensita.NET ___/ www.mysql.com -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: MySQL vs. PostgreSQL -- speed test
Hi! First of all, if I decide to benchmark MySQL vs. PostgreSQL with my application, PostgreSQL will probably be faster. That does not mean that MySQL is generally slower or that I *want* it to look slower. That just means 1) I have no experience in tuning MySQL 2) My application was built with another DBMS in mind Well, after installation and moving my MySQL dbs into PostgreSQL I decided to check if PostgreSQL is as fast as MySQL is. I was shocked... I have made several tests with simple and complicated querys - select, update, insert, drop. PostgreSQL execute those querys even 20 times slower than MySQL. On average, PostgreSQL is 2-3 times slower. Well, while 2-3 times slower looks believable, 20 times slower looks like there is something wrong with your tests. 1) Have you run ANALYZE / VACUUM ANALYZE after loading the data into Postgres? If you didn't do this, its optimizer will be unable to choose the correct query plan as it does not have real statistics. 2) Did you run with default postgresql.conf? That has *very* conservative settings for memory usage. Here is SQLite's benchmark page: http://www.sqlite.org/speed.html It boasts that the thing is 10-20 times faster than PostgreSQL, but this is with *default* configuration, while tuned PostgreSQL (there is a link on the page: http://www.sergeant.org/sqlite_vs_pgsync.html) works considerably faster. So, all people who needs trigers/views/procedures etc. have to be patient and wait for new MySQL versions. And don't you dare switching!!! :] -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: MySQL vs. PostgreSQL -- speed test
MySQL has posted a very interesting comparison on their website. It appears to be a reasonably fair evaluation. PostgreSQL was faster than MySQL in some areas and MySQL was faster than PostgreSQL in most areas. For speed with all of that functionality, I'd be more inclined to look at DB2 rather than MSSQL since DB2 actually has security. :-) Curtis On Monday 14 July 2003 09:35, Jim Smith wrote: I agree with your opinion in 100%, but in my case I need DBMS with features like subselectes/utf-8/stored procedures but the speed is also very important issue. You might have to spend money! You are saying that there is DBMS with all this features and it is as fast as MySQL ? I don't know, but if there is, it is one you will have to pay for. In any case, speed is as much a matter of application design as a DBMS characteristic. As a minor side issue, we did some _very limited_ testing with MS SQLServer 2000 using unicode v ascii queries. Using unicode, queries tended to run at about half the speed compare to using ascii. This was client server, so it is likely that the increased network traffic is to blame, but bear it it mind. -- 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: MySQL vs. PostgreSQL -- speed test
Marek Lewczuk wrote: For everyone who thinks about moving from MySQL to PostgreSQL I have a realy bad news - It's not worth. That's a bit of an overstatement! Why, You may ask... A few days ago I have installed and tested PostgreSQL, becouse I realy need UTF-8 support and subselects. I thought that PostgreSQL will be as good as MySQL but also will give me that features, Optimist! I was shocked... I have made several tests with simple and complicated querys - select, update, insert, drop. PostgreSQL execute those querys even 20 times slower than MySQL. On average, PostgreSQL is 2-3 times slower. Which is *fine* for many applications, although not all. So, all people who needs trigers/views/procedures etc. have to be patient and wait for new MySQL versions. If maximum speed is critical. It's easy to lose sight of the fact that speed is not the only criterion in choosing a DBMS. Features, stability, security, and so on can be just as important or more so. No single DBMS is going to win all the prizes; the trick is to find the one with the right balance. Bruce Feist -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
RE: MySQL vs. PostgreSQL -- speed test
If maximum speed is critical. It's easy to lose sight of the fact that speed is not the only criterion in choosing a DBMS. Features, stability, security, and so on can be just as important or more so. No single DBMS is going to win all the prizes; the trick is to find the one with the right balance. I agree with your opinion in 100%, but in my case I need DBMS with features like subselectes/utf-8/stored procedures but the speed is also very important issue. -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
RE: MySQL vs. PostgreSQL -- speed test
which PostgreSQL version have you testet? If you want compare MySQL and PostgreSQL, than you have to use InnoDB tables. Tests with MyISAM make no sense. Out J2EE Application is working woth PostgreSQL 7.3.3 and MySQL 4.0.13 with InnoDB tables (we need transactions and referencial integrity). and the performance is at moment the same. But we have unoptimized PostgreSQL version. I was testing MySQL 4.0.13 with InnoDB tables and PostgreSQL 7.3.3. Rafal -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
RE: MySQL vs. PostgreSQL -- speed test
Very smart your opinion, I agree at all with you. -Mensaje original- De: Bruce Feist [mailto:[EMAIL PROTECTED] Enviado el: Monday, July 14, 2003 5:37 AM Para: MySQL List Asunto: Re: MySQL vs. PostgreSQL -- speed test Marek Lewczuk wrote: For everyone who thinks about moving from MySQL to PostgreSQL I have a realy bad news - It's not worth. That's a bit of an overstatement! Why, You may ask... A few days ago I have installed and tested PostgreSQL, becouse I realy need UTF-8 support and subselects. I thought that PostgreSQL will be as good as MySQL but also will give me that features, Optimist! I was shocked... I have made several tests with simple and complicated querys - select, update, insert, drop. PostgreSQL execute those querys even 20 times slower than MySQL. On average, PostgreSQL is 2-3 times slower. Which is *fine* for many applications, although not all. So, all people who needs trigers/views/procedures etc. have to be patient and wait for new MySQL versions. If maximum speed is critical. It's easy to lose sight of the fact that speed is not the only criterion in choosing a DBMS. Features, stability, security, and so on can be just as important or more so. No single DBMS is going to win all the prizes; the trick is to find the one with the right balance. Bruce Feist -- 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: MySQL vs. PostgreSQL -- speed test
If maximum speed is critical. It's easy to lose sight of the fact that speed is not the only criterion in choosing a DBMS. Features, stability, security, and so on can be just as important or more so. No single DBMS is going to win all the prizes; the trick is to find the one with the right balance. I agree with your opinion in 100%, but in my case I need DBMS with features like subselectes/utf-8/stored procedures but the speed is also very important issue. You might have to spend money! -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
RE: MySQL vs. PostgreSQL -- speed test
I agree with your opinion in 100%, but in my case I need DBMS with features like subselectes/utf-8/stored procedures but the speed is also very important issue. You might have to spend money! You are saying that there is DBMS with all this features and it is as fast as MySQL ? -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
RE: MySQL vs. PostgreSQL -- speed test
I agree with your opinion in 100%, but in my case I need DBMS with features like subselectes/utf-8/stored procedures but the speed is also very important issue. You might have to spend money! You are saying that there is DBMS with all this features and it is as fast as MySQL ? I don't know, but if there is, it is one you will have to pay for. In any case, speed is as much a matter of application design as a DBMS characteristic. As a minor side issue, we did some _very limited_ testing with MS SQLServer 2000 using unicode v ascii queries. Using unicode, queries tended to run at about half the speed compare to using ascii. This was client server, so it is likely that the increased network traffic is to blame, but bear it it mind. -- 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: MySQL vs. PostgreSQL -- speed test
I agree with your opinion in 100%, but in my case I need DBMS with features like subselectes/utf-8/stored procedures but the speed is also very important issue. You might have to spend money! You are saying that there is DBMS with all this features and it is as fast as MySQL ? I don't know, but if there is, it is one you will have to pay for. In any case, speed is as much a matter of application design as a DBMS characteristic. As a minor side issue, we did some _very limited_ testing with MS SQLServer 2000 using unicode v ascii queries. Using unicode, queries tended to run at about half the speed compare to using ascii. This was client server, so it is likely that the increased network traffic is to blame, but bear it it mind. IPv6 is coming soon and PostgreSQL 7.4 will be the 1st database IPv6-ready! This oportunity give to us the choice to move on to IPv6 network environment. I do believe (tested in my network 6to4 connection) this move can improve the environment performance until 18% in all! Some moves can Checkmate! Robson Oliveira -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
RE: MySQL vs. PostgreSql -- speed test
When I benchmarked PostgreSql against MySql for my application, MySql was 15 times faster, so 18% wouldn't make much difference for me! Andy -Original Message- From: Robson Oliveira [mailto:[EMAIL PROTECTED] Sent: 14 July 2003 15:35 To: [EMAIL PROTECTED] Subject: Re: MySQL vs. PostgreSQL -- speed test I agree with your opinion in 100%, but in my case I need DBMS with features like subselectes/utf-8/stored procedures but the speed is also very important issue. You might have to spend money! You are saying that there is DBMS with all this features and it is as fast as MySQL ? I don't know, but if there is, it is one you will have to pay for. In any case, speed is as much a matter of application design as a DBMS characteristic. As a minor side issue, we did some _very limited_ testing with MS SQLServer 2000 using unicode v ascii queries. Using unicode, queries tended to run at about half the speed compare to using ascii. This was client server, so it is likely that the increased network traffic is to blame, but bear it it mind. IPv6 is coming soon and PostgreSQL 7.4 will be the 1st database IPv6-ready! This oportunity give to us the choice to move on to IPv6 network environment. I do believe (tested in my network 6to4 connection) this move can improve the environment performance until 18% in all! Some moves can Checkmate! Robson Oliveira -- 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: MySQL vs. PostgreSQL -- speed test
As a minor side issue, we did some _very limited_ testing with MS SQLServer 2000 using unicode v ascii queries. Using unicode, queries tended to run at about half the speed compare to using ascii. This was client server, so it is likely that the increased network traffic is to blame, but bear it it mind. Actually, Unicode is much more difficult to handle than the small character encoding sets. Some slowdown is probably to be expected. -- Joel Rees, programmer, Kansai Systems Group Altech Corporation (Alpsgiken), Osaka, Japan http://www.alpsgiken.co.jp -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: MySQL or PostgreSQL
As with most things, depends on what you want to do, what are the requirements ? Jerry - Original Message - From: InfoSysNCA [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Friday, February 28, 2003 5:23 PM Subject: MySQL or PostgreSQL Hi! I've just started working in Linux, but I'd like to know which database is better to use, MySQL or PostgreSQL. Which one would be better in the long run? -- Regards, Neil - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
RE: MySQL or PostgreSQL
Since you're posting on a MySQL list, you could probably expect some biased responses. Could you post more about what you need to use a database for, i.e., what are your needs, wants, what kind of data are you handling, connection rates, serving platform, code base, etc. Here are a few URLs I was able to google up for your specific question: http://www.webtechniques.com/archives/2001/09/jepson/ http://librenix.com/?inode=1266 http://phd.pp.ru/Software/SQL/PostgreSQL-vs-MySQL.html -Original Message- From: InfoSysNCA [mailto:[EMAIL PROTECTED] Sent: Friday, February 28, 2003 11:24 AM To: [EMAIL PROTECTED] Subject: MySQL or PostgreSQL Hi! I've just started working in Linux, but I'd like to know which database is better to use, MySQL or PostgreSQL. Which one would be better in the long run? -- Regards, Neil - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
RE: MySQL or PostgreSQL
Since you're posting on a MySQL list, you could probably expect some biased responses. Could you post more about what you need to use a database for, i.e., what are your needs, wants, what kind of data are you handling, connection rates, serving platform, code base, etc. Here are a few URLs I was able to google up for your specific question: http://www.webtechniques.com/archives/2001/09/jepson/ http://librenix.com/?inode=1266 http://phd.pp.ru/Software/SQL/PostgreSQL-vs-MySQL.html These link seems to be a bit dated. I know they contain obsolete information on mysql. -Original Message- From: InfoSysNCA [mailto:[EMAIL PROTECTED] Sent: Friday, February 28, 2003 11:24 AM To: [EMAIL PROTECTED] Subject: MySQL or PostgreSQL Hi! I've just started working in Linux, but I'd like to know which database is better to use, MySQL or PostgreSQL. Which one would be better in the long run? -- Regards, Neil - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
Re: MySQL or PostgreSQL
Neil, Hi! I've just started working in Linux, but I'd like to know which database is better to use, MySQL or PostgreSQL. Which one would be better in the long run? I guess about anyone on this list will scream Postgre is better, but let me make an exception. Some people consider Postgre the Open Source Oracle because it has all those features people expect a DBMS to have when they migrate from something like Oracle or MS SQL Server. If you need all those features, like stored procedures and views, and you need them _now_, Postgre will certainly be the better choice. If your primary concerns are speed, stability, scalability, and ease of use, you probably will be better off with MySQL. (I'm sure I forgot to mention at least 100 important things in this discussion, and a cross-post to the Postgre list would probably end up in a flame war ;) Regards, -- Stefan Hinz [EMAIL PROTECTED] iConnect GmbH http://iConnect.de Heesestr. 6, 12169 Berlin (Germany) Telefon: +49 30 7970948-0 Fax: +49 30 7970948-3 [filter fodder: sql, mysql, query] - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
