Hacker News new | past | comments | ask | show | jobs | submit login

If you want to use this, you will port your code, run your tests, fix an issue here or there as needed, and develop for Postgres for now on.

None of those steps is particularly risky. If any of the steps that may fail brings an insurmountable obstacle, you ditch the project and go back to where you started.

> People pay for commercial DB's for a lot of reasons - including having someone to call at 3am when things go bad.

Oh, the old support excuse for proprietary software. The Oracle support is excellent, but good hope getting anybody to help you at 3am. Good luck getting anybody to actually help you in less than 24 hours anyway. None of the big proprietary software distributors offer anything like this. Oracle is way ahead of the competition on that they will even actually help... kind like you get when you hire a local company to support Postgres for you.




The scale of your operation and license subscriptions matters for the level of support you receive, naturally.

Big Microsoft shops, like state governments routinely have Microsoft staff fly out and work closely to bring new services online, etc. You cannot expect that level of service if you're just paying for a single database instance, of course.

IBM's support is also legendary - you will get a person on the phone at 3am, and even have a service technician onsite in the morning if needed. Personal experience with this one - they'll fly someone in from out of state to replace a hard drive if it means meeting their service levels.


> you will get a person on the phone at 3am

And that person will do nothing else but waste your time.

What is the natural result of any interaction with Microsoft support too. Not limited to 3am calls.

Anyway, I wonder how RedHat has adapted to the IBM culture. I haven't dealt with software support for a while now, what I'm very grateful for.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: