PostgreSQL Review

HStore is a data type that gives the flexibility to store key/value pair.


What is most valuable?

HStore is a data type in PostgreSQL database that gives the flexibility for storing sets of key/value pairs which is quite an awesome feature.

What needs improvement?

Slow count. As the number of rows exceed a couple million, the count query and queries which get to the depth of the data (like FTS) start taking too much time even with all the right indexes in place.

For how long have I used the solution?

I've used it for two and a half years.

What was my experience with deployment of the solution?

We use RDS Multi - AZ deployment which takes care of it all for us.

What do I think about the stability of the solution?

We've had no stability issues.

What do I think about the scalability of the solution?

There have been no issues with scalability.

How are customer service and technical support?

I've never had an issue with the product, and therefore never had to reach out.

Which solution did I use previously and why did I switch?

We tried RethinkDB a couple of years back, and it was unstable at that time. Also, MySQL didn't have a JSON type back then. We switched to PostgreSQL and never looked back.

How was the initial setup?

I do remember facing problems with the initial setup, but the overall documentation and SO answers has increased since then. New users face much less problem now. But there is still scope for improvement here.

What other advice do I have?

I'd recommend reading Greg Smith's PostgreSQL High Performance.

**Disclosure: IT Central Station contacted the reviewer to collect the review and to validate authenticity. The reviewer was referred by the vendor, but the review is not subject to editing or approval by the vendor.
Add a Comment
Guest