PostgreSQL Review

Array and JSON fields is good. It is too restrictive in cross-table/view constraints.

Valuable Features:

  • Updatable views (also over multiple tables)
  • Array and JSON fields
  • Point-in-time backup and recovery (WAL files archiving)

Room for Improvement:

I find, sometimes, that it is too restrictive in cross-table/view constraints. This is very annoying as I needed to change a field definition from VARCHAR(10) to VARCHAR(30) and, having a group of views depend in it, the only solution was to implement a function that would:

  • Read the view definitions
  • Store them
  • Delete the views
  • Update the field definition
  • Recreate the views

It took me like three or four hours (and caused a lot of stress) to make such a simple change. To me it looks a bit too overkill, especially nowadays that application requirements and implementation change so often.

Use of Solution:

I have used it for one and a half years.

Deployment Issues:

There were no problems with deployment.

Scalability Issues:

The app hasn’t had the need to scale much yet.

Initial Setup:

It was quite straightforward.

Implementation Team:

I implemented it myself and don’t have any particular advice about it. Today I would consider implementing it via Docker.

Other Solutions Considered:

I've only used online open source resources and would say there's not as much as there is for MySQL. Sometimes it took me some time to find a good solution to the more unusual scenarios

**Disclosure: I am a real user, and this review is based on my own experience and opinions.
More PostgreSQL reviews from users
...who work at a Comms Service Provider
...who compared it with MySQL
Learn what your peers think about PostgreSQL. Get advice and tips from experienced pros sharing their opinions. Updated: July 2021.
521,637 professionals have used our research since 2012.
Add a Comment
ITCS user