We've been able to cut costs on databases over our previous solution with Microsoft SQL Server and migrate many applications into Amazon web services. Performance has been decent. 

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.

One of the key ways that Postgres has improved the functioning of our organization is by freeing up financial resources that can then be applied to upgrading existing infrastructure. A side benefit, of course, is that by bringing in another platform, we have given current staff the ability to grow their skill set and experiment with a new, feature-rich environment. This improves employee satisfaction and makes our CFO happy at the same time.

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.

I have never been in an environment where PostgreSQL was not used. It was always used alongside other RDBMS solutions, depending on the specific requirements of each project. In this way, we were always sure that we would get the best out of it.

The company I work for creates economic time series and forecasting’s based on monthly surveys with companies. Besides a set of general questions, different sectors of economic activity include questions specific to their sector. This means that we have different sets of answers depending on the survey. Instead of having a separate table for each set of answers, it would be nice to have a single survey data table including all answers from all surveys. The Oracle implementation that was implemented around 13 years ago stored the numerically encoded answers in a string. Along with that there were tables associated for each question in the string field name, the starting position, and the width of the answer code within the string. This system is very prone to errors and, more problematic; it is not flexible enough to respond to new requirements in a timely manner if our researcher wished to add questions in single months that are relevant for that specific period in the economic history of the country. All this was only possible at the cost of long implementation and testing times and eventually was never really done. With PostgreSQL we moved what used to be a string with fixed positions into an HSTORE (a key/value store) field. We have now named answers (the key) and their values. The HSTORE field is flexible, i.e. adding a single question in a single month simply means that only for that month there is a key pointing to the single question's answer.

Full ACID compliance for all transactions (including those with DDL changes) is supremely helpful when making modifications to the schema. The query planner and indexing functionality is second to none, making it one of the fastest database platforms available.

PostgreSQL has been a key component of our business, it is a rock solid product with years of expertise behind it, it is more cost-effective than Oracle and allows us to focus on innovation rather than licensing costs.

This is an open-source product with advanced features that support OLTP/OLAP applications with the following benefits that helps organizations grow:

• No recurring licensing cost
• Huge cost savings forever
• No vendor lock in
• One-time migration cost
• Yearly major releases
• Increase in profit margins
• Completely open source
• Community-based FREE support available
• Commercial support option

It drives our enterprise architecture we are building.

I have a quick example about how it reduced the amount of backend code and also improved the application's performance. When you are in a scenario where your application has an input, and based on that, you have to do several back and forth exchanges with the database to get more information or do data changes, you can do that transactionally by using a stored procedure.

Some may say that this puts logic in the database, and yes it does, but it's the most efficient way to get the right output. By exploiting the PL/PgSQL capabilities it can be done and maintained more efficiently than usual backend code.

Another reason for improvement is that PL/PgSQL is a type safe language and this reduces considerably the amount of errors and even the functional flow of the application. Stored procedures are transactional, so either everything goes well, or an error happens.

We use PostgreSQL as the basic tool for offering our data warehouse and BI solutions. This way my customers have a free tool and I can offer a lower price for our services.

The Full Text Search functionality saved us a lot of time because we didn’t need to program that ourselves.

There are a few little odds and ends like all SQL servers that differ from other SQL servers. The way it handles logical, the fact it does not support primary keys on views etc. My experience is all SQL servers have little differences from each other. PostgreSQL is far more robust and built for production use than MySQL which I have also used.

I have worked at the Ministry of Economy in the IT area, for more than 20 years ago. Since then, the main developments have always used PostgreSQL for their robustness, reliability, stability, and conformity with the standard SQL.

Before using PostgreSQL, we had a database issue that we were trying to solve with Oracle. However, Oracle is quite expensive and I heard from a colleague that Oracle increases their charges year on year.

Helped solve my problem to extract large amount of data in a specific order on a Greenplum application.

We have migrated some databases from Oracle to PostgreSQL lowering licensing fees and reducing the vendor lock-in, gaining sovereignty.

By using PostgreSQL, it was easy to get all the developers configured and running. With using it as our back-end for data storage, our company isn’t worried about data loss or data integrity, especially with snapshots and WAL. Our company is also able to run reports and do analytics off data in custom tables.

As we’ve used this since our founding, I cannot speak to how it has improved any function.

Postgres is for our systems a very solid database, easy to use in development and easy also to manage in production environment, and that's valuable because in the end it cuts a lot of costs (also during the upgrading processes).

PostgreSQL is the most flexible database I have worked in my career. For example, when I need geographical data processing for my application, I can use PostGIS. It is the best GIS solution out in the market, by installing extension the extension onto the database. Additionally, PostgreSQL's full text search functionality helped a quite a number of times to avoid introducing another system for text search and use PostgreSQL.

I worked as a consultant/trainer. I have a few installations of Dev/Test in my VMs, and I don't have anything in the production installation in our organization.

The database is used to set-up customers projects and is our standard database which we use.

Back in the day, MySQL had storage problems with InnoDB (everything in a single file), and we wanted ACID compliance. So we decided to use PostgreSQL for that, and it helped us achieve that goal. PostgreSQL's feature set was excellent for our needs, and we didn't want an expensive (meaning hardware utilization) RDBMS. Fit like a glove.

We used MySQL for many tasks, because there were simply more documentation available, but while using it, we found many serious weaknesses with it like no data validation even for string length, no transactions, etc. PostgreSQL catches a lot of things that MySQL didn't because it is serious about the data it protects!

