PostgreSQL Reviews

This database is highly reliable and offers excellent disaster recovery. In short, I can depend on it to be available and operational.

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

The development team has been teasing me with talk of multi-master capability for some time. Their latest release, 9.5.3, does offer some asynchronous capability, but I really want synchronous multi-mastering as that would allow horizontal scaling with much more capability.

Current bidirectional support is limited to the functions provided by a third party integrator. The extension does not offer real-time update guarantees nor does it support DDL updates (schema changes). This is quite unlike the current unidirectional replication scheme, where DDL updates are processed, and there is a way to guarantee real-time updates so the slave server can function as a hot standby. With BDR (bidirectional replication) this is not possible. I understand that in all respects, true bidirectional replication is the holy grail of databases as would give any server in a cluster the ability to take over as a single master without any transaction loss.

I've used this solution for more than 10 years.

There were no issues with the deployment.

I have in the past before the code base had stabilized. Certain procedures just didn’t operate reliably and some internal parameters were just too small and caused problems with large data tables.

It's been able to scale for our needs.

Well, it’s open source so mileage varies, but generally I haven’t had problems. Of course being open source, I can and have looked through the database source code and found the answers to problems I was experiencing.

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.

It is rather complex to set up correctly. The configuration file is over 400 lines in length and many parameters have only vaguely defined suggestions. Changing a single parameter can have unintended consequences.

Strictly in-house, and I would say anyone attempting implementation should hire the expertise to get the system correct.

Obviously pricing and licensing is non-existent, but the costs need to include the expense of in-house expertise, either employees or consultants.

PostgreSQL is an enterprise capable database very similar to many commercial offerings, but be prepared to either pay for consulting or a long period or experimentation to get the configuration proper.

• Stability
• Standard SQL for ease of development with pre-existing knowledge

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).

The Postgres team is already doing an amazing job in putting in features to ease the life of developers and sys admins, such as JSON support and database replication.

A feature that is still a work in progress and it would be nice to have would be native master-master replication, we don't have a need for it right now but it's something that should be addressed in the future.

I've used it for five years.

There have been no issues with the deployment.

We have had no stability issues.

It has been able to scale it for our needs.

I've had no need to use any.

I've had no need to use any.

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

It was easy.

We deployed it in-house.

It's a great database engine that is easy to use, powerful, and scalable.

PostgreSQL is the only open source and multi-functional database solution out in the market today. I have used it to replace Oracle (RDBMS) up to MongoDB (Document DB). Postgres has very rich SQL and NoSQL features that gives it a special place in database industry. It’s easy configure and manage features helped to increase adoption in last decade or so.

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.

PostgreSQL has introduced number of new features to achieve out of the box multi-master replication and reach JSONB features, horizontal and vertical scalability and parallelization features. I’d like to see them to be production ready. As the number of users of application grows, the multi-master replication will helpful to replicate systems across the continents. We have started using JSONB in number of application, I would like to see some extended features to make JSONB data type more reachable. The horizontal/vertical scalability & parallelization features will help our big data analytics processes faster to improve application response time.

I've used it for approximately 10 years.

I have experience working with over dozen of database and datastores in production environments but PostgreSQL has been the most stable database I have worked so far.

It is missing some key scalability features such as sharding and automatic failover, but the Postgres developers are working on adding these features.

Postgres community is very thriving and Postgres ecosystem is very strong. The product is open source but it has the best documentation and readable code among other open source products. The turnaround time for logged bug is much faster than some of the commercial vendor’s support team. Additionally, there are a number of PostgreSQL professional support companies in the US and all over world.

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.

PostgreSQL is easy to setup compare to any other commercial RDBMS out there in market. It is easy to install and configure.

Postgres has great documentation and various open source tools available for maintenance. However, it is recommended to work with Postgres consulting services companies to expedite design and implementation.

PostgreSQL is truly open source database system so the licensing cost is zero. If you are migrating from any commercial database system, you are saving licensing and recurring support costs.

If you don’t have experience with PostgreSQL, I recommend to attend some of the local PostgreSQL user group meetups and/or conferences to learn how it is being used. If you need help discussing about the solution, you can reach to any of the Postgres consulting services company.

• Security
• HA and DR
• Performance
• Maintenance

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.

It's not very user friendly, as it is open source and has no immediate support. You can download the Enterprise version of Postgres that is a GUI installation and also have a support contract.

I've been using it for five to six years. I did the PostgreSQL DBA’s training and led the implementation and data migration projects.

We also use the EDB Postgres Plus Advance Server v9.3 (EnterpriseDB). We use it to evaluate the Database migration from Oracle to Postgres. The data level migration was successful but for objects, and at the security level, you have to fix issues manually.

We've had no issues but setting up the replication, security, and login is different from other databases.

We've had no issues with the stability.

There have been no issues with scaling it for our needs.

As mentioned earlier, there's no support contract for open source but with EDB (EnterpriseDB) you have the open to purchase the support contract. I don’t have any experience with EnterpriseDB support.

