I find it a bit annoying that mysql dominates as a storage. There are only two blog engines supporting postgresql (or even one, if you're interested in php software). Why aren't these guys using some DB abstraction libraries?

At least there are also some flat file engines...

I recently made the same choice as Owen:
http://ziphstric.com/blog/archives/2004/06/26/reboot-into-wordpress/

Like Konrad, I'm disappointed that PostgreSQL isn't an option. A primary WordPress developer mentioned: "Database independence isn't a terribly high priority at the moment because there really isn't that demand for it. (You're the first to even mention it.)" so I, like others, are "squeaking" (as a wheel for grease) in this support thread:
http://wordpress.org/support/7/549/
so that developers would know that there is interest because without such comment, the lack of support is self-fulfilling as those with the need for an alternative DB move on and don't hang around the support forums. Konrad, feel free to add your comments there.

Myself, I'd use MySQL on my shared webhosting account because that's what they offer and PostgreSQL at work where I already use that DB for several things.

I hope the discussion of blogging software and associated database is appropriate here since Kasia mentioned she isn't shopping. Um, Kasia, isn't this post somewhat akin to a post:

"I'm not thinking about this topic: hang-gliding in South America. Talk amongst yourselves."

:-)

Kind of disappointing that they don't differentiate between flatfiles and XML — I know that at least Pivot uses XML "flatfiles" to store all its information.

I remember the not so far days when PostgreSQL was a dog, and even then, Id loved it. Most times you need "simple" web access to a database (ie blogging) the extra features provided by postgres are just not useful, and if its slower... there is no point on it.

Today things are really different but most ISP offer MySQL inertially, that's not bad, its just market, and thats what counts when ou start to develop any app, what you see is what you get, at least in a first instance.

Im not really surprised about the WP developers arent too interested in database independency, they should prefer, always to add new features than spend boring-to-death time re-writing and re-checking code fot that pretty small reward. At least any of us can hack the code to use Postgres anytime.

Well its time to undress that PG advocacy polo... :-D

well, it took me about 2 hours to create the entire setup for what i'm using at my spot.. with an already existing MySQL and PHP and webserver.. course, it's probably not exactly the most functional piece of software anyone ever used, but I figure as I need functions, I'll add them.

presuming that my SQL is compatible across the board (and it should be, as I only know the SQL standard, rather than any specific extensions to it), it would take doing:

vi db.php
:1,$s/mysql/pgsql/g

to convert it to use postgresql, or whatever other functions you would want to use. A previous version of my database access code actually had it down to a single line change, if the PHP functions were of the type "dbname_select_db" and such, but i kinda got away from going that far into it, since i really can't see any need for me to ever port db's.

its easy to make a global change in a code file, but most databases arent sql syntax compatible, even less if we talk about SQL-92. Unfortunately.