To be honest, and I'm a total pgsql fan, you usually wind up needing to edit pg_hba.conf and reload to allow external access. But yeah, it is about as easy to me as mysql.
Now, 6.5 was a bit more of an exercise to install.
Sun still sells their servers with PostgreSQL. They still hire and pay the salaries of a couple of the PostgreSQL core developers.
Sadly, those developers, who are world class db hackers, were placed under the management team they bought along with MySQL, who are not world class db hackers.
Happily, the MySQL folks seem to be chafing under the yoke of Sun and leaving one at a time at a rate which will see them all gone within a year.
A commercial license to MySQL before sun bought them was $500. You can buy a whole bunch of commercial licenses, one at a time, when you need them, for a billion dollars.
I still remember installing the last versions of redhat compiled for sparc on an old 32 bit Sparcstation 20 with 4 50MHz CPUs and watching it quite literally trounce a 64 bit 200MHz dual CPU Ultra 20 or something like that running 64 bit solaris.
And it trounced it at everything. PostgreSQL db, apache serving, file serving, everything. It was anywhere from 50% to several hundred % faster. This was back in the RedHat 6.x days with a 2.0 or 2.2 kernel (can't remember which one that had, I think it was 2.2).
I order mine from China via Ebay, preloaded with dd-wrt-v24. Cost about $80 shipped for the high powered WHR-HP-54G model, which is a rocking piece of equipment. We get a lot of interference at the office so we have one on channel 1, one on 6 and one on channel 11. Both WinXP and Linux clients roam seamlessly.
Or what if you're into BDSM or Queening, or like to write Star Trek Slash fiction.
Is it really a good idea that what was previously a semi-private url is now available to your parents, children, boss, coworkers, and business contacts?
This change was not thought out, and the change was made without any warning.
What if you live in Iran and are Gay, and are subscribed to feeds on the subject of your sexuality, and you'd shared that with one or two close gay friends.
You go into work monday morning and everyone is looking at you like you're a freak, and on the way home you just disappear.
It's possible. And no one at google thought to question this new behaviour...
MySQL's docs are set up as a tutorial, and I can't find anything easily in them. If you know anything about databases then reading MySQL's docs is painfully slow.
PostgreSQLs docs are set up with one section being the tutorial, one a user's guide, and one an admin's guide. I find it MUCH easier to find what I want with it, plus it's got a search engine sitting on top of the docs that's fast and accurate for finding the relevant information.
How someone can find MySQL easy and PostgreSQL difficult (or vice versa really) is beyond me. They're both dirt simple to set up and use. Just one is better at keeping your data coherent.
I repeat, if you couldn't find your answer in the pg docs, you can't read.
Sadly, the simple, easy mysql replication is prone to silent failure, so you have to constantly check to make sure your replication really is replicating. Like a lot of features in MySQL replication is one of those that's better for filling in a check box on a spread sheet than actually providing reliable and functioning replication.
All support for PostgreSQL comes from third party companies. PostgreSQL is a community project not a commercial company.
Dozens of the companies there support Debian. Command Prompt and Enterprise DB for a couple of examples.
The problem with MySQL and support is that you have to buy a commercial version if you write non-open source code for it, because of the GPL libs. so, buying support from a 3rd party doesn't cover you.
Not so with Firebird or PostgreSQL where you don't need a commercial contract to write commercial software.
Oracle is lucky to find its butt with both hands most days. They can't even make an rpm for their instant client. Christ, any day-old RHCE can make an rpm out of the.zip file they let you download.
How's a company that doesn't know how to make the simplest of RPMs supposed to compete against RedHat?
Anybody who think's Oracle is gonna beat RedHat at their own game is smoking something milfweed.
I use it because it's incredibly well supported. When I first started using it (WAY back in the day) I found something that didn't work quite right, (actually it did, I just didn't know right from wrong at the time,) posted a message to the mailing lists, and had workaround within a few hours.
Here's a post to the advocacy page from someone in wisconson working as a contractor. His praise mirrors mine, and that of hundreds of other users.
Now that's funny. Anyway, multi-master is on the way with the next version, supposedly. Until then, definitely look at using pgpool. You can use it for synchronous replication, running it on a pair of HA / failover boxes in front of a pair of pg databases. It works pretty well.
There are all different kinds of workloads for database servers. Is the workload mostly transactional, moving around thousands of tiny buckets of data, all interrelated by constraints, foreign keys, and triggers, and all being done by thousands of users at once? Or is the workload one where you're trundling through hundreds of gigabytes of data to mine for certain critical points hidden in them, and only a few users at a time will be hitting the system?
Are we talking about workgroup size database apps, or enterprise class stuff?
Does it need to run well on small machines, with limited I/O, or does it need to be able to take advantage of very large machines, with tons of CPU, RAM, and hard drives?
I would love to see some comparisons of the standard TPC tests. Several of these are already implemented by the OSDL folks on top of PostgreSQL to test it and the linux kernel on top of large machines. I'd love to see them ported to MySQL 5.0 and some comparisons done.
I would REALLY want to see the tests be between PostgreSQL 8.0/8.1, MySQL-innodb, MySQL-isam, firebird, MaxDB, and so on. I.E. NOT just MySQL-isam and PostgreSQL. and not done by folks who can't tune one or the other of the databases, so I think the OSDL folks would be a great choice here, if they wanted to expand their test suites.
1: Slony is about as hard to setup as it is to compile PHP or apache from source and then configure them. Honestly, if you're not capable of configuring slony, you probably shouldn't be administrating servers.
There are a bunch of admin scripts that come with it to setup replication and things like that. Considering it's a pretty new piece of code, it's not bad, mostly lacking in detailed documentation.
2: Notice your replication on MySQL didn't keep you guys up when the db server fried yesterday, so what was the deal? Shouldn't your failover server have just kicked in and all that?
Wow, I can't believe some idiot modded your post as flamebait. It seems well thought out and truthful.
I'd just like to point out that the performance of a database when handling only one user or running one batch file is generally considered uninteresting. It's how it behaves when 100, 1000, or 10000 people are hitting it at once that counts. And it's ability to be placed on bigger, faster hardware to handle load.
In this category, MySQL quickly falls behind. PostgreSQL fairs quite a bit better, and Oracle rules the roost. This from an ardent PostgreSQL supporter, who thinks that, as time approaches infinity, PostgreSQL's performance will surpass Oracle's.
Slashdot Mirror
To be honest, and I'm a total pgsql fan, you usually wind up needing to edit pg_hba.conf and reload to allow external access. But yeah, it is about as easy to me as mysql.
Now, 6.5 was a bit more of an exercise to install.
Maybe because as long as they're complying with the GPL they don't owe them any money?
Sun still sells their servers with PostgreSQL. They still hire and pay the salaries of a couple of the PostgreSQL core developers.
Sadly, those developers, who are world class db hackers, were placed under the management team they bought along with MySQL, who are not world class db hackers.
Happily, the MySQL folks seem to be chafing under the yoke of Sun and leaving one at a time at a rate which will see them all gone within a year.
A commercial license to MySQL before sun bought them was $500. You can buy a whole bunch of commercial licenses, one at a time, when you need them, for a billion dollars.
I still remember installing the last versions of redhat compiled for sparc on an old 32 bit Sparcstation 20 with 4 50MHz CPUs and watching it quite literally trounce a 64 bit 200MHz dual CPU Ultra 20 or something like that running 64 bit solaris.
And it trounced it at everything. PostgreSQL db, apache serving, file serving, everything. It was anywhere from 50% to several hundred % faster. This was back in the RedHat 6.x days with a 2.0 or 2.2 kernel (can't remember which one that had, I think it was 2.2).
I used to have to restart my WRT54G and WRK54G Linksys routers all the time.
I bought a Buffalo WHR=54G with dd-wrt on it a year and a half ago. It has not required one reboot in that time.
It's not the user's fault, except in the fact that he is using a wireless router with crappy firmware.
I order mine from China via Ebay, preloaded with dd-wrt-v24. Cost about $80 shipped for the high powered WHR-HP-54G model, which is a rocking piece of equipment. We get a lot of interference at the office so we have one on channel 1, one on 6 and one on channel 11. Both WinXP and Linux clients roam seamlessly.
Or what if you're into BDSM or Queening, or like to write Star Trek Slash fiction.
Is it really a good idea that what was previously a semi-private url is now available to your parents, children, boss, coworkers, and business contacts?
This change was not thought out, and the change was made without any warning.
What if you live in Iran and are Gay, and are subscribed to feeds on the subject of your sexuality, and you'd shared that with one or two close gay friends.
You go into work monday morning and everyone is looking at you like you're a freak, and on the way home you just disappear.
It's possible. And no one at google thought to question this new behaviour...
Read this about Kapersky:
http://www.uninformed.org/?v=all&a=21
So, you can't read then?
MySQL's docs are set up as a tutorial, and I can't find anything easily in them. If you know anything about databases then reading MySQL's docs is painfully slow.
PostgreSQLs docs are set up with one section being the tutorial, one a user's guide, and one an admin's guide. I find it MUCH easier to find what I want with it, plus it's got a search engine sitting on top of the docs that's fast and accurate for finding the relevant information.
How someone can find MySQL easy and PostgreSQL difficult (or vice versa really) is beyond me. They're both dirt simple to set up and use. Just one is better at keeping your data coherent.
I repeat, if you couldn't find your answer in the pg docs, you can't read.
Sadly, the simple, easy mysql replication is prone to silent failure, so you have to constantly check to make sure your replication really is replicating. Like a lot of features in MySQL replication is one of those that's better for filling in a check box on a spread sheet than actually providing reliable and functioning replication.
All support for PostgreSQL comes from third party companies. PostgreSQL is a community project not a commercial company.
Dozens of the companies there support Debian. Command Prompt and Enterprise DB for a couple of examples.
The problem with MySQL and support is that you have to buy a commercial version if you write non-open source code for it, because of the GPL libs. so, buying support from a 3rd party doesn't cover you.
Not so with Firebird or PostgreSQL where you don't need a commercial contract to write commercial software.
Test cluster slower than single machine
This says otherwise.
Oracle is lucky to find its butt with both hands most days. They can't even make an rpm for their instant client. Christ, any day-old RHCE can make an rpm out of the .zip file they let you download.
How's a company that doesn't know how to make the simplest of RPMs supposed to compete against RedHat?
Anybody who think's Oracle is gonna beat RedHat at their own game is smoking something milfweed.
For dirt simple PostgreSQL synchronous replication, look at pgpool. It has similar behaviour and caveats as MySQL's built in replication.
And it's VERY easy to setup and use.
I use it because it's incredibly well supported. When I first started using it (WAY back in the day) I found something that didn't work quite right, (actually it did, I just didn't know right from wrong at the time,) posted a message to the mailing lists, and had workaround within a few hours.
6 -03/msg00126.php
Here's a post to the advocacy page from someone in wisconson working as a contractor. His praise mirrors mine, and that of hundreds of other users.
http://archives.postgresql.org/pgsql-advocacy/200
Oh yeah, that has worked so well with the whole meth thing. I mean, you can't get that shit anymore, right?
Face it, everytime you do something to stop someone from making one drug, they start making another, more dangerous drug to replace it.
If you could buy coke and heroin at Walgreens, about 98% of all the bad things that happen because of drugs would go away.
Sorry, but it is perfectly legal to copy your own cds and such and re-encode them for your own use. It's getting it from a friend that's illegal.
Look up the home recording act or something like that, which clarified the position on home recordings and such.
Now that's funny. Anyway, multi-master is on the way with the next version, supposedly. Until then, definitely look at using pgpool. You can use it for synchronous replication, running it on a pair of HA / failover boxes in front of a pair of pg databases. It works pretty well.
There are all different kinds of workloads for database servers. Is the workload mostly transactional, moving around thousands of tiny buckets of data, all interrelated by constraints, foreign keys, and triggers, and all being done by thousands of users at once? Or is the workload one where you're trundling through hundreds of gigabytes of data to mine for certain critical points hidden in them, and only a few users at a time will be hitting the system?
Are we talking about workgroup size database apps, or enterprise class stuff?
Does it need to run well on small machines, with limited I/O, or does it need to be able to take advantage of very large machines, with tons of CPU, RAM, and hard drives?
I would love to see some comparisons of the standard TPC tests. Several of these are already implemented by the OSDL folks on top of PostgreSQL to test it and the linux kernel on top of large machines. I'd love to see them ported to MySQL 5.0 and some comparisons done.
I would REALLY want to see the tests be between PostgreSQL 8.0/8.1, MySQL-innodb, MySQL-isam, firebird, MaxDB, and so on. I.E. NOT just MySQL-isam and PostgreSQL. and not done by folks who can't tune one or the other of the databases, so I think the OSDL folks would be a great choice here, if they wanted to expand their test suites.
Two points:
1: Slony is about as hard to setup as it is to compile PHP or apache from source and then configure them. Honestly, if you're not capable of configuring slony, you probably shouldn't be administrating servers.
There are a bunch of admin scripts that come with it to setup replication and things like that. Considering it's a pretty new piece of code, it's not bad, mostly lacking in detailed documentation.
2: Notice your replication on MySQL didn't keep you guys up when the db server fried yesterday, so what was the deal? Shouldn't your failover server have just kicked in and all that?
The showtime was at 1550, and all the other places I looked at were quite a bit later (1730 to 1900 or so).
Wow, I can't believe some idiot modded your post as flamebait. It seems well thought out and truthful.
I'd just like to point out that the performance of a database when handling only one user or running one batch file is generally considered uninteresting. It's how it behaves when 100, 1000, or 10000 people are hitting it at once that counts. And it's ability to be placed on bigger, faster hardware to handle load.
In this category, MySQL quickly falls behind. PostgreSQL fairs quite a bit better, and Oracle rules the roost. This from an ardent PostgreSQL supporter, who thinks that, as time approaches infinity, PostgreSQL's performance will surpass Oracle's.
I went to see it opening day at the Loews near the Grand stop on the Red Line.