Interview With The PostgreSQL Team
Gentu writes "OSNews features an interview with some members of the PostgreSQL team regarding the much needed replication feature, their competition to MySQL, their future plans and a "native" Windows/.NET port."
I can't wait until PostgreSQL has these features. Once that happens Oracle will have to run and hide. Yeah I know a ton of people will reply to this saying that Postgres doesn't have nearly the feature set of Oracle and the like, but I think for 90% of people that need a fault-tolerant database the featureset of Postgres is more than enough.
-----BEGIN GEEK CODE BLOCK----- Version: 3.12 GIT d? s: a-- C++++ UL++++ P++ L+++ E- W++ N o-- K- w--- O- M+ V PS+ P
I've been trying to learn Postgre's useage and try it on production systems. I started out with the MySQL that the developers were sarcastic about, but realized the very different applications that need databases.. Ever since, I've been delving into db3 for lower end data management (for dbase-replacement apps) and Postgresql for higher end.
I dont think its fair to compare Postgre with MySQL. Postgres developers work so hard to point at their features, but not all web backends require transactions or even subqueries. The basic Postgresql installation is a bit of a pain to get up and running with a basic database, which keeps pushing new users to MySQL, and the feature list gets repulsive there too.. But for applications like managing the
I like to think Postgre as a middle to large-scale database, with DB2 and Oracle taking the 'large' end of the spectrum and mysql,minisql and the sleepycat way of dealing with data, at the 'small' end. Mysql's niche happens to be at a sweet spot where developers seek ease, speed, simplicity and functionality with PHP, Perl, C and scripts.
"Give orange me give eat orange me eat orange give me eat orange give me you." -Nim Chimpsky
I'm Peter Eisentraut, I'm quoted in this article, but I never knew I was doing an "interview".
We're using contrib/dbmirror in production, and it works fine, if your definition of fine is "ok". We run the mirroring process every five seconds, and have a few triggers and whatnot written to facilitate a hot-swap failover.
Our transactional volume isn't high enough yet to cause us problems (less than 30 a minute), but for now, this is ok. I'm tracking the "real" pgreplication stuff, and occasionally take a desultory trip into WAL land, when I can grab a minute.
'jfb
To spur "enterprise Linux," Big Bang, the distributed two-phase commit.
Terse? Not really. I find PostgreSQL's shell to be far easier to connect to and use than mySQL's shell. Indeed, PostgreSQL has *very* verbose help, which is a major bonus during development. I can find nothing terse about it. I couldn't figure out mySQL, but PostgreSQL's documentation got me up and running in about 10 minutes.
Heute die Welt, morgen das Sonnensystem!