It's straightforward, as it's an open source product.

We did it in-house.

As it's open source the ROI is quick.

The core product is free but you have to pay for third-party utilities / plugins and support.

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.

• Positive - 100% free as it's open source
• Negative - it's hard to find expertise

If you are planning to migrate an existing environment, please go through with the full UAT cycle at data, connectivity, objects and apps level.

The most valuable features are a good feature set, understandable, and good tuning features. It is, also in our experience, the best open source GIS enabled database, with good support from other open-source tools.

The product has easy installation procedures for the OSes we are working with and gives also a good possibility to tune the database for the given usage.

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

One of the features it needs is a tighter integration with business intelligence software, so that the optimisation of the requests can be handled natively in the database. These features are on the roadmap, and are already partially released in the latest version.

We have been using this database for about 18 years.

We have had no issues with the implementation. Most of the issues we have encountered in external installation where due to misconfiguration.

There have been no issues with the stability. Most of the issues we have encountered in external installation where due to misconfiguration.

We had no issues scaling it for our needs. Most of the issues we have encountered in external installation where due to misconfiguration.

We have up until now not needed additional customer or technical support, these can be purchased by supporting companies.

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.

The initial setup is easy to perform, but the tuning is a bit more complex. The installation support on Linux flavours is excellent and has native installation packages.

Implementation and installation was carried out in house.

The pricing of the database is open-source and our investment in the product is based on training.

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.

What I like most about PostgreSQL is its ease of management.

They should make PostgreSQL more secure. It's stable, but from a security point of view, it still needs improvement.

It's been a few years since I started using PostgreSQL.

PostgreSQL is a stable solution. It's also very easy to manage.

PostgreSQL is scalable.

Installing PostgreSQL was straightforward. There were just a few parameters I needed to get through, then the process became straightforward. I was able to do the installation myself.

I did the implementation of PostgreSQL myself, and did not need a vendor or technical team to help me.

PostgreSQL is for personal use, e.g. I've been using it for my applications. It's deployed on cloud.

I'm not from the core database team, so whatever features are currently provided by this solution, I'm happy with them, e.g. PostgreSQL is fulfilling my needs. Our database administrators will be able to provide more information on areas for improvement for this solution, because they know all the ins and outs of the database. I'm using this for my application, and I have not faced any issues with it.

I'm part of a global company, and in our team, we keep recommending PostgreSQL to our client, but increasing the usage of this solution depends on the client, e.g. the one who pays.

We have more than 200,000 users of PostgreSQL.

In my project, I don't need a technical team for the deployment and maintenance of this solution, e.g. I can do it myself, but for other projects, deployment and maintenance could be handled by database administrators.

On a scale from one to ten, I'll rate PostgreSQL seven out of ten.

Any relational databases that you have in Oracle, you can move to PostgreSQL. This is what we have been doing at the moment. 

I like that you can move any relational database from Oracle to PostgreSQL. I also like that it's pretty stable.

The price could be better.

I have been using PostgreSQL for a few years.

PostgreSQL is quite stable.

We used Oracle before switching to PostgreSQL.

The initial setup and installation didn't take a lot of time. It usually takes about a couple of hours.

I implemented this solution by myself.

It could be much cheaper. If you would like to build an application on Amazon today, PostgreSQL is the standard database with Redshift. If you want other databases, you can add them, but PostgreSQL is the basis of everything. It's a question of money, that's it.

I would recommend it as a choice for people that want to move from Oracle to another database, which is relatively free. 

On a scale from one to ten, I would give PostgreSQL an eight.

• Free and open-source RDBMS, with a permissive license
• ACID compliance
• Multi-version concurrency control
• Custom data types
• Array data types
• PL/Python stored procedures

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.

There's always room for improvement. Better SELECT performance is something that PostgreSQL could really benefit from. Replication should also be made easier. PostgreSQL also lacks a good tool like MySQL Workbench. PgAdmin3 works, but it's funky and crashes sometimes.

We've been using PostgreSQL in production since version 8.4, in 2010.

I have not encountered any deployment, stability or scalability issues. It's been running since version 8.4, updating one version at a time (9.0, then 9.1 until 9.4). Database is currently at 6GB, works without a hitch.

I have never used or never needed technical support. StackOverflow covered all our needs on this scenario.

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.

The initial setup was somewhat complex. We had to import the old database, which was in MySQL. Most tables were rewritten, and the team was not used to PostgreSQL at that time, so there was a small cultural impact.

Implementation was completely in-house. On our case, it was much better to train the team to use a new RDBMS than to use external consultant; after all, our team is a development team.

Since it's completely free, the ROI means only the time spent by the team to get the database up and running, and the time maintaining it. I'd say it doesn't compare with any other solution I've worked with before.

PostgreSQL has extensive and comprehensive documentation. Chances are that you'll find your answers there for 99% of the cases. For those answers you don't find, you can always go to StackOverflow. If you're not a DBA or a programmer, I'd suggest hiring external help, as with all the cases with databases (RDBMS or not).