We also have used MySQL.

I was previously using Microsoft SQL Server and MySQL.

With MySQL, I had once a terrible problem with a group that was only giving me the first record of a group. I had to implement it through other means for the solution to give me the result that I was required.

I have used MySQL.

I am also using Oracle.

We have been working with Microsoft SQL.

The main difference between SQL and Postgre is that Postgre is open source. It's completely free.

Initially applications at my current employer used Microsoft SQL Server. The cost for licensing/maintaining windows systems was more than we liked. PostgreSQL has offered similar performance for our workloads with lower cost. 

We used Oracle. We're currently in the process of migrating from Oracle to Postgres, and we're doing it because of cost.

Postgres is a superior product, and it is free. Oracle's support is really terrible, so you're not really getting any support from Oracle.

See my answer above. We evaluated both open-source as well as proprietary solutions. Of the open-source solutions we examined, Postgres has the best track record for innovation and enhancements. While the user base is smaller than some of the more established solutions, the fact that it has been able to avoid being “acquired” by a major player is, in my opinion, a plus.

We used to provide service to various clients, and we were also providing internal services. We used different solutions in parallel, such as Amazon Redshift, MySQL. MySQL is also free. I have also used Oracle and IBM Db2 in other organizations.

I used other database management systems (MySQL and its variant MariaDB) for my NMS applications before moving to PostgreSQL. I had some optimization issues on MySQL and MariaDB and decided to switch to PostgreSQL, mainly for the TimescaleDB extension support provided on PostgreSQL and which my application natively support including automatic database partitioning and compression. TimescaleDB proved to be helpful since I mostly deal with time series data and the TimescaleDB hypertables improved my applications perfomance greatly.

We've used a few other products previously. We're also using MongoDB, or at least, we will be, in an application that we've just started.

I am also using Oracle Database. The main difference is the scalability. PostgreSQL could be used for small to medium databases but not for a huge production database. I still prefer to have Oracle Database.

I don't recall us using a different product.

We did not previously use other products. 

I've also used Oracle and Microsoft SQL. This product is free and more robust than Oracle, however, Microsoft SQL might be easier to use.

I have used MariaDB and Oracle MySQL.

We were using Sybase. We've actually transitioned most of it over to PostgreSQL.

We used Oracle before switching to PostgreSQL.

We used Sentinel which was awesome but it did not provide metric views.

I've also used MySQL and MongoDB, but neither of those technologies provide any competitive advantage over PostgreSQL in any respect that comes to mind.

We also use Oracle Database. I would say the two are quite comparable.

I've also worked with Microsoft SQL, and I find the product to be much more stable.

I started with this product.

I've used a larger set of databases (including the most well-known and a few more exotic) and setups. Definitively PostgreSQL is a serious contender at the top of the list. I chose it because it's fast, reliable, rich in functionality, and it has no commercial costs for its acquisition.

I was previously working in a research organization, which favored open source. I have also used Oracle, Sybase, Microsoft SQL Server, and Ingres databases.

We had some problems with bigger customers using MySQL so we moved to PostgreSQL.

We used Oracle, MySQL, Microsoft SQL Server. Oracle and Microsoft SQL Server were simply too expensive for smaller customers. MySQL had too many short comings to make it a workable solution.

I have used other solutions for over 20 years and the problem of licensing has been our biggest drawback because of the costs and dependence we require from the provider.

I have more than 10 years of DBA experience, working with Oracle, DB2 and MySQL too. All of them have pluses and minuses, and I usually need to explain that nobody can claim "X is better to Y", at least with the universe limited to world-class RDBMS like PostgreSQL, Oracle, DB2 and MySQL. Of course, certain scenarios can mean that one RDBMS is better positioned than another to handle.

We had used Microsoft SQL Server in our previous company. But, the licensing terms kept getting more and more onerous. We started looking at PostgreSQL from the reviews and recommendations, especially since it was open source and Amazon RDS started supporting it.

I have used MySQL, another open source product now controlled by Oracle. It’s reasonably fast and OK for simple databases, but it lacks transactional isolation and its replication setup does not enforce a true master/slave configuration.

I used MySQL and Oracle previously, PostgreSQL is open source and fully ACID and SQL standard

