That's a good first step, but that's not enough for many companies.

If you're an enterprise customer with IBM, Oracle, or Microsoft, you know that you can have someone onsite within 24 hours if you have a critical failure, sometimes even sooner. You know that you can have people engaged 24/7 for as long as it takes to get you back up and running and you'll have not just technical people, but also incident managers who will keep you updated and help the engineers locate additional resources. They'll have someone sit in a conference bridge around the clock if you want, ready to provide updates.

Enterprises are also thinking about long time spans. With IBM, Microsoft, Oracle, Redhat, and others, they generally guarantee at least 10 years of support for their products, plus the ability for custom agreements that go beyond their normal support dates. Offering 3+2 is a good start, but that's not long enough. Remember, many (probably most) banks still have applications written in COBOL running.

Don't get me wrong, I think everyone should look at all the available options - free and paid. At the end of the day, though, there are a lot of projects where the risks and expected application lifecycle pretty much mandate the level of support you only get from the big companies.

The drive time from the nearest EnterpriseDB office to my office is at least 12 hours (and that is probably quite a bit below the median). To the nearest Oracle office it's a 15 minute walk. That is probably going to have some effect on the call out time for technicians.

But then Oracle doesn't do support directly, it is one of their partners. So maybe you should look for some EnterpriseDB partner ;)

Point taken. I stand corrected.