What is your primary use case for PostgreSQL?

It is a backend database for security. We dump the data, collect the database, and then analyze it using some BI tools.

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.

Use cases include querying data warehouses and databases to fetch data for clients already working on PostgreSQL. We also use Postgres for building reports.

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 use the product to manage large datasets. We also use it for forecasting. The product is integrated into our application to test the data.

We use PostgreSQL in our company for test systems.

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.

We have a use case for the solution which was related to a website that we developed for a Spanish energy line transmission company. The company used to face a lot of legal issues in Brazil. We had created a SaaS product that helped them to monitor the Brazilian legal parameters. The company had used the product only for two years and then discontinued it. The company also faced many internal problems where they had to urge the lawyers to get used to the SaaS products. The lawyers wanted to input information into another system and this is where we used PostgreSQL.

We use PostgreSQL as a database, e.g. it's where we install the application. We also use it for all types of batch processing, and it also has the batch sequencing engine. We use it for everything, e.g. everything's right there in the database.

I am using PostgreSQL to develop a general ledger system. The solution is on-premise right now, but it's going to be on the cloud soon.

We use it for inventory control.

Our primary use case for PostgreSQL is data storage.

We deployed the Postgre database on CentOS, which is a version of Linux. We have experimented with our replication and other operations. It works perfectly well. We are using the open-source version and do not plan on using any enterprise database.

We deploy our databases in either a local cloud or AWS. For the locally deployed database, we have our own private cloud consisting of a couple of different data centers that we partner with. For everything else, we use Oracle or Microsoft SQL. On the Microsoft SQL side, that's not usually software as a service. It's generally done as a local installation on a virtual machine. If we're doing a deployment on an AWS environment, we use the AWS Postgres database. It's slightly different than doing the installation yourself. So if you're doing the PostgreSQL installation on a Linux environment, that's usually when we're using that directly from postgresql.org.

We are using PostgreSQL for databases.

We use PostgreSQL as a database for our ERP system.

We use it as a backend for some vendor-supplied tools and products. We also do a certain amount of software development, and we use it as the database platform behind our own software. We have a number of deployments, and the version number very much depends on the vendor software requirements. We have on-premises and cloud deployments.

We use the solution for media purposes. We manage the sites of one of the largest sports business papers and multiple TV channels. So, we develop the websites.

We use it for processing files mostly. It integrates basically with the SQL Server. On the server-side it uses the SQL Server, then from the files that are generated from SQL Server we do have an application running using Microsoft, and we attach it to a Postgres server. We do is for the backups there from time to time.

We use the solution for database management and storage.

We use the solution to conduct surveys and consider this approach to be one which is cheaper for us.

The solution is primarily used to develop the databases for your application. I used it personally for a college assignment.

I am using the solution for data analytics, mainly for ERP because we use Hadoop and Hadoop is a dependency of PostgreSQL through the platform.

I have used it in the past for some web applications and back-end databases. In my current organization, we are using Microsoft SQL Server.

We design it and put it as part of our system and sell the system to various airports. We've designed our own schemas, and we track events that are meaningful to airports so that they can create their reports, view statistics, and make meaningful decisions that make sense for them.

I use PostgreSQL on-premises to store monitoring data collected by the 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 requests 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 has regular updates and plenty of official and community resources.

I have implemented costing models. I use it to capture item costs and then do calculations to compare costs.

We use it as an intermediary database for the collection of a variety of data points out of our data systems. There are many departments that have different data, single points of truth. We asked them to give us different datasets, and we accumulated them in our Postgres-stored database. It's an intermediary for a machine learning model.

The database is used for our customers' products. We also offer some products on our POC system, and our customer's POC systems post some data stored on PostgreSQL on the cloud. Our company's data doesn't store at PostgreSQL. We still have our system MS SQL and Oracle.

The database for the accounting systems is our primary use case for this solution. Business software is 80% of my use case in the accounting software. It's a good tool for planning. I work with financial data and the data mining aspect is very important, as I need to access the data easily. The data is the most important thing. Sometimes the software developers forget this part because they just want to save the data on the database, but they don't know how to manipulate the data. The performance of the solution is dependant on how easily and quickly you can obtain access to the data.

Currently, I'm doing a lot of source applications with Ruby on Rails, React, and mobile applications. PostgreSQL is my preferred database over MySQL. It's open-source and licenses are free, so it is excellent. The SQL queries are almost the same as MySQL.

We primarily use the solution for management. We have a managed ERP solution, however, it's all in-house.

One use case is that we installed it and built it for a customer so that he has access to the database, and he can create whatever he would like to create on it. We have deployed it on-premises and in the cloud.

I am using it to gain knowledge of the product, as I am an implementation engineer. Some clients are public organizations, migrating from Oracle to PostgreSQL.