I used to be an Oracle DBA over decade ago. I have used over dozen of database solutions ranging from MySQL to MongoDB in the distributed production environments but Postgres provides superior features but not limited to; extendibility, performance, scalability, analytics queries.

We have been using Oracle software, and in some cases MS SQL server. The price difference between the used products and PostgreSQL was one of the issues. The second was the ease of installation and the availability on different platforms.

Up to that point, we used MySQL. The decision to change came with a new version being written from scratch, and PostgreSQL being better suited for our needs.

We previously used MySQL. PostgreSQL tries to solve things in the correct way for all platforms, all file systems, and all users. In the end, this means you get a better working and more stable system. They try to stay away from hacks and other non-portable or limited solutions and prefer to work inside the system. For example, an operating system already does many optimizations so why would one want to reinvent things with raw file systems, etc. like Oracle tried to do in the past?

It is a bit different from Oracle, with respect to security.

We are using PostgreSQL for new installations and new versions of our solutions where it's possible, and the customer does not require a specific SQL server. Nowadays it's covering all of our needs.

We use both MySQL & PostgreSQL, some applications have better compatibility or built in tools, this decides which database we use.

I used other solutions in other companies I've worked for before. When I arrived at my current company they were already using PostgreSQL.

We use Microsoft SQL (all versions), MySQL, PostgreSQL, SQLite, etc. We use PostgreSQL when the application supports it and where it makes more economic sense to use it.

I have worked with MySQL and Oracle solutions. Against MySQL, performance is the big difference. PostgreSQL is far more robust and mature than MySQL, especially when you think about keys and indexes. Against other databases, such as Oracle, the easy installation steps of PostgreSQL is the best difference for me.

We initially only used an Oracle database, but we decided to add PostgreSQL as an option because of its similarity to Oracle. Also, it's free and is the best open source database.

We previously used Microsoft SQL.

I don't use any similar solutions such as Microsoft SQL, Oracle, or MySQL.

I used MySQL, but for safety and consistency issues, I moved to PostgreSQL

I use MySQL, MariaDB, and Oracle. I chose PostgreSQL or others depending of the project. For Java implementations I prefer PostgreSQL, and for PHP development, I prefer MySQL or MariaDB,

No other solution was used.

We were using version 8 before, and also an earlier Oracle instance. We chose the product because it is powerful, well documented, and open source.

I have previously used MySQL and am currently using it for other projects. MySQL is a little easier to use.

We haven't used any other open-source service, but we have engaged Enterprise DB for enhancing our monitoring but there was no need to do so.

Since Oracle was expensive for a company business an inexpensive way was to focus on PostgreSQL.

I have worked with MySQL, Microsoft SQL, db2, and Oracle. We chose PostgreSQL for its JSON support as our APIs are sending JSON responses and PostgreSQL is like home for JSON. Choosing it has helped our cloud computing requirements a lot.

The company used a Microsoft SQL Server previously. I don't know what the reasons were for changing, however, due to the fact that, when I arrived at the business, they already had Postgre.

We had several performance issues with MySQL.

We've got experience with a number of RDBMS, but PostgreSQL has always stuck out to be the most economical and sensible product. That being said, we do have instances of Maria, and various NoSQL's floating around.

In my last company, we had been using Access. We changed to PostgreSQL as we needed something more robust and usable. This was provided by PostgreSQL which at the time was the perfect solution for what we needed.

I used MySQL. PostgreSQL syntax is much clearer and consistent, and its stored procedures are powerful and fast. The documentation is also much better and of more help.

I used MySQL, but I needed support for full text search. PostgreSQL adds this, and also many more advanced SQL functions.

MySQL but not in the same scale.

We tried RethinkDB a couple of years back, and it was unstable at that time. Also, MySQL didn't have a JSON type back then. We switched to PostgreSQL and never looked back.

I used MySQL. I switched because at that time, because some things were complicated with MySQL. For example: scaling, sparse data JSON, and other issues.

Both projects have the same query syntax, and the transition for me was almost painless.

We switched due to a common OS integration strategy.

We switch to this solution due to its stability and that it is open source.

Yes, we evaluated other solutions, and we are moving away from PostgreSQL after the evaluation period.

I switched as I needed to increase the volume of data.