We use PostgreSQL alongside Microsoft and Oracle solutions. Postgre is suitable for scaling with specific projects. But while it scales very well, Postgre doesn't have the same recovery features as some larger-scale databases. For example, you can run Oracle Databases in a couple of different ways for easy recoverability should the primary database fail. First, you've got a rack for redundancy and load distribution. Second, Oracle has a feature called Data Guard that replicates the database in case it goes down. Data Guard allows you to run a completely different copy of the database that will take our main exports and keep it up to date. So if your primary database has a software or hardware failure, you can bring up the secondary database and re-task your applications to use that database. It's not as simple to do this with Postgres. 

We are utilizing the database's active native security features. As a result, we currently have no need for any external security tools. We had, but we worked around it.

We evaluated EnterpriseDB (EDB) Postgres, which is a paid product, whereas Postgres is open source. We decided that it was better to go with a free product.

I evaluated other options including MySQL and its variant MariaDB & Percona Server for MySQL, Oracle DB, and SQLite.

We're currently looking for a more modern solution to replace Postgre. I'm aware of AWS Redshift, Query, and Nextly. These are major players in the market.

I have tried and worked on other solutions such as Oracle and MySQL. I would say that the combination of PostgreSQL's features, plus the reliability and performance it offers in combination with the fact that you don't pay for a license was the reason I chose it.

We evaluated Oracle, MongoDB and CouchBase. Although those seem to be different products, they have some common features that worked for us, we decided to go with PostgreSQL because of its reliability and proven track record.

When it comes to pros, I would put MySQL and PostgreSQL in the same class. let's say I'm trying to write to the database and then the power went off. It will still keep the data integral. I don't have duplicated data, and data integrity is intact. With NoSQL databases I have to duplicate queries in case something like this happens I don't know whether my data is going to be integral in cases like a failure situation. PostgreSQL has the rollback function which remains integral. I cannot build a search engine using PostgreSQL, because that would be a very expensive hit on resources. Alternatively, with the ElasticSearch utility, and the use of load balancing, it is very easy to use. Elasticsearch returns substantial results and works in the background. I cannot do that with MySQL or PostgreSQL databases as that's actually a very expensive use of resources.

PostgreSQL is written in ANCI C, fulfilling all of the ACID properties other proprietary databases support. Most of the customers who use proprietary database solutions to their business applications prefer to move away from proprietary licensed databases to open-source databases to save huge amounts of recurring licensing costs resulting in huge profit margins. Customer choose PostgreSQL for its rich feature list, open source, no recurring software licensing costs, no vendor lock-in and various choices for the best commercial support and community-based support available.

I have evaluated SQL Server.

For our current use case, I'm evaluating PostgreSQL versus MariaDB. I am probably going to use MariaDB because I need the temporal SQL feature, which is not available in PostgreSQL.

We compared it to MySQL, Oracle and we though PostgreSQL Full Text Search functionality was the best for what we needed.

We got carried away by the experience of a team member with experience in PostgreSQL and first we used the tool in applications of low concurrency of users but with storage of files pdf, doc and xls in the tables. We were surprised by the results. This is how we trust in PostgreSQL and we demand more and more. We always get good results. Sometimes we have had to migrate to a new version of PostgreSQL, but have done so without any problem(s).

I have evaluated MySQL and Ingres previously and then PostgreSQL. My personal choice is PostgreSQL. I also worked on a migration project from Ingres to Oracle.

I've used Oracle, DB2, Sybase and MSSQL. The only one that comes close to PostgreSQL is Oracle, and only because of the large set of developer tools it offers. But, it's very difficult to manage and extremely expensive.

I work with few other RDBMSs, but nothing compares to PostgreSQL when it comes to ACID and SQL compliance, stability and the ease of administration.

• MySQL
• SQL Server
• Sedna XML

I have evaluated MySQL and DeviceSQL.

We tested a big portion of our online API product using SoapUI and it was very fast and efficient.

We also looked at MySQL and other databases including open source, standards, compliance, and enterprise features.

Yes, MySQL.

I've only used online open source resources and would say there's not as much as there is for MySQL. Sometimes it took me some time to find a good solution to the more unusual scenarios

• MySQL
• Microsoft SQL Server

I've worked with MySQL, Firebird, etc. and, in my opinion, PostgreSQL is more scalable.

I explored many different databases: Redis, MongoDB, MySQL, Elasticsearch, and others.

I use some of them in conjunction with PostgreSQL. However, if we are talking about relational databases, then I only use MySQL.

We had an RFP process to evaluate between similar product categories.

For me all SQL tools/products are similar, except for a few important differences like GIS functions in PostgreSQL, and programming abilities in Oracle PL/SQL, etc.

Yes, we reviewed MongoDB, MariaDB, and MySQL.