PostgreSQL Reviews

By far indexes is the most useful and robust feature. Also, the query optimization engine is simply great. It is very complete, clear and useful documentation, forums and diverse information channels.

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.

I think that data types that decrease the breach against NoSql Databases will be the next steps. I am not talking about changing to a pure NoSql DB but to some features that will face the big change in data analysis and maintenance that that DB are facing nowadays. Also tools for distributed replication and clusters should be more researched and improved; anyway nowadays there is some of them.

I have been using PostgreSql since University where I teached students some DB theory concepts. The course was focused on indexing and benchmarking. Also I use it on software industry, as a DB manager, designer and operator; common tools were PL/pgSQl, indexing and tuning; using about 3.0M per month DB tuples inserted and about 500tps on peak points. Finally I use it on personal projects, for small data sets (~1.000).

We have had no issues with the deployment.

I have faced just a few issues working with PostgreSql, one of them was specifically on Hash Index (see as example http://www.postgresql.org/docs/9.2/static/sql-createindex.html.

We have had no issues scaling it for our needs.

Most of the great value of PostgreSQL is the variety of technical support you can find Consulting, lots of forums, and big communities who have been using and documenting PostgreSQL for a long time. I have never faced a problem or question that couldn't be solved using these channels.

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.

I have faced a few issues while installing it and configuring it; most of them related to incompatibility while using old Ubuntu Linux versions.

I have always implemented it in-house, and as all solutions for everything on vast areas, is highly recommended read guides on how to install it.

ROI is by far fair enough for startups and enterprise projects that are expecting a big grow in the mean time.

PostgreSQL license is a fair enough for small to medium size business solutions.

Just read the comparisons between different database engines, and read some documentation so you can exploit most of the powerful tools and functions it has.

The use of extensions for integration with different databases is valuable.

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.

The use of XQuery besides XPath into PostgreSQL. It would also be nice for them to add some backup features similar to the one that Oracle Recovery Manager has. Also, a tool to query archive files would be a nice addition, and being able to change the execution plan through hints like we do in Oracle. There are some more but these would be my favorite ones.

I've got six years experience with PostgreSQL, and 18 with Oracle.

No issues encountered.

No issues encountered.

No issues encountered.

I'd rate it as 10/10 as an open source product with an active community.

I'd say it's good.

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.

It is simple, especially when you know the main components of a database.

We implemented it in-house.

We didn't have any setup costs because it is free.

• MySQL
• SQL Server
• Sedna XML

I'd say go for it. It is stable, and easy to use but you should get an understanding of it to implement backup strategy.

This is an open-source solution, operates at a high speed, and supports more than one SQL language.

It integrates with different platforms, the upgrades are quite fast and the solution keeps getting better. 

This solution could be better integrated with other systems. 

I have used this solution for four years. 

This is a stable solution. 

This is a scalable solution.

We have not needed much help from the customer service team. When we have had questions, we have found the answers on Google. 

We previously used Microsoft SQL.

The initial setup is straightforward and took less than one day. 

This is an open-source solution and there is no need to pay for a license.

We recommend PostgreSQL for our customers who want an open-source solution.

I would rate this solution an eight out of ten. 

We use the solution for database management and storage.

The most valuable feature is the performance.

The solution could improve the integration.

I have been using this solution for approximately four years.

I have found the solution to be stable.

PostgreSQL is a scalable solution. However, it could be better.

I have not needed to use the support.

The installation is not simple, it is more difficult than DeviceSQL. We had a few issues during the installation.

I did the implementation of this solution myself and it was more complex than MySQL.

I have evaluated MySQL and DeviceSQL.

I would recommend this solution to others.

I rate PostgreSQL an eight out of ten.

In my experience, the most valuable features of PostgreSQL are streaming replication, rich indexes support, extensibility and NoSQL features such as hstore and JSONB. This features are very mature and stable, we use them in many projects, they're predictable, always work as expected and without problems.

In future releases I would like to see built-in realization of multi-master cluster with sharding, effective partitioning, incremental backup, optimizations for SSD, connection pool facilities, and built-in replication for tables and databases.

I've used this solution for five years.

There are no issues with deployment. Postgres has a very verbose and clear documentation and install instructions.

From a scalability point of view, there are no difficulties. It works out-of-box without any third party tools, but streaming replication allows you to scale read-only workloads. For write scalability, Postgres-XC or Postgres-XL should be used.

I don't use any services and technical support, and th community's support is very helpful, friendly and the members have rich experience with PostgreSQL.

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

The initial setup is simple and doesn't take a long time, but in serious projects, PostgreSQL requires additional configuration optimizations as do the other RDBMS.

We did it all in-house. You should read all the official documentation as all the answers are there.

PostgreSQL is an amazing product, very stable, predictable and reliable with rich set of features.

Common Table Expressions(CTEs). It's powerfull, easy to write and read and very flexible.

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.

Replication is not yet as well implemented as in MySQL.

I've been using it for one year and five months

There are some issues around different OS, but not a big problem.

There are some issues around different OS, but not a big problem.

There are some issues around different OS, but not a big problem.

The documentation could be written better, but there is a huge community committed to help.

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

Straightforward, easy and intuitive.

In a vendor team, we develop products for different segments stores. In the implementation, keep in mind the configurations and platforms that are available, it certainly will save time and avoid potential problems.

Currently this is one of the best solutions on the market. It is a tool without cost, powerful, easy to learn and with a large active community.

It is an open source solution and that is a database engine very powerful. Besides it is highly configurable. I prefer PostgreSQL over MySQL or MariaDB because you can create several databases with many schemas and create roles like owners, and not only grants over tables, or procedures. On the other hand its very easy and intuitive to administrate the connections by hosts, databases, and roles.

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.

It needs to be able to cluster. We have implemented the high availability with a master-slave mode and one host in only read mode. This is the worst feature of this product and the quality sign of Oracle.

I have been using PostgreSQL server for three years.

The upgrade from v8.4 to v9.3 was a little hard, but this was executed finally well.

We had no issues with the stability.

We've had no issues with scaling it for our needs.

I've not had to contact them.

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,

In my opinion the initial setup is easier than MySQL because it is more intuitive, but you must to edit a couple of config files, and become more aware of the entire infrastructure.

It's open source code, so you get it for free and need to contribute to debugging errors and improving the code.

Be patient! Like most open source tools, this requires commitment and a little knowledge.

* pg_hba.conf

* A fragment from postgresql.conf

* How to access to database-server using psql client, and create a database

Create a user/role and be owner for a database. We can list all databases with "\l".

Overall it is an excellent RDBMS and it is easy to use and administer. In PostgreSQL 9.5 the table inherent Foreign Data Wrappers(FDW) is available. This extension is available for most databases which makes building server federation very possible.

In 9.5 support for FDW was improved which means it is now possible to import a complete foreign schema. Foreign Table inheritance is now supported as well. They have also improved the Foreign Query optimization since v9.4. Lastly, It has low maintenance requirements so not much has to be done as far as DBA tasks go.

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

• Improved support for parallel query execution
• Merge Joins
• Improved Handling of Materialized Views

I've been using it for years.

We have had no issues with the deployment.

There have been no performance issues. It's a very stable environment.

It's been able to scale for our needs and easy to extend when needed.

Although there is no tech support, it has a large user community who are always helping each other.

The last few versions work great out of the box without much config changes. Don't be afraid to try it.