Re: [GENERAL] Re: PostgreSQL vs Oracle vs DB2 vs MySQL - Which should I use?
On Fri, Feb 16, 2001 at 09:36:23AM -0500, Bruce Momjian wrote: > > Funny you should mention PHP. I talked to Rasmus about the email volume > when I first met him in the fall. He said the volume of email is so > great that just reading the subject lines takes a long time. > > We aren't there yet, but we are heading in that direction. One thing > some of us have done are to take full-time jobs with PostgreSQL so we > can handle the increased load. Second, I have started to skip emails > with subjects that contain obvious questions, relying on other users to > answer these. When several people post on the easy question, I start to > suspect there is some issue there and start reading. > This could eventually be handled the way they do with Usenet lists. When the volume finally gets too high, split the lists into more specialized sub-lists. (Though obviously you want to continue to improve the docs as well.) The busiest list I was ever on was the debian-help list. This one might be even busier. Paul
[GENERAL] Re: PostgreSQL vs Oracle vs DB2 vs MySQL - Which should I use?
On Fri, 16 Feb 2001, Mitch wrote: > Helpful developers doesn't go near far enough.. > > I've seen (and still do see) commercial support that isn't up to the grade > of support I have gotten from the -general and -hackers lists. I can ask any > question and I *always* get a response within minutes from one of the core > developers.. I have yet to have a question go un-answered and I've been on > the list for a pretty long time! It just doesn't get much better than that > to me. What I really like is the truth. The developers will tell you straight out that a feature is broken and they may even say they don't know how to fix it properly yet. Whereas for some commercial products (not all, some have excellent support), I've had cases where they deny that there's anything wrong. Cheerio, Link.
[GENERAL] Re: PostgreSQL vs Oracle vs DB2 vs MySQL - Which should I use?
> Yah. What I find is the developers set the general tone/culture of the list. > This affects the type of responses/support you get even from the other list > subscribers. So it's quite good here where you have kind and helpful developers. Helpful developers doesn't go near far enough.. I've seen (and still do see) commercial support that isn't up to the grade of support I have gotten from the -general and -hackers lists. I can ask any question and I *always* get a response within minutes from one of the core developers.. I have yet to have a question go un-answered and I've been on the list for a pretty long time! It just doesn't get much better than that to me. Thanks to all the people that have put up with my strange (and sometimes amusing) questions! -Mitch
[GENERAL] Re: PostgreSQL vs Oracle vs DB2 vs MySQL - Which should I use?
On Tue, 13 Feb 2001, Paul M Foster wrote: > Let me echo this. I have _never_ been on a list where so many of the > developers of a product were subscribed as well. And these folks > provide _very_ considerate and clear assistance. Hats off to them. Yah. What I find is the developers set the general tone/culture of the list. This affects the type of responses/support you get even from the other list subscribers. So it's quite good here where you have kind and helpful developers. As for the original question. I find in a corporate environment it boils down to who you want blame to fall to - blame tends to flow down the payee channels. For accounts and order processing it's probably Postgresql/Oracle/DB2. If you have a resident DBA, get the DBA to pick the database. If the DBA is you well then if you have lots of money you may wish to pick Oracle/DB2 - because if you're new to DB stuff and doing major stuff, you'll probably need to blame someone else ;). If there's very small budget then it's Postgresql, but make sure your bosses know that they're getting a lot more than what they paid for ;). That said, installing, configuring and maintaining Postgresql is a lot easier than Oracle/DB2. For instance there's a lot more "backward compatibility" ugliness in Oracle. So in a less "corporate" environment I'd say go with postgresql. Performancewise with these three the main factor is probably going to be how the DBA organises the data and forms the queries. The DB engines of all 3 are quite decent once you know about their various quirks[1]. Cheerio, Link. [1] I've come to a conclusion that if it doesn't have strange quirks it's not an RDBMS.