I am more of a fan of doing things straight out of Python, but with the size of the data sets, we were forced to do it in SQL.

All of our BI needs are implemented using PostgreSQL functions. Our tools are designed in such a way that the BI is implemented as much as possible through our database. We need a lot of flexibility to extend the BI logic on a specific installation.

I'm a data consultant that specializes in PostgreSQL. The combination of it's open community, open source approach and it's unique features make it the perfect platform for solving today's sophisticated data challenges.

PostgreSQL allows us to have a single database engine used for OLTP and OLAP workloads, for relational and non-relational data. Its robust and battlefield-proven replication makes us sleep better.

It provides standardization on the database and related skills.

I'm working as architect for a custom software development company and we are using Microsoft SQL Server, Oracle DB and PostgreSQL as our main databases, in recent years Postgre is offering more and more useful features which we can use. For its open source model and very good documentation is very easy to optimize queries within bigger databases (100GB). Also its free and its lowering price of our solution so we can (and we are) address smaller customer.

Due to budget restraints procuring software is always an issue, and mainly production systems are well maintained. However development systems are not usually so well off. As PostgreSQL is free, this enables us to develop applications without having to think about budgets, and give us greater flexibility. There is still reluctance by business to accept free ‘Open Source’ software, but proof of concept development can be achieved at no to low cost.

We used it from scratch of the organization. It helped a lot since we could improve our hardware, and we upgraded the Heroku plan as we grew.

We used this product for applications which require a database. Since MS SQL Express has limitations and regular MS SQL requires pricey licensing, PostgreSQL was an easy choice. The deployment is quick and easy and works with very little configuration, if any at all.

Most of the enterprise I have worked has been startups and small to medium software industry and data analysis. One of the most improvement it is not in the mean time but in the middle to long time. At first sight it seems to an overkill implement a product as PostgreSql for small projects; even managers and investors tend to put some resistance to it. Then, as soon as projects start scaling and data set increase in size, concurrency, consistency and data types, is were you think PostgreSQL was one of your "hit" on the project design, time give you lot of credits.

Our organization has MySQL, Oracle, PostgreSQL and flat files in our processes, and the use of extensions has facilitated the integration between these processes. Also, it's only 7-8/10 when comparing it to an Oracle database.

JSONB (Binary JSON storage), because I can have both relational and non-relation data storage at the same time with this data type. In addition, by using Generalized Inverted Indexes (GIN) it supports fast lookups and simple expression search queries.

PostgreSQL is a powerful dateserver although not like Oracle. So we can make many developments in a cheaper way with high availability. Besides, its very useful tool for debugging with a soft learning curve.

We were able to use the latest features described above to facilitate the integration of disperate data sources into our Postgres Data Warehouse.

It's saved us money as it's free.

It improves the query performance a lot and helped in some real time and analytic reporting

PostgreSQL is a powerful and open source database, which is central all data processing.

• Cost savings
• Easy spin off for new environments

It helped me to find an easy and inexpensive solution for databases

PostgreSQL (geo)spatial support is stable, and you can add, remove, and edit all standardized GIS features. Thanks to projects such as EDB, Bitnami etc., PostgreSQL can be used by people on pure user level, without deep knowledge of OS administration, programming.

We are spending less time parsing API response and more time exploring data. We spend time understanding APIs and how to interact with them, If we can load responses directly to the database that saves many man hours for a project.

It has helped to cut costs because it's open source.

The ease of use has been a great benefit for us in the organization.

We use it as main database for our SaaS product.

It is a world class, performer, a scalable database that is free and open source.

I use it for personal projects. It's been really easy to learn and it's been useful since ramping up it use.

I can say that PostgreSQL increased the database possibilities within the company.

I can integrate solutions quicker than with other RDBMS'. At the same time, I am able to keep an RDBMS' integrity, robustness, and High Availability which is the most important thing for all my production environments.

The documentation is very well written and detailed, it helps to implement the right features for your needs in a timely manner.

We use it daily.

All our data is stored in PostgreSQL, and we use a BI solution on top to gather all the important metrics to our business, so the whole company has a clear picture of what is going on.

I have developed many portals and internet commercial sites with this RDBMS. It's easy and quick to publish portals and websites when you have this in production.

It's improved security by allowing us to switch from an unsecure file-based database to a secure SQL database without license payments. Also, it provides us with multiple disaster recovery options with streaming replication.

It has allowed us to run a Scada database, which reads data every 2 minutes. It does it in a very smooth way.

By implementing PostgreSQL, organizational databases get stabilized, no locking issues occur and report extraction is faster.

It requires enterprise integration improvements from the security, and audit perspective (AD integration etc.). Also, integration into existing BI tools is not present.

It provides access to data for analytics. It has a lot of free tools available for data access, and has easy integration with a lot of visualization tools such as QlikView and Tableau.

The strength of this product is set in the timeliness of SELECT queries with lots of joins. compared with other DBMS, it is really optimized for joins.

We are considering migrating to this platform due to its robust backup and recovery solution, among many other features.

Rather than using Desktop GIS software we were able to carry out a lot of our spatial operations faster with larger datasets by moving the operations into PostgreSQL. We also save a ton of money on Oracle licenses. Finally, rather than having to give up my relational features, I can use the JSON data type and get everything I want.

We're in the evaluation period at my current company, so we haven't really seen improvement to our functioning.

It allows us to deploy test functionality on a very simple normal computer and not on a server.