PostgreSQL Reviews

We use it when we have large OLAP workloads and data rates that normal SQL can't replicate across all our systems – unstructured data where we can use code for everything. We use it with unstructured data.

We usually process data in batches, pushing the data to our data pack daily. So, PostgreSQL has handled high-volume transactions for us.

Our data security primarily includes encrypting our databases. We also use field certificates, and all data is replicated in an encrypted format.

We primarily use normal SQL queries. With a SELECT query, we consume the data and then push it forward.

Use cases include querying data warehouses and databases to fetch data for clients already working on PostgreSQL. 

We also use Postgres for building reports.

It's a transactional database, so we use Postgres for most of our reporting. That's where it's helping.

I use the solution in my company for relational data and transactional data storage as part of our microservices. We use the tool as a relational relational data storage.

The tool's most valuable feature is its simplicity. As it is SQL-based, the tool is quick to deploy and adapt. The open-source PostgreSQL tool is very useful for us. Basically, it's a simple small DB maintenance tool.

I haven't gone too deep into the tool's technical side.

We use PostgreSQL in our company for test systems.

PostgreSQL is very powerful, easy to manage, and has many features.

In my current company, we use a wide array of databases, like, Cassandra, Elasticsearch, MongoDB, and Postgres. But here, We specifically use Postgres for transactional purposes.

Since, NoSQL database does not have any, like, transactional-based things. It is called asset property. Since SQL databases possess these asset properties, we primarily rely on SQL, particularly Postgres, due to its superior indexing and performance advantages given our scale.

Compared to MySQL, Postgres has some functions called JSONB aggregators or other aggregators, which are quite useful. Indexing is better in Postgre due to the algorithm it uses, such as B-tree indexing. 

Moreover, Postgres has a specific data type called JSONB, which stores JSON in binary format, resulting in optimized performance.

We use the solution to store tables. It is stable and performs well.

Stability could be improved.

I use PostgreSQL on-premises to store monitoring data collected by  Zabbix Server.

I wanted a database engine that could handle an ingress of a thousand real-time values per second, delete old items without affecting performance, and handle hundreds of user queries at all times.

The solution had to support high compression and time series data while maintaining data integrity and performance.

I wanted the database engine to be easy to tune, secure, and set up.

PostgreSQL matched those requirements and has regular updates and plenty of official and community support resources.

PostgreSQL greatly improved our monitoring solutions data storage, performance, compression, and processing. Our monitoring solutions run efficiently with little maintenance.

The availability, stability, and reliability of our monitoring solutions greatly improved because the database engine scales out well, is easy to tune, easy to upgrade and manage, and supports extensions and plugins for specific use cases. One such plugin is TimescaleDB and it has proved greatly beneficial for time-series data storage and automatic partitioning of the database.The upgrade of the database has been great too, from 12 to 13 to version 14.

We use it for inventory control.

We are able to use it on many servers and incur no cost impact, whereas Oracle charges you by the number of cores that are on each individual server, whether you use those cores or not.