PostgreSQL Review
Updated June 22, 2021

PostgreSQL Review

Anson Abraham | TrustRadius Reviewer
Score 8 out of 10
Vetted Review
Verified User

Overall Satisfaction with PostgreSQL

Using PostgreSQL in all aspects of the company. Using it for our front-end platform to display data. Using PostgreSQL as part of our pipeline looking up reference data. Also using it for reporting purposes as well. The data we have is structured, but with some unstructured data, the jsonb datatype support, also helps us considerably to store dynamic data generation. Helps us scale out our platform.
  • Aggregation of data quickly for report generation
  • Lookups of reference data vs looking up in files
  • organization of data for quick references
  • quick ansi sql functions vs writing out functions in program language
  • regex isn't as strong
  • parallelization of querying of data
  • data distribution natural sharding
  • PostgreSQL extensions
  • PG functions/Stored procedures
  • Support of other languages to work in PG functions like C and python
  • reduce costs in lookup for reference data
  • Easily backed up vs doing backups of files over and over
  • versioning of data, vs backups of db
  • structuring of data to decrease storage costs
PostgrPostgreSQL as a transaction db engine against oracle and sql server works well. TPM wise compared to MySQL and MariaDB, on an evan scale.
SQL function supports, far outweighs compared to MySQL and MariaDB. PG Extensions allow for flexibiltity and scalability. Allows other vendors to create extensions like Citus, PostGIS, TImescale to expand pg into norms not though possible. As a document store, depending on how storing the data, can work better than mongo. However, depending on use case, is where PG might be better than mongo.
built in ETL tools sadly PG doesn't work compared to SQL Server and Oracle. however, w/ extensions flexibility is there.

Do you think PostgreSQL delivers good value for the price?

Yes

Are you happy with PostgreSQL's feature set?

Yes

Did PostgreSQL live up to sales and marketing promises?

Yes

Did implementation of PostgreSQL go as expected?

Yes

Would you buy PostgreSQL again?

Yes

Like any RDBMS, it's perfect for storing structured and sometimes non structured data in the db engine. Transactional data is perfect for PostgreSQL. OLAP data works well.
What it's not suited for, is large document stores. This is where PostgreSQL doesn't do well, compared to mongo. however, newer releases show that it is getting there. Genomic data (raw data) is not suited for PostgreSQL. And PostgreSQL engine alone is not suited for timeseries data. But with extensions in place, works really well.