PostgreSQL Reviews

The SQL is very close to the standard, the richness of of procedural languages and the strong attitude to the data reliability.

The product is used to ensure the data delivery and the HA features are used to enforce a non stop service.

The partitioning, is still very basic and not touched for years.

7 years

More a lack of knowledge rather an issue. PostgreSQL implements the data management in a very peculiar way. Ignoring this can result in disasters. And often this does happens. A better explanation about the architecture will reduce the risk.

Not on the production side. I’ve seen a lot of bugs or misconceptions on the HA side. Same as question 7, It’s more a lack of information than an issue.

The product scales pretty well.

Customer Service: As this is an community managed system there’s no customer service. There are companies offering support, I never used as I don’t need it.Technical Support: Quite good. The mailing list are a good way to have quick response. What really lacks is a centralized knowledge base like the Oracle’s metalink/otn. That is what I’m really missing from the oracle universe.

I worked for years on Oracle. I decided to move on PostgreSQL because I think is a first class product.

Using the packaged way is almost immediate to install the product. Even the compile from source is a task any system administrator or advanced linux user can do it without any problem.

It’s an in house team.

Basically zero for both. The product is released under the BSD license and, apart from my salary, my employer have no extra costs on using PostgreSQL

I considered in the past MySQL and Firebird.

Employ a DBA to work together with the developers.

Out of all the open source database applications available, PostgreSQL is among the best DB storage engines with a single unified database server unlike MySQL which supports multiple storage engines for storing the data. PostgreSQL was specifically designed and developed with a focus on features and standards whereas MySQL was designed with a focus on speed. So, if you are looking for a large number of features and support for various standards, then PostgreSQL is the answer. PostgreSQL supports scalability on write intensive tasks. It also supports asynchronous commit, which is generally missing from other similar DB applications. It is fully ACID compliant.

PostgreSQL does not multiple back-end storage engines unlike MySQL. It does not perform well when dealt with read-only DB queries. It is not very efficient in handling COUNT(*) queries. PostgreSQL does not support queries like 'INSERT IGNORE', which inserts if a row doesn't exist, and 'REPLACE' which replaces the current row, both of which are supported by MySQL. Another query missing from PostgreSQL is "INSERT ... ON DUPLICATE UPDATE ". PostgreSQL does not have an unsigned integer data type. PostgreSQL is limited to 32 columns per index.

PostgreSQL is one of the best open source DB storage application which supports only one backend storage engine. PostgreSQL is well known for the number of features it supports and the standards followed. PostgreSQL is pretty slow when dealing with queries like COUNT(*) and many of the queries like 'INSERT IGNORE', which inserts if a row doesn't exist, and 'REPLACE' which replaces the current row. It is also limited to 32 columns per index. If you are looking for a speed, then you have to look for other DB engines available e.g. MySQL.

GIS function. Geography is a very important function/dimension for our f. Postgres helps analyse that easily.

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.

They need to develop an easy way to do a cross-DB query and some basic report visuals and alert systems would make it awesome, if they are possible.

>2 years

We had no deployment issues.

The product is quite stable.

There's been no issues with scaling it for our needs.

It has a great support community.

It's very easy, and you only need to familiarize yourself with its file structure. Sometimes you need to write your own plugin, so sometimes it is better to have it implemented by a vendor.

It's free as it's open source.

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.

Go ahead with the product which has the best use case for your organization. Cost is never an issue.

• It's open source product not need to license, so economic
• It provides a graphical interface (pgAdmin) simple, intuitive and efficient
• Simple installation 
• It does not consume a lot of resources
• Really suitable for business n-tier solutions
• Rich documentation
• An interactive community

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.

I think that due to the lack of functionality for data warehousing, it is more suitable for operational information systems instead of BI systems. Besides, it only allows Relational Online Analytical Processing (ROLAP) not Multidimensional Online Analytical Processing (MOLAP).

There have been no issues with the deployment.

We have had no issues with the stability.

It's been able to scale for our needs.

Because we use it in many information systems (Financial, Human Resources, Inventory Management) in several large companies with significant data flow, we have not had problems. It was effective as a product.

Read the product documentation well and know the configuration parameters because just one incorrect parameter can affect the entire database.

We use PostgreSQL for most part of our mission critical applications.

The solution has a very robust backup and recovery integration, and has good ANSI SQL language.

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

• Robust backup and recovery integration.
• Follows ANSI SQL.
• opensource
• easy to integrate with applications and high level programming languages such as; python, ruby, java, C, perl, php...

• Possibility to use query routers on sharded clusters.
• Remove the limitations of how many changes one can have on the databases before it requires to reset all blocks, which are very painful.

More than five years.

No issues.

Yes, as the database grows, one has to perform a full vacuum in order to continue to work on the database.

Another issue is that the "archive_command"s are executed in sequence, instead of in parallel, and as the WAL size is fixed to 16MB, and it is not possible to change in a configuration file, this will have a huge impact of protecting the WAL logs to a backup system.

Customer Service:

10 out of 10.

Technical Support:

10 out of 10.

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

The initial setup is simple.

We implemented it in-house.

The software is free, and very easy to find for skilled people.

Use backup software that integrates with the solution.

We selected "DB Protection for PostgreSQL", which has some nice features to perform block level incremental forever using IBM Spectrum Protect.

Yes, we reviewed MongoDB, MariaDB, and MySQL.

The spatial extension, PostGIS, is amazing and probably the gold standard. I also like the Key-Value column type and the JSON column type. Apart from this, it has all the other features you will need in an RDBMS and then some. It has a vibrant FOSS community with a great license and it has plenty of books and documentation

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.

They need to work towards making it work better in a cloud environment. Also, I would love to see them developm multi-master replication.

We have had no issues with the deployment.

There have been no performance issues.

It's been able to scale for our needs.

Get a good book so you can get exposed to all the great functionality in PostgreSQL. I would highly recommend looking at the postgresql.conf configuration settings when you are ready to go into production.

6 years

Authentication config could be made easier.

It's very stable.

From our use of it, its stability and performance are the best features. The fact that there's no downtime and that it functions quickly are very important to our workflow and business.

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

The multi-master replication feature needs improvement.

I've used it for eight years now.

We've had issues with deployment, but I can't share the details.

We've had issues with stability, but I can't share the details.

We've had issues with scalability, but I can't share the details.

We are running the open source version and haven't purchased technical support.

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

The initial setup is very straightforward.

The implementation was done with our in-house team. My advice is to get training.