PostgreSQL Inc. Open Sources Replication Solution 383
Martin Marvinski writes "PostgreSQL Inc, the commercial company providing replication software and support for PostgreSQL, open sourced their eRServer replication product. This makes PostgreSQL one step closer to being able to replace Oracle as the de facto RDBMS standard. More information can be found on PostgreSQL's website."
The defacto standard (Score:5, Insightful)
Re:The defacto standard (Score:5, Insightful)
I have had experience with both Oracle and Postgres, and I would never go back to Oracle...
Maybe I was not using all of it's "Enterprise features", but I find Postgres to be fast, and reliable... Plus I am not constantly bombarded with Oracle spam, like I was when I registered for an oracle devnet account...
Re:The defacto standard (Score:5, Informative)
No source code packages. You can't create a library, like you would in oracle.
When you have an sql error, it tells you the char it occured at, and not much more. Quite annoying if oyu miss a , in a multiline query and have to paste it back.
You can't network two instances so to speak. You can't say.. "select * from slashdot.messages, freshmeat.list where..." Bloody useful for running remote queries over a dedicated line, w/o dump-replicationg stuff.
Not easy to see, verbatim, what queries are running. Well, nothing i've seen so far.
But you know what, I use it, and I like it. 'cuz it doesn't require a java installer and it is simple. But it doesn't hold a light to oracle in some ways
Re:The defacto standard (Score:3, Insightful)
Not important to some, but it is important to those of us that support the same product across many RDBMS.
Re:The defacto standard (Score:5, Informative)
Try adding
stats_command_string = true to your postgresql.conf
then, "select * from pg_stat_activity" for a list of users pids and queries
-Mark
Re:The defacto standard (Score:3, Informative)
I'm not sure what you mean here. You can certainly create
The main feature I see missing from Postgres is tablespaces.
MS SQL Server - Re:The defacto standard (Score:5, Insightful)
Re:MS SQL Server - Re:The defacto standard (Score:3, Informative)
> low or mid range solution
Is it?
> it improves with each iteration.
As does Postgres.
> Our needs aren't high-end, but it handles
> our 300GB databases
That's a lot higher-end than where I'm at
Re:MS SQL Server - Re:The defacto standard (Score:3, Interesting)
In my opinion, Postgres can, to a large degree, fill the same slot that MSSQL is filling now, but that just doesn't appear to be what's happening. Still, MSSQL does cost a pretty penny, especi
Re:MS SQL Server - Re:The defacto standard (Score:3, Interesting)
And pgAdmin III [postgresql.org] just reached beta and is purported to be quite a bit better (than II).
Re:MS SQL Server - Re:The defacto standard (Score:5, Insightful)
No I don't work for MS, no I'm not in bed with thier marketing department, no I'm not afraid of the command line, etc. I just can't deny that it is a good product. In my opinion the best product MS has ever released, and much cheaper than Oracal.
Granted, I still don't trust MS to be secure, so I never let it be internet facing. To get around that you let the web server be internet facing and only allow connections to the db from that one box. They would have to comprimise you from the inside first, or take control of the web server. And there is nothing stopping you from using Linux and Apache on that web server. We do the same thing with Exchange. I don't like exchange nearly as much as I like MSSQL but the VP's demand it so we just put it behind the firewall and relay all the outbound mail to a Unix-based mailserver in the DMZ.
Unix security on the outside, MS useability on the inside.
Go ahead and flame me now, I'm ready for you.
Places SQL Server can never go (Score:5, Insightful)
SQL Server will never run on any version of UNIX. AFAIK, there aren't even (MS-supported) SQL Server client libraries for non-windows platforms. I realize that FreeTDS is available, but such a library would never be used in a highly critical sector.
If you have to integrate multiple platforms, you cannot use SQL server. Closest similar product is Sybase ASE, but Microsoft broke Sybase compatibility on purpose.
I think if people understood how irrationally obstinate SQL Server's platform dependence was, they would look elsewhere. I hope that this attitude holds them below 10% penetration - it certainly has up to now. They are a bit player.
In any case, there is a cheap, new version of DB2 out for $500/copy.
Re:MS SQL Server - Re:The defacto standard (Score:5, Interesting)
It's not as scalable as oracle or db/2 but at the same time it costs 15K per processor which is a hell of a lot of money.
Postgres has just about all the features (and more) of mssql server and it costs nothing. You can buy the EMS postgresql manager [ems-hitech.com] for a few bucks and it's much better the enterprise manager.
BTW. The next version of postgresql will have world class replication the database partitioning.
Honestly in the long run I don't see how people are going to justify spending 15K per processor on a database which only runs on windows, only works well with windows clients (the JDBC driver sucks and is slow as hell), has quite possibly the worst stored procedure language known to mankind. I work with it every day and every day it makes me want to poke sticks in my eye to distract me from the pain. Just today I got pissed because none of the string functions work against text fields (varchar only!). Postgres is so much more fun to work with.
Re:MS SQL Server - Re:The defacto standard (Score:3, Informative)
It's not as scalable as oracle or db/2 but at the same time it costs 15K per processor which is a hell of a lot of money.
I don't want to defend MS too much, but last month we bought Small Business Server [microsoft.com] for about $1500. That included Win2k Server, SQL Server 2000 and a lot of other things.
Re:MS SQL Server - Re:The defacto standard (Score:5, Interesting)
I work with both every day. I don't know why you think they got SQL server right. Lots of lock escalation bullshit, weird locking semantics, goofy functions that only work on some text types and not others, 8K row limit, crappy SP language, the list goes on and on.
Things you totaly take for granted on mysql or postgres trip you up on sql server.
Try passing some XML out of a stored procedure sometime and then tell me how great SQL server is.
Re:The defacto standard (Score:4, Insightful)
One thing I like to point out is that if you have high turnover data, not only do you need frequent vacuums to get good performance, but you also have to *reindex your database* because vacuum doesn't reclaim freed index space. This means if you don't reindex, you could possibly run out of *disk space*. The postgres developers like to reference their laudable MVCC Multi Version Concurrency Control system, but that very row reuse is the cause of the problem in the first place.
I mean, I like Postgres and all, but until they get rid of reindex and vacuum and add a whole lot of extra functionality, there's no way in hell it will replace Oracle.
Re:The defacto standard (Score:4, Interesting)
OR, I can hire an Oracle DBA for $100/hr to slave away maintaining Oracle.
Woot! What a choice. That's it, I'm going back to Oracle. I really miss the contants bugs and patches and the obscene support costs just to call an 800 number and be told "yes, that's a bug, you'll have to upgrade/patch/sacrifice a goat".
I long for that piece of crap SqlPlus, I can't stand using a SIMPLE explain plan, being able to rename columns, JDBC drivers that work, installations that take 3 minutes on a bad day.
I just don't get that with Postgresql, not matter how hard I try to fuck it up.
Yeah, Oracle has some features that Postgres doesn't have, but after 8 years of using Oracle (since 7.1.4 or so through 8.1.7.4 currently), I don't really miss anything except PERHAPS the ability to allocate my own datafiles to distribute I/O.
However, I can't come up with any real reason for that - machines have gotten so fast now, I see vastly better performance on my new dual Xeon 0+1 Linux Postgres boxes than I do on my EMC-backed E6500 Oracle boxes.
I also miss dealing with Oracle sales - people that make used car salesmen seem honest, with obfuscated licensing practices that make Microsoft's BSA invasions and SCO seem reasonable.
I know plenty of crusty Oracle people that swear "dag-nabbits' and 'gosh darnits' and spit on the floor when you mention something like Postgresql. I guess I'm just not old enough to be stuck in such a rut as to not give something else a spin.
I did, and I'll never go back.
Re:The defacto standard (Score:5, Informative)
Oracle runs vacuum as well -- it just has a different name. It's what the undo / redo logs are for, to allow MVCC while maintaining an overwriting storage manager.
Good Thing(tm) (Score:4, Interesting)
Now that Postgress can replicate at DB level other, more interesting things are possible. You can use replication for both failover and performance clustering.
Re:Good Thing(tm) (Score:5, Insightful)
Re:Good Thing(tm) (Score:2)
Oh man, that is sooooo cheating.
Re:Good Thing(tm) (Score:5, Informative)
you can not pull the data out of table and stuff it into another table under even a reasonable workload.
but i understand this is slashdot and technical relevance need not necessarily apply.
Re:Good Thing(tm) (Score:3, Informative)
In my day job we use Oracle because
1.- Management is using the Powered by Oracle (or something like that) to sell the products to our clients
2.- Replication
But in my freelance company we use PostgreSQL exclusively and have experienced the burden of not having a reliable replication software
mySQL gets more publicity (Score:5, Interesting)
Re:mySQL gets more publicity (Score:3, Insightful)
Um, no it doesn't. MySQL's popularity has absolutely nothing to do with it's ability to replace most commercial databases. Even if MySQL is the only open source option, if it doesn't have the features that companies need then they won't switch.
Re:mySQL gets more publicity (Score:2)
And vice versa: MySQL's ability to replace most commercial databases has absolutely nothing to do with it's popularity. In other words: you can put very smart and well designed features to PostgreSQL, but MySQL has more populariy and more of a critical mass. So, in new open source projects people almost always prefer MySQL, while in commercial organizations technology decision makers always (again almost
Re:mySQL gets more publicity (Score:3, Interesting)
I started fiddling with mysql, but moved on to postgresql when my job required it. Mysql is ok for most applications, but I must say that postgre flogs mysql featurewise.
The one thing that mysql excells in, is their greit documentation with very useful comments. I guess that makes learning mysql very easy for beginners, and is a good reason to keep using it, if you compare it to the online postgre docs.
There are some good postgre books though..
Re:mySQL gets more publicity (Score:2, Troll)
You know there can be more than one. (Score:4, Insightful)
MySQL is a good solution for some tasks. Postgres is a good solution of some other tasks. I swear people are so odd. There can be room for more than one OS, Database, Office Suite, and CPU. I really like Postgres and use it for our in house database. I use Mysql for our website's database. Why? because it is what our ISP provides and it works.
How about this... Learn Both.
Re:mySQL gets more publicity (Score:3, Informative)
+----------+
| count(*) |
+----------+
| 80081227 |
+----------+
No, it's not true. (This is just a quick example I pulled out, we have larger tables).
Re: (Score:2)
Re:mySQL gets more publicity (Score:4, Informative)
Version 4.0 of the MySQL server includes many enhancements and new features:
* The InnoDB table type is now included in the standard binaries, adding transactions, row-level locking, and foreign keys. See section 7.5 InnoDB Tables.
Re:mySQL gets more publicity (Score:2)
Re:mySQL gets more publicity (Score:3, Informative)
4 billion rows.
And yes, I've got other tables with more than 1 billion rows.
Re:mySQL gets more publicity (Score:2)
all "pgsql vs mysql" posts below this subject pls (Score:2, Funny)
PostgreSQL fanboy (Score:5, Informative)
Re:PostgreSQL fanboy (Score:2)
Re:PostgreSQL fanboy (Score:2)
supports the objects that the mechanism works on (in this case, into the
database), then all applications built above that level can take advantage
of the new mechanism without reimplementing it.
Think about it. If you have 10 applications that use a db, do you want to
implement clustering/failover once for each application or just once for the
db?
Re:PostgreSQL fanboy (Score:5, Funny)
Awww. Go one, you know you want to really. Here, I'll help get the ball rolling:
I've only every tried MySQL once, and that was for a database course assigment. It didn't have the features required for Question 1, so I switched to PostgreSQL. From this I deduce that MySQL is crap.
There. That wasn't hard, was it? All that is required is a strongly stated, yet uninformed, opinion about either. Now we just need some other contributors...
Re:PostgreSQL fanboy (Score:4, Informative)
So with some trepidation I used PostgreSQL instead. I was concerned with the setup time taking away from the time I learnt actual SQL but after a few hours of learning and tweaking I now have a spanking server running in RedHat and ODBC drivers so I can access it from Win32. I was thrown off to begin with because the 'postmaster' daemon was set to run without enabling TCP/IP support (-i option). But after I figured that out the rest was reasonably easy. I even installed a wonderful util called pgAdminIII which offers hierarchical configuration from a Windows box and was a doddle to use.
So now I have a nice DB that I can play with and pgAdmin has a nice user friendly GUI that I can type SQL in with.
What impressed me most was how *complete* support for SQL seemed to be. MySQL has a big list of gotchas but PostgreSQL seems to be aiming for completeness. This might not be everyone's cup of tea, especially if you want maximum speed but I appreciated the completeness - if something didn't work it was probably my fault! It also has a very complete and thorough manual which surprised me considering how shockingly awful most documentation is for open source.
Anyway, top marks to PostgreSQL. I have no idea if it sucks in a performance environment but it feels very slick to use on a casual basis. With what I know of it so far, I would be seriously consider using it instead of reaching for a commercial (and horribly expensive) option. I suspect for all but the most demanding applications, something like Oracle is just massive overkill.
Re:PostgreSQL fanboy (Score:3, Informative)
Did you try their web site? The little "Downloads" link on their main web page?
Seriously, both 8i and 9i are available as downloads, as long with a ton of other stuff. You'll want a fast link, 9i is a couple or 3 CDs. (I DL'd the developer version with a lot of extra stuff)
installation would be easy.
Well, that's a
Re:The myth of transactions (Score:3, Informative)
Re:The myth of transactions (Score:3, Insightful)
So when data are in the process of changing, they just don't show up in queries? That's horrible. And what happens if the system goes down in the process of changing? You can't roll back; the old data are lost. And you have to manually go in and clear the dirty bit for the broken, half-new dat
Re:The myth of transactions (Score:3, Interesting)
That way, if you were changing someone's address, and phone number, you'd be sure to have a valid address, and a valid phone number. They might be out of sync, but then you'd have a dirty bit to indicate it.
It's pretty easy to do this, with minimal risk, on inserts. If
eRServer and PG Replicator (Score:5, Interesting)
This is indeed good news, as free software always is. But eRServer can only operate in single-master mode, which makes it unsuitable for high-availability kind of work. Single-master systems are good for load-balancing on installations where most of the queries to the DB are SELECTs.
eRServer comes a bit late. We already have PostgreSQL Replicator [sourceforge.net], which is multi-master. Unfortunately PG Replicator is not supported anymore. The latest version it can work with is 7.1, and the project's latest news are timestamped nearly two years ago.
Re:eRServer and PG Replicator (Score:3, Informative)
eRServer has fail over of the master to the primary slave, which makes it just fine for HA applications
Replication in postgres is still quite alive. The website is dead, but the mailing list and development is pretty active.
They were trying to get replication code into the main line 7.4, but that got pushed back. However people are still hgacking away at it.
Good day for OS (Score:2)
A Good Thing(tm)
Corporations are the people Open-Source needs to get on its side. (And, I might add, the OS community is doing a very good job here). They give a project name-recognition, thousands of users, good infastructure, and credibility. PostgreSQL will hopefully begin to compete seriously with Oracle. Another feather in the Open-Source cap.
But (Score:2, Interesting)
Re:But (Score:3, Informative)
believe cross transaction cursors is the most recent.
plPHP (Score:5, Informative)
PostgreSQL has made some pretty nice advancements post version 7+, performance and feature wise. I worked on a intranet where the company spent lots of money trying to get an Oracle solution to work, but found it was way to slow. The suggestion of PostgreSQL, and MS SQL came up. We tested PostgreSQL, and it was acutually faster, and easier to maintain then our Oracle database. The best part was, it was free!
One Step Closer? (Score:3, Funny)
Synchronous Replication? (Score:5, Insightful)
The replication needs to be able to keep all data consistent across multiple servers, without any conflicts. Then, if a particular server goes down, the DNS can simply fail over to a second server.
Once the above has been achieved, then we have a viable alternative to Oracle.
OOS vs. Oracle (Score:5, Informative)
Please! While this may help win the hearts and minds of OOS geeks, it does little to improve their standing in the business world.
Oracle is as established in the database world as Microsoft is on the desktop. This alone would doom any OOS wannabe to quiet places like web server back ends where they already do well anyway ( e.g. mySql ).
Put aside the technical considerations, support, client base, etc and PostgreSQL still offers as much of a threat to Oracle as mySql or dBase. The only real threat I've seen to Oracle supremacy is Microsoft's SQL Server but, of course, that's only in MS shops.
Re:OOS vs. Oracle (Score:5, Insightful)
My forecast, for what it's worth, is that Oracle's database business is in secular decline.
It doesn't matter that mySQL or PostgreSQL can't do everything that Oracle 9i does. That they do some of it, do it better and do it cheaper is what is key.
Five years ago, if you wanted to build a web-based application of any size, you probably went with Oracle. Now there is a free option. At the very least corporate purchasers will use this as a way to extract price concessions from their Oracle salesperson. More likely, in a few places (at first) PostgreSQL and mySQL will work their way into the corporate psyche by being used. Maybe for internal stuff, where budgets are tight. Or where projects are being "hidden" from management. But slowly, open source databases are taking hold.
The next stage is for the enterprise application vendors (SAP, PeopleSoft, Siebel) to start supporting OSS databases. They'll want to, because it lowers the cost of projects to clients, while safeguarding their (falling) application license revenues. Hence, SAP "donating" SAP DB to mySQL. My forecast (number two) is that we'll see all three of the application vendors at least trialling OSS databases with beta customers by end '03. (Yes, I know SAP is already doing it, and that PeopleSoft has issued press releases but no product.)
And in this way, in the same way Linux slipped quietly into corporates, OSS databases will take off.
My only hope is that PostgreSQL, which is a much superior product to mySQL, will get the publicity it richly deserves.
*r
Re:OOS vs. Oracle (Score:3, Insightful)
cough.. db2. cough
You watch, oracle will be looking at MSSQL and DB2 will bitch slap them silly.
SAPDB relicenced to MySQL (Score:3, Informative)
This will probably mean that PostgreSQL will have a very hard time competing with MySQL ! (also see the info [sapdb.org] on the SAPDB webpage)
At the same time the licencing will change to pure GPL (no more LGPL libraries !!!)
Re:SAPDB relicenced to MySQL (Score:2, Interesting)
Re:SAPDB relicenced to MySQL (Score:2, Interesting)
PostgreSQL on the other hand just works, is fast and is smooth as silk. I think even plain old MySQL 4.x is better than SAPDB (yea, it lacks features, but it's a better product overall).
Re:SAPDB relicenced to MySQL (Score:2, Insightful)
Is this only a partial solution? (Score:5, Interesting)
I visited the site, and the commercial site too and it seems this is only simple replication with the master being a single point of failure. F.E.
1. update a row in the master
2. master replicates the update to multiple slaves
3. clients perform select operations against the slaves (nice load balancing opportunity)
4. the master crashes
5. No one can write until the master comes back online.
Here are the steps that seem to be missing:
6. the slaves elect a new master
7. if the old master comes back up it must realize a new master is present and become a slave.
8. clients using JDBC would need some mechanism of finding out what the new master is when an update/insert/delete fails.
Cheers.
Re:Is this only a partial solution? (Score:3, Informative)
C-JDBC may take care of this [objectweb.org]
Re:Is this only a partial solution? (Score:5, Funny)
6a. The slaves realize to their horror that the new master has become as evil as the old master was.
7. if the old master comes back up it must realize a new master is present and become a slave.
7a. Some of the slaves conspire with the old master to assist his return to power.
IANADBA (Score:5, Insightful)
Like the subject says, I'm not a DBA, but I know some pretty heavy-duty ones that say nothing beats Oracle running on HP Superdomes with EMC storage.
Re:IANADBA (Score:5, Informative)
But it is also true that wast majority of Oracle installations are poorely implemented (due to enourmous and unjustyfiable complexity), Oracle's management software sucked (getting better recently), support far from stellar (telephone support hardly usable), yearly costs are sky-high.
I started looking at PostgreSQL and the more I look the more I like what I see - it is conceptually simple, seems to have adequate performance with large tables, JDBC seems to work well too, stored procedures language is very close to Oracle's (I wish for better exceptions handling), and the whole thing is more than adequate replacement for 80% of Oracle installations I have personally seen.
And I have to add that I tried very hard to like MySQL but it did not work for me.
Everything above is IMHO and the usual disclaimers apply.
Re:IANADBA (Score:3, Funny)
Re:IANADBA (a dba's opinion) (Score:3, Interesting)
Postgresql looks like it's better positioned to eat SQL Server's lunch than oracle's to me. First Off, back in the day (3 years ago), when oracle was licensing by 'power unit' - it cost about $1000 / CPU / Mhz. So - a single CPU license for a 1-ghz machine would set you back $100k! Since then they've had to drop prices - because of the market, and because of DB2 - which is far less expensive.
Anyho
Re:IANADBA (Score:3, Informative)
We've recently sold appliances to some high volume customers and I must say that PostgreSQL has had no issues. It's fast for small, medium, and large installations serving up thousands to millions of documents.
We ha
IAAEDBA Re:IANADBA (Score:4, Interesting)
First things first. Online replication is generally considered by professional DBAs a fools errand. You have to babysit and it fails at the drop off a hat for a variety of reasons. The are no good reasons to do replication in the manner they are talking about, unless that is your ONLY option.
There are however, reasons to replicate data. The reasons you want data replicated are usually for one of two reasons: availability or scalability.
To address availability Oracle provides several options that are just plain better than regular/triggered snapshot logging or materialized view refreshing over a network.
The best option is Oracle's Dataguard, which applies redo/archive logs to a duplicate remote databases. You can perform this option at the logical and at the physical level, and you can choose to maximize/guarantee the protection all the way down to best effort. This option provides the ability to have an absolutely current very warm site, a simple command and you're database is up and running.
As for scalability, again Postgres or mysql doesn't hold a candle. There are too many options to list, so I'll discuss the big ones.
Paritioning/sub-partitioning of data. The way Oracle lays out it's logical database block layer and physical OS block layer is absolutely perfect for being able to do anything you want with the database file layout. I can put my OLTP indexes and tables on fast raid10 devices, the historical and warehousing data on raid5 devices, but that's not all. I can increase parallelization of the hardware by putting a single table or index across N devices. The ability to sprinkle files and chop up data anywhere you want, is just one thing that makes Oracle configurable, scalable, and great.
Real Application Cluster (was Oracle Parallel Server). This is a for REAL clustering solution. Oracle allows several servers (can be dissimiliar in capabilities, i.e. some can have 64gig of memory and 12 processors, and then the others could be smaller dual processor machines.) to connect to the same storage (usually shared over a SAN or SCSI direct connect to EMC gear). Each of the servers is connected to a crossover/ipc LAN (we use gigabit) and now each of the servers has access to the same data. One node goes down or needs to go down for maintenance or reconfig, that's ok, the other nodes are online and traffic can be configured to automatically transfers over to the other nodes MID-TRANSACTION and picks up where it left off and the application is none the wiser (i.e. happens in seconds). The nodes share cached data over the fast network, so there is often little need to go to disk. This kind of scalability can not be found on any other database.
<rant>
The real gain for OSS and Oracle, is Linux and Oracle running on Linux. OSS databases are too immature to be let anywhere near real money. I'm not talking about ecommerce money, I'm talking about the millions and bajillions of dollars that flow like water through companies. Linux has Oracle validation and certification, which goes a LONG way in getting Linux into the real datacenters. The price point for the hardware, and the OS and the special deals that Oracle cuts for it are the true win for OSS. The performance is more than there for Linux/Intel solutions, and the price point for Intel hardware is very attractive to companies looking to cut expenses. You still have to pay homage to the Oracle and EMC gods, but even they have felt the crunch, and they too are providing competitive price points.
</rant>
So Postgres is one feature closer to what Oracle was several years ago. So what, this is embarassing. Mysql has had transactions for how long? a few days? Please people, Oracle is not resting on it's laurels waiting for anyone to catch up. They have real companies, with real money, that are real threats to them. IBM and Microsoft. Oracle, is pushing the edge on the database front, and doesn't show any signs of stopping.
Pardon my ignorance (Score:3, Funny)
Re:Pardon my ignorance (Score:3, Interesting)
Another powerful Open Source DB (Score:2, Interesting)
It's not perfect for everything, but if you want scalability, failure resilience and excellent query time, it's well worth a shot.
As an added bonus, it gives you a good excuse to learn erlang, so that LISP-weenies can sneer at you.
enterprise application support (Score:2, Insightful)
StarFish (Score:3, Interesting)
StarFish [bell-labs.com] is a block-level storage system allowing on-the-fly geographic replication, that would work with any database. It was OpenSourced by Lucent a few months ago. It won the Best Paper award at Freenix '03.
[
Top Five Components (Score:3, Interesting)
From the press release:
Does anyone know what the other four components are and whether they're already here?Re:Top Five Components (Score:3, Informative)
It already has them. You have to write the rule yourself, so it's not nearly as convenient as in Oracle, but it's possible. It's something like:
Now, I could see why you'd really want these to be automatic, as updating the definition of these rules manually is a maintenance headache. But
Nice to see OSS moving forward (Score:4, Insightful)
I listen to folks at work talk about why we "need to move to a *real* database at some point", and it always comes down to the fact that they've bought into the marketting, and when they examine their reasons (if they are willing to), solutions like PostgreSQL or MySQL are a whole lot better choices than the "real" database choices out there.
Bravo guys!
PostgreSQL vs MySQL (Score:5, Insightful)
What the posters here need to realize is that it is exactly this competition that is driving the projects. If MySQL was not given the press and did not have its cult following, we would not see this pace of development for pgsql. The developments for FreeBSD really improved to compete with Linux although their developers claim they are not competing... they do have the fear Linux will supplant them.
What is interesting to note is that in most of these project wars, both projects really survive and get two different niches of their own. This was true of bash vs csh, BSD vs SYSV, BSD vs Linux, KDE vs GNOME, and now MySQL will become the standard entry level database and pgsql the higher level.
I use pgsql because my databases have complicated requirements that MySQL cannot meet. Yet MySQL is the quick and dirty solution when I have to set things up fast. For all new learners I always suggest MySQL. For people thinking of replacing or duplicating their ERP systems, I always suggest pgsql. I even know how to program in sleepycat's db and know where it should replace mysql in smaller embedded systems and where the mysql license cannot be used.
I believe this competition is coming to a close since pgsql has taken a big lead over MySQL in features, and therefore made itself more difficult to deal with especially for newbies. All I can say about the postgresql replication is bravo, and hope MySQL doesnt follow suit so it remains the simple fast and easy database in its own niche.
Compitition (Score:4, Insightful)
Myself, I use Linux/KDE/pgsql ~ 95% of the time. But there are times where I like BSD (awesome security), Gnome (i like their simple interface and their apps are nice in a number of areas), and Mysql (want a fast mostly read DB? Nothing beats Mysql in the true relational arena (dbm/gdbm/sleepycat can for simpler relations)).
Lets hope that real compitition never stops.
Re:Postgre sucks! (Score:5, Interesting)
Ever heard of InnoDB [mysql.com]? MySQL lets you choose -- on a table-by-table basis -- exactly what parts of your application need to support transactions, foreign keys, etc.
Odd, neither Slashdot [mysql.com] nor Yahoo! Finance [mysql.com] seem to be having corruption problems...
Adding extra memory, CPUs, or slave servers obviously has no impact on server performance. (Yes, replication is... clumsy, at best, but depending on the application, it can work quite well.)
Compared to Postgres?
Re:Postgre sucks! (Score:5, Informative)
For how many server computers you want to order an evaluation copy, or 1-year licenses (390 euros or 450 US dollars each), or perpetual licenses (990 euros or 1150 US dollars each); discounts are available for large volume orders.
This is from http://www.innodb.com/hotbackup.html
Re:Postgre sucks! (Score:2, Informative)
Allows to backup a running PostgreSQL database.
No locks.
Does not disturb normal database processing.
Consistent copy.
Free.
Re:Postgre sucks! (Score:2, Informative)
Have you actually used MySQL and tried to break it? The damn thing is hopeless in comparison to PostgreSQL, Oracle and even SQL Server:
InnoDB transactions don't include the DDL so your create table/index etc... WON'T roll back when you cancel a transaction - so really mysql transactions are for inserts, updates and deletes ONLY. Don't give me this crap about inno
ok.. (Score:2)
Re:Postgre sucks! (Score:3, Insightful)
This makes no difference if you write your application correctly and check your data going in for VALIDITY. It shouldn't be the DB server's job to enforce
Re:Postgre sucks! (Score:2)
Er, well, I have mysql installed on my windows dev machine and it's scurrently consuming 2.848 MB. I suppose that doesn't fit into 640k, but there you go.
Troll.
Re:Postgre sucks! (Score:2, Interesting)
<tr
Re:Excellent (Score:5, Informative)
Re:Excellent (Score:3, Funny)
It'll probably get there about two years after KDE 3.1. So, about 2007.
Re: Excellent... not quite... use FIREBIRD (Score:4, Interesting)
However, I was able to port the entire application to Firebird [sourceforge.net]--IMHO a far better database.
Re: Excellent... not quite... use FIREBIRD (Score:4, Informative)
Just to clear up any confusion:
Re:WOOHOO!! (Score:5, Insightful)
Re:WOOHOO!! (Score:2)
Re:WOOHOO!! (Score:2)
Let's see, with Oracle, I can call 24/7 and get access to a complete idiot with a phone who can say he's escalated it and give me a cute little number. I have to trust them that they do actually have qualified engineers working on it and not some lame-o that just got hired last week. The amount of time it takes to reach a senior developer is unknown.
With PostgreSQL, most emails to p
Re:WOOHOO!! (Score:2)
How does charging lots of money = evil?
Re:WOOHOO!! (Score:3, Informative)
In addition, you can't really take it for a test drive, because it takes MONTHS to set up, even for small installations (it was a year process for a 300-employee com
Re:Terminate RDBMSs (Score:2)
And then watch the DBA break down and cry as the UPS fails during a blackout...
Re:Terminate RDBMSs (Score:2)
Geez... Now what whould be the point of object prevalence? Perhaps the idea is to make sure the objects prevail, no matter what happens. Perhaps you don't know what you are talking about?
Re:PostgreSQL is a non-entity... (Score:2, Informative)
Re:OraSlave (Score:3, Insightful)