PostgreSQL - A great database at a great price.
September 18, 2017

PostgreSQL - A great database at a great price.

Louis Marceau | TrustRadius Reviewer
Score 10 out of 10
Vetted Review
Verified User

Overall Satisfaction with PostgreSQL

In my previous and current organisation we develop applications using PostgreSQL as one of or the database of choice to store application data. I have used it in both client-server implementations where it is used to store data for a single company as well as in cloud implementations where it is used to store data across many companies and users. Recently I have used it as the database in a data warehouse solution, data mining millions of rows.
  • The biggest reason I have used postgreSQL and continue to use it in places where I work - is the cost. There is none. It is a great feature rich database which doesn't cost you anything.
  • When using properly design database, tables, and relationships - we have not ran into any particular database limit
  • For my uses I have none. Currently we are developing a new application using the lastest version of PostgreSQL and are exploring any limitations.
  • I find that there is just positive ROI when using postgreSQL. SQL from one database to another and concepts are fairly universal. Most third party support PostgreSQL. There are many db reporting tools that support PostgreSQL as well.
  • negative ROI. none.
The features between these database are quite comparable - except for possibly MongoDB. MongoDB being a different type of database and geared towards big data - I don't compare it to PostgreSQL. The other two I have used and would say PostgreSQL does fairly well when compared with them. Again, the feature set being similar and the cost $0 does give PostgreSQL an advantage. Unless I have a specific integration need for Oracle or MSQL - I will generally always consider PostgreSQL.
I have used it as a data warehouse, client specific database for a web application, test systems where each developer has their own schema for testing, local application database, and as a remote application database. It has worked well in each of these situations. Currently the main area where I would not use PostgreSQL is when I need an embedded database - in which case I would look at something like SQLite or other.