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
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
On 7/26/07, Andrew Armstrong wrote:
* Table 1: 80,000,000 rows - 9.5 GB
* Table 2: 1,000,000,000 rows - 8.9 GB
This is a generic star schema design for data warehousing.
I have read that it is better if perhaps partitioning is implemented, where
new data is added to a partitioned
partitioning.
Cheers
- Andrew
-Original Message-
From: Jochem van Dieten [mailto:[EMAIL PROTECTED]
Sent: Friday, 27 July 2007 6:44 PM
To: mysql@lists.mysql.com
Subject: Re: Data Warehousing and MySQL vs PostgreSQL
On 7/26/07, Andrew Armstrong wrote:
* Table 1: 80,000,000 rows - 9.5 GB
On Thu, 2007-07-26 at 18:37 +1000, Andrew Armstrong wrote:
Hello,
I am seeking information on best practices with regards to Data Warehousing
and MySQL. I am considering moving to PostgreSQL.
* Table 1: 80,000,000 rows - 9.5 GB
* Table 2: 1,000,000,000 rows - 8.9 GB
Just
Hello,
I am seeking information on best practices with regards to Data Warehousing
and MySQL. I am considering moving to PostgreSQL.
I am currently using MySQL as the database of choice. I am now running into
performance issues with regards to large tables.
At the moment, I have the
On 7/26/07, Andrew Armstrong [EMAIL PROTECTED] wrote:
snip
Information is deleted from this DW as well, after every five minutes.
The data being recorded is time sensitive. As data ages, it may be deleted.
Groups of samples are aggregated into a summary/aggregation sample prior to
being deleted.
: Re: Data Warehousing and MySQL vs PostgreSQL
On Thu, 2007-07-26 at 18:37 +1000, Andrew Armstrong wrote:
Hello,
I am seeking information on best practices with regards to Data
Warehousing
and MySQL. I am considering moving to PostgreSQL.
* Table 1: 80,000,000 rows - 9.5 GB
Warehousing and MySQL vs PostgreSQL
On 7/26/07, Andrew Armstrong [EMAIL PROTECTED] wrote:
snip
Information is deleted from this DW as well, after every five minutes.
The data being recorded is time sensitive. As data ages, it may be
deleted.
Groups of samples are aggregated into a summary
so much due
to the
large table size.
-Original Message-
From: Wallace Reis [mailto:[EMAIL PROTECTED]
Sent: Friday, 27 July 2007 1:02 AM
To: Andrew Armstrong
Cc: mysql@lists.mysql.com
Subject: Re: Data Warehousing and MySQL vs PostgreSQL
On 7/26/07, Andrew Armstrong [EMAIL PROTECTED
more concerned as to why inserts begin to slow down so much due to the
large table size.
-Original Message-
From: Wallace Reis [mailto:[EMAIL PROTECTED]
Sent: Friday, 27 July 2007 1:02 AM
To: Andrew Armstrong
Cc: mysql@lists.mysql.com
Subject: Re: Data Warehousing and MySQL vs PostgreSQL
On 7/26/07, Andrew Armstrong [EMAIL PROTECTED] wrote:
Do you have a suggestion to how this should be implemented?
Data is aggregated over time and summary rows are created.
I think that you didnt design correctly your DW.
It should have just one very larger table (the fact table).
Data should
To: Andrew Armstrong
Cc: 'Wallace Reis'; mysql@lists.mysql.com
Subject: Re: Data Warehousing and MySQL vs PostgreSQL
Wallace is right, Data Warehousing shouldn't delete any data. MySQL
isn't as robust as say, Oracle, for partitioning so you need to fudge
things a little. I think partitioning
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]
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
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
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
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
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
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
hi,
just want to know the main benefits of mysql over postgresql.
thanks,
Payam Shabanian
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
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
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
Hello group,
For everyone who thinks about moving from MySQL to PostgreSQL I have a
realy bad news - It's not worth. 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
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
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
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
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
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
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 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
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
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
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
Hi,
Does anybody know of any MySQL vs. PostgreSQL recent article?
I mean, that it covers MySQL 4.x and PostgreSQL 7.3.x
Thanks in advance,
Juan
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Philip Johannessen wrote:
Im currently in a debate with someone who prefers PostgreSQL. He says that
MySQL is unstable etc. Can you please give me examples of some well known
sites built on MySQL so I can tell him that MySQL rocks?
PostgreSQL: Unless something has changed in the more recent
36 matches
Mail list logo