You might also point out the cost difference. Depending on the terms under which you must license it, the MS SQL option could cost $25,000 vs Postgres at ... $0. To a bigcorp that's nothing, but when you start running a bunch of those servers it adds up fast. http://store.microsoft.com/microsoft/SQL-Server-2008-Enterpr...
Personally, I prefer Postgres to MS SQL because 1) it runs on *nix; 2) It's open-source; 3) significantly cheaper; 4) supports recursive queries; etc.
The less you install on the database box, the less stuff you have to upgrade, the less exposure to security critical bugs you have and the less downtime for upgrading you will get.
Mandating .NET framework and IIS is just dumb.
Latch wrote "The goal is to show Windows folk" - there are ways to show things without ridiculing the opposition. It's HN, not some other service, so let's try to keep the level high.
And "Windows folk" may very well not be appropriate terminology. This is a hacker place. There are Windows users, Windows enthusiasts (who tend to severly mod me down when I get carried away) and some Windows developers (the kind that develops Windows, not for Windows) and we should really try to keep everything civilized.
A humorous jab here and there won't hurt, however.
IIS is going to be required when installing parts of MSSQL like SSRS or MSAS since they can interact with client tools and users through IIS.