Interview with Josh Berkus of PostgreSQL 41
SilentBob4 writes "The PostgreSQL database project has recently released Version 8.0, which was received with quite some fanfare, mostly due to its first-ever Windows port. Mad Penguin talked with Josh Berkus, one of the core team members, to find out how 8.0 has fared since its official release on January 17, 2005. Full interview."
Ever since I ran into unicode ... Pgsql has rocked (Score:4, Informative)
Ever since I started using transactions in pgsql, I haven't looked back to mysql land. All I now need is the Postgres-R (replication) stuff to work out of the box (like it does for mysql). I don't know if transaction speeds might be hit by replication or not.
Also great win32 installer - thank god the pgsql jdbc components aren't GPL. (it's a thin edge of the wedge to get it used for in house projects).Re:Ever since I ran into unicode ... Pgsql has roc (Score:5, Informative)
Look into Slony. It's an addon project, but replication for PostgreSQL will always be an addon so that it works across multiple backend versions.
It's fairly straight forward to setup a master/slave scenario, and PgAdmin is currently working on GUI tools for managing it.
Re:Ever since I ran into unicode ... Pgsql has roc (Score:4, Informative)
Don't bother with Postgres-R -- use Slony. It works fantastically well.
Re:Ever since I ran into unicode ... Pgsql has roc (Score:1)
> (it's a thin edge of the wedge to get it used for
> in house projects)
Please read the GPL.
In house projects are NOT considered as redistribution of the code, so you can keep your changes for yourself.
Re:Ever since I ran into unicode ... Pgsql has roc (Score:3, Insightful)
How to treat one's friends. (Score:2)
Re:Inspecting my enterprise? (Score:2)
Re:How to treat one's friends. (Score:2)
You do realize that these are contradictory statements, don't you?
Re:How to treat one's friends. (Score:2)
Re:Ever since I ran into unicode ... Pgsql has roc (Score:2)
Re:Ever since I ran into unicode ... Pgsql has roc (Score:2)
MySQL supports transactions http://dev.mysql.com/doc/mysql/en/transactional-c
Incentive to switch (Score:3, Insightful)
I think this is interesting. Now, I'm no PostgreSQL cheerleader, but they're certainly one of the top open source projects going around. It seems to me that if the PostgreSQL team had leveraged their position and spent more time developing for open operating systems, businesses would be given the incentive to switch. Instead, they've chosen to accomodate the enterprise windows crowd. Of course, this will be great for their marketshare. But it just seems like a missed opportunity given the bigger picture.
Re:Incentive to switch (Score:2, Insightful)
PostGres coming to Windows is good - because trying a new application is easier than trying a whole new operating system. Once someone knows what your app is, there's going to be far less resistance to trying it out on another OS. Th
Re:Incentive to switch (Score:2)
Re:Incentive to switch (Score:3, Insightful)
Since we know the pain of being forced to use an OS we dislike, let's try to be the Better Man here. If the tables someday turn, let's continue to encourage that apps get ported to every OS under t
Re:Incentive to switch (Score:5, Insightful)
This argument made its rounds a while ago. I think it was when a prominent KDE developer write about how it was a bad idea to port applications to Windows. The counter argument is that they're letting people switch to open source software a little bit at a time (which is easier). Once people are comfortable with using cross-platform applications exclusively, the Windows platform no longer has an unfair advantage. At that point, different operating systems can be judged on their own merits, instead of simply on the availability of application software.
Re:Incentive to switch (Score:2)
But let's not worry; it's too late now. It'll always be too late. Fortunately!
(If you don't get it, don't mod)
Fatal Flaws (Score:5, Interesting)
Firstly, the broken Unicode support, which arose because certain collation functions doesn't work well on UTF-8 (PostGre uses UTF-8, Win32 prefers UCS-2). The tone you get from reading the bug/support forums are disdainful, pointing the problem to Win32 libraries and suggesting that it should not be in the confines of the PostGres team to fix Windows bugs. Nevertheless, if they already put so much effort to porting to Win32, it seems strange that they are adopting such a stance instead of proactively trying to fix that problem.
Secondly, there is no support for the Win1252 code page, which is very commonly used in English Windows, while mind-bogglingly, there seem to be all other code-pages from Cyrillic to Arabic. This makes migration of data from SQL Server very difficult, and using Latin-1 doesn't help when it encounters characters like `. Yes, Windows should be whacked on the bottom for introducing such shitty incompatibilities but that doesn't solve the problem. The other solution to this problem - to convert to UTF-8 instead - is unavailable because of first problem.
I have been trying to persuade my company to shift from SQL Server to PostGreSQL on Windows (for some reasons, we cannot move over to Linux yet). But after hitting these brick walls - I've giving up. Here's to hoping!
Re:Fatal Flaws (Score:1)
Re:Fatal Flaws (Score:2)
Would you care to be mopre specific? Is it a bug in their implementation or a limitation of UTF8 itself? (and if so, explan why)
Re:Fatal Flaws (Score:4, Informative)
First Windows port? (Score:3, Informative)
mostly due to its first-ever Windows port.
No, PostgreSQL has been working on Windows for years. This was just the first version where Windows was an officially supported platform.
Re:First Windows port? (Score:3, Informative)
Whether the former constitutes a 'Windows port' or not is semantics.
Re:First Windows port? (Score:3, Informative)
It sure feels like a "First Windows port" (Score:1)
I consider myself to a competent developer with some SQL skills and bit of DBA knowledge albeit mainly in MSSQLServer.
The PostgreSQL 8.0 for windows installation process was very difficult and ultimately unsuccessful. Anyone who uses the Win platform for development will reject PostgreSQL like I did due to difficult getting it up an running.
I am looking forward to PostgreSQL maturing relative to the windows port. Let's hope the team feels the same way!!
Re:It sure feels like a "First Windows port" (Score:4, Informative)
You got to be kidding right? There is a packaged Windows installer for 8.0.1 [postgresql.org], and as database installer goes, this got to be one of the most no-brainers around. It even installs the documentation, pgAdminIII and the necessary ODBC and OLE-DB drivers.
Re:It sure feels like a "First Windows port" (Score:1)
I haven't found a graphic query editor analog to MS access's one yet, but I guess it's a matter of different style - scripting instead of GUI. But installation? A breeze.
Kudos to Josh and the PostgreSQL team! (Score:3, Interesting)
Re:Kudos to Josh and the PostgreSQL team! (Score:3, Funny)
MySQL can run SELECT * faster than any database anywhere
Re:Kudos to Josh and the PostgreSQL team! (Score:2, Insightful)
Uh...everyone?
Without data integrity, that just means you can get a wrong answer very quickly.
Re:Kudos to Josh and the PostgreSQL team! (Score:2)
There is a buzz around (Score:3, Interesting)
Re:There is a buzz around (Score:1)