We have to set up event API, which takes a lot of events from the user. For us, Postgres DB wasn't performant enough to use, so we had a bottleneck there. We use Cassandra, which drastically improves but isn’t a drawback of Postgres. It is common with most SQL databases.

View full review »

PostgreSQL’s performance could be improved.

View full review »

While it can scale, sometimes it requires more knowledge than SQL Server. 

They need to improve the user experience of the management. I'm not aware of Postgre needing a lot of new features, however, they can improve the user experience. That would be awesome. The backup strategies and that kind of stuff could be much better.

View full review »

PostgreSQL could improve by providing a geographical solution for tracking trucks and people in the field. They might already have features similar to this and I have not found them. I haven't done research about this topic.

View full review »

I find it difficult to get connectors on the tool. For example, .NET has only one free provider in PostgreSQL. I need to pay the provider if I need something more sophisticated features. Other languages like PHP and Java have good community support. We need community support for .NET.

View full review »

The search option is not very good. If I need to see data in a table, I must go into the table. The solution must provide filter options in the log files so that we can search for a particular range of data.

View full review »

There could be a plugin to distribute the data on servers for the product.

View full review »

I'd like to see better memory management. I think that that's one of the few areas that Postgres does not handle as well as MySQL does or did. 

View full review »

We don't have any use cases where we would use it in a large application as we do with Oracle. This is one limitation of this solution. We are unsure when it comes to deploying a large 24/7 application. 

It is possible that in the newer version this has been addressed, but I would like the deployment in microservices architecture could be improved.

View full review »

We often find the solution's datetime datatype challenging.

View full review »

I have noticed that user and access management should be improved. Connection pooling should be improved. We rely on connection pooling.

Monitoring is incompatible. It is open source. To advance, you must access the internet and download and test various other tools, or develop your own tools. With Microsoft server, it is one single platform that provides you with everything, but with Postgre you have to install or check different tools to integrate with it. That's the annoyance, but it's still the way open source technology works.

I would like to see better management in PostgreSQL.

View full review »

By far the biggest limitations are in replication support. A native master to master replication option would make things much easier as we're in need of an easier method to load balance traffic with Spring Data.  

PostgreSQL is slower than MySQL with insert performance. While using COPY can make an application fast, we often use ORMs which cannot benefit from this. 

9.4 seemed to have some regressions with the query planner and multi table joins are slower than in previous versions. 

View full review »

They need to have a better graphical interface. There is a tool called pgAdmin 4 that they use, which is free. It is written in Java, and it is slow. They need to have a better product that is similar to Toad for Oracle, but, of course, it is hard to get something that's really great and free. Other than that, it is great.

View full review »

I would really like to see a more mainstream approach to support what we see as critical extensions. One example is the FDW (foreign data wrapper) for MSSQL. This extension hasn’t been updated in several releases and would benefit from an overhaul. In general, the Postgres community is not as enthusiastic about supporting integration with Windows products (MSSQL, AD, etc.) as they are about other products like Oracle, GIS and full-text searching.

View full review »

It would be good to have machine learning functionality in this solution, similar to Microsoft SQL Server and other solutions. Machine learning capability for a basic level or a common user would be useful.

It can also have good reporting capabilities.

View full review »

PostgreSQL uses high memory compared to its counterparts when a highly demanding workload with many database connections is in use, especially one that makes many concurrent connections to the database. 

Like many other databases, the tuning is manual through a configuration file. It would be useful if the database engine could detect the specifications of the machine in which it is installed and so bring some levels of auto-tuning. 

PostgreSQL replication support isn't so straightforward for multi-sources and master replicas. It will be great if native support of those replication modes become available in the future.

View full review »

Currently, we are working with Postgre's economy, and we are not able to implement real-time solutions with our existing architecture. There's a general lack of real-time data from Postgre.

The solution isn't as stable for larger data sets. 

The scalability is limited.

We'd like the solution to be faster. 

View full review »

I don't work directly on development, however, I haven't heard of any complaints from the development team in general. I can't speak to any features that may be missing. Our team seems quite satisfied with it overall.

It would be great if the solution offered even more integration capabilities.

View full review »

PostgreSQL is limited to 32 TB in maximum table size for version 9.6 and earlier. This can be problematic for large databases. We currently don't have the multi-tenant feature and we require that with the contract integrated reassurance. To create have one tenant or more tenants, I need to implement or develop a software solution to connect with the multi-tenant, and to connect each tenant. PostgreSQL is not great for software developers, but it is adequate. For developers, databases such as Firebase and MongoDB technology are better. With PostgreSQL, all you need the database for is to save your data. This function on its own is not enough. The database and applications can become very slow. To debug you need to make the database query display information on your device. Some developers are not experienced in developing databases. This is especially difficult for junior software developers, and they often need more experience to be able to deal with that aspect.

View full review »

It still needs to be more mature and have some backup feature. We are normally dealing with Oracle's data, and we have very strong online tools to back up the data and do other things. PostgreSQL still needs to do more in this area as well as in the high availability area. There are many external tools that you can use for PostgreSQL's high availability, but there is no embedded tool within PostgreSQL for high availability.

It could have a feature similar to Oracle for working on a distributed system. It can have some scripts to improve the monitoring and some tools to do performance analysis. We have a workaround for most of such requirements except for the support for a distributed system, which is very difficult to have. This area should be included in the core of the database itself. 

View full review »

The solution could be improved through an upgrade to the latest version. 

A better graphic user-interface would be nice to see. 

There is nothing I particularly dislike about the solution. The data propagation in master-slave configurations would be a good example. This is one of the features that I understood the least, yet we have it working and use it to propagate from the content management system database to the multiple publishing databases. 

This said, I would like this propagation feature to be simplified for new users and to come with better explanation. However, I will refrain from giving criticism on this point, as I do not know if they already handled this in the last version. Overall, I have only praise for the solution.

I cannot point to anything in particular that we are missing out on at the moment. What comes to mind are features that I have yet to try, although I don't  have any wish lists for PostgreSQL at the moment. I don't know how it stacks up when it comes to the importing and exporting of data. For databases involving this, we just make use of Redshift, which is verified from PostgreSQL and developed by Amazon. 

View full review »

The pricing could be better.

View full review »

If you look at overall PostgreSQL, it could be easier to use.

I'm not yet able to use all of the features on the product at this time. 

I'm not really able to customize it.

The integration could be easier. SQL Server has an easier integration process, for example, as a comparison.

With Postgres, you can run it in Windows Server, however, there are other things that you have to run.

The product is more for technical people. For example, SQL Server is for anybody. Even newer users can just pick it up and learn from it and mess with it and run it. You can't do that with PostgreSQL. It has more of a learning curve. YOu need more training and documentation.

View full review »

The performance of PostgreSQL could improve.

View full review »

There are some products out there that have a slightly different method of implementation for the SQL language. Some of those are slightly better in some areas, and PostgreSQL is slightly better in some areas. I would probably like to match all of those products together. It is just down to the functionality. For example, Oracle has a number of options within SQL that are outside of what you would class as the SQL standard. PostgreSQL misses some of those, but PostgreSQL does other things that are better than what Oracle does. I would like to merge those two products so that there is a certain amount of functionality in a single product.

View full review »

The performance is too low, although we haven't tested for this. 

The interface climate could be better. There are many third party ones that we can use so it would be nice to see more support with the database diagrams.

View full review »

The price could be better.

View full review »

There are still things missing compared to other RDBMS, for example monitoring is a little behind as there not that many solutions out there. An equivalent of Oracle's RAC and/or flashback logs would be nice to have. There are a lot of steps need to get it back on the right direction with the logical replication and the parallel sequential scans.

What I mean is that despite the fact that there are things missing (like monitoring solutions and/or flashback logs etc.). Lately, there have been some developments that seem promising and set Postgres to a proper path. Two of these developments are the logical replication and the parallel sequential scans, and compared to other RMDBs, some could say that these are long overdue but nevertheless, they are a great addition and will definitely improve the performance/scalability/replication-capabilities of postgres in the current version and in the versions to come.

View full review »

v9.5, which we currently don't have in our productive systems, already has some key features that we would like to use. In particular, row level security, a feature allowing to restrict the visibility of rows based on a set of policies. A feature that is not available yet and I would welcome is more of a by-product. PostgreSQL offers very good documentation features, which we integrated in the technical documentation on our internal Wiki. Changes in the database are immediately available in the Wiki without the need of editing the Wiki page manually. It is possible, and we do it, to attach comments on objects and their components. These comments also appear then in the Wiki documentation. Unfortunately it is not possible, i.e. there is not an implementation yet, to attach comments to function parameters and return type. We make extensive use of functions as structured interface to applications. This feature would make our documentation more complete. We created a workaround for that, but still, it would be nice to have it built in the database.

View full review »

I would like to see the ability to reorder columns on a relation, as well as change the base SQL query that generates a materialized view without having to drop the view, provided the view's structure is unchanged.

View full review »

JSON support although great, it still has some gotchas, querying and manipulating JSON will be one of the topics I'd like to see some improvement, still feels not natural to work with it.

View full review »

I don't work with the solution often enough to really know if there are any missing elements. For me, for how I use it, it works fine.

We're only really using two to five percent of the functionality available.

While there's no perfect solution, we aren't using too much of the functionality to really be able to comment on what might be missing.

If it was free to use, it would be the perfect solution.

View full review »

The interface could be much better. Maybe it took a little bit longer to understand the menu options and so on. On top of that, it's a web interface. It makes it uninteresting to look at. It's not so appealing as the options that Microsoft offers. It's a separate program that works separately and you don't mess with the browser. It works okay, you can do what you need to do, however, it's not, in my opinion, so professional-looking. That said, it's open-source so I can understand that they prefer to do it like that.

The installation process could be better organized.

The stability could be better. they release new versions all the time and they aren't quite as stable as we'd like them to be.

View full review »

It could be improved by using parallelization. We want distributed computing. Some databases handle huge volumes of data better, such as the NoSQL database, MongoDB which can handle 100 000, or a million people using the same data search. PostgreSQL is going to take longer to do this, but it is more structured, and unlike MongoDB data is less likely to be duplicated. Large volumes of data can be handled better in PostgreSQL if the queries are written well.

View full review »

The product has room for improvement with horizontal scalability and multi-master replication options, where community work is already in progress. These features will greatly benefit customers by balancing the load between servers, resulting in great performance improvement, scalability and high availability at a fraction of the cost.

View full review »

The only thing that could potentially be improved is PGAdmin3, the DB Client that's has not been updated in quite a while. PostGres keeps ahead of the curve on it's feature set. For instance the new JSON column that's come out recently to provide nosql functionality that has been benchmarked to outperform mongo.

View full review »

Starting with v9 it can be seen an intensive activity to bring more features, more performance or productivity. I would like to see it be more reliable, and easier if possible, to make PostgreSQL clusters - more machines working together as a single instance .Providing an autonomous solution to share data across machines or replicate when it's needed. I would like to see horizontal scaling, up and down, made easier, and if something happens (I've rarely encounter cases after version 8), easier recovery from database general failure.

View full review »

PostgreSQL could improve by being more user-friendly. In SQL Server they have a studio where you can easily do management but not in this solution. 

View full review »

PostgreSQL doesn't have a feature for temporal SQL, which is useful for selecting version(s) of a row. 

Specifically the syntax 

SELECT 

FROM <table> FOR SYSTEM_TIME AS OF ...

This feature should be included in PostgreSQL. This feature is available in MariaDB, SQL Server, Oracle Database, and DB2. 

View full review »

It should have a better native client tool to manage the databases.

View full review »

We don’t have any real database expert in the company, we are mostly developers. So I wouldn’t know if something would need improvement or we just haven’t learn how to use it properly yet.

However, less advanced programmers may have a bit of a learning curve. Also, it will make a difference with your database only once you get past the basic levels.

View full review »

I would love to have primary keys on views. This function missing has made PostgreSQL harder than need be with Microsoft Access as a front end.

View full review »

As PostgreSQL is an open-source product, you do have to do a bit more configuration and management yourself. I would like to see it become more user-friendly. 

View full review »

I have noticed that it consumes a lot of resources. I would improve this aspect.

View full review »

There are many places that it could be improved through the provision of more plug-ins and extensions, such as data distribution, load balancing, new data types, indexing and searching, etc. They could also make it easier to access data manually.

PostgreSQL is Open Source Project, it is never ending development process and maintenance. Since 1996 up to now already 20 Years, PostgreSQL has been borne as Open Source, while before it was an academic research. There are already some improvement actually, such as: Load-balancing can be achieved by Multi-master Replication or PostgresXL with real clustering model. Multi-master replication a.k.a Bi-Directional Replication is best implemented in data distribution topology.

There are many solution from that new features. It already a time to go to implement it on High Performance Transaction system, huge system implementation, mission critical system, most of the time, PostgreSQL is implemented in the financial and service industries, including banks, insurance, loan companies etc.

As an Object based Relational Database, there are many opportunity for expansion of PostgreSQL in many ways. We can create another data type, we can create another programming languages for functions. etc. There are limitless opportunity for expansion of PostgreSQL features, and it is already surpassed Oracle, in terms of Performance, Capability and Enterprise Features.

View full review »

String manipulation functions can be improved. I could not find reverse string function and ended up writing my own. Similarly array functions like length of array etc where not available and we created our own.

View full review »

The are many items in my wish list - parallel access (in development), incremental backups, standard MERGE statement (there is a similar INSERT/ON CONFLICT DO), snapshot queries (SELECT AS OF TIMESTAMP), better monitoring stats views, a "trace" feature for a specified running backend, allow streaming replication for a standby from a previous major release in order to minimize downtime during upgrades (this could be difficult with physical standbys, maybe could be easier with logical replication). Of course, everybody needs to keep in mind that any wish list needs to point to the core features, because PostgreSQL is FOSS, and there are other ecosystems out there developing third party features. Here, my wish list for third party software factories is the HTTP->PL/pgSQL adapter, that will enable the development of an Enterprise Web Application Development Framework with just a database (like Oracle APEX).

View full review »

It needs more integration.

View full review »

The only thing I would really want/need to improve is pgAdmin3. pgAdmin3 is a nice tool for SQL Admin and Queries. But, I wish it would allow multiple queries to be run and displayed in the output pane.

Also, it would be amazing if Full-Text Search would work on encrypted data, but I don’t know how that would be possible with any kind of speed.

In regard to pgAdmin 3, there are so many times I’m in one window running different queries. In Microsoft SQL Server, you can select and execute multiple queries and they are shown in the output pane as separate sections. In pgAdmin3, I have to open multiple windows and execute separate queries and jump from window to window looking at / comparing results.

For the Search/Encryption, PostgreSQL supports having certain fields encrypted in the database (https://www.postgresql.org/docs/9.5/static/encryption-options.html). It also supports Full Text Search (https://www.postgresql.org/docs/9.5/static/datatype-textsearch.html). But, if we encrypt the fields where the lexemes are stored, search won’t work. (Some of the lexemes could give too much information if a user got their hands on the table.)

View full review »

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.

View full review »

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.

View full review »

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.

View full review »

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.

View full review »

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.

View full review »

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

View full review »

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.

View full review »

It needs more parallelism for big tables. This is already in PostgreSQL 9.6 beta so things are looking promising.

View full review »

There are several features I would like to improve that aren't working as expected. It's likely that the latest version is doing something that was missed in the previous versions. For example, the output parameters — the stored procedures — is something new in PostgreSQL that Firebird has already had for a long time. We haven't tried the latest version, but they're supposed to add some of the most important things.

View full review »

It could be more secure.

View full review »

I had some issues when I integrated with the Jupyter Notebook. 

In the system administration, if you open the connection to the database with a notebook, there is no automatic closing of this connection. 

I would like to see seamless integration with other tools such as Jupyter Notebook. We use it with Anaconda.

Also, possibly more streamline integration with more programming languages. An API for some different languages such as MARGO and JavaScript could be interesting.

View full review »

Synchronous replication is needed, and although I have only searched the web for a couple of hours the only solutions I could find were at the application level of the database.

XML and JSON manipulation functions need to be improved as for some applications we need to add new elements to these "structures". To do this with JSON I currently use a PL/v8 extension.

View full review »

PostgreSQL could improve by adding data warehousing tools.

View full review »

Extensibility could be even better as there are still too many things that require programming in C to add to the database. There could also be better object-oriented support. The table inheritance feature is critical to some of my work, and I wish a similar concept existed for other objects.

View full review »

Logical replication would be a major improvement and it's already being worked on. It'll enable true multi-master replication and active-active setups. More OLAP-related performance improvements are also on the way with parallel query processing and parallel background workers being to most significant ones.

View full review »

Parallelization and some connection to analytics is needed.

View full review »

The biggest issue that we are having is upgrading and moving databases between servers and versions. Restoring database is slow with pg_restore because indexes are need to be rebuilt. What I'm missing is a query profiler similar to what is in Microsoft SQL Server. PgAdmin should also be easier to use for beginner users.

View full review »

Simplicity in design and improvement with programming languages like PHP.

View full review »

It could be easier to perform some fragmentation in the database. It's possible, but still a hard job.

View full review »

The commands for PostgreSQL work, but are behind the curve compared to Microsoft SQL and MySQL. Adding additional functionality to be move comparative to Microsoft SQL would be a nice to have. For experienced users needing to make configuration changes, it is straightforward, but for users who are new to PostgreSQL they need some help working within the config files, a GUI for config may help with this.

View full review »

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.

View full review »

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.

View full review »

This solution could be better integrated with other systems. 

View full review »

The solution could improve the integration.

View full review »

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.

View full review »

Replication is not yet as well implemented as in MySQL.

View full review »

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.

View full review »

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

View full review »

Eliminate the transaction wraparound possibility. If transaction wraparound occurs it can be a major problem.

View full review »

Sometimes it hangs and then we need to stop and start the services again

View full review »

We'd like to be able to start using JSON objects for easy code representation. This feature is available in v10.4.

View full review »

In the next release, I would like to see better integration with other platforms.

View full review »

The solution needs to improve the query, documentation, and JSON data functionality.

View full review »

The only feature where I can see an area of improvement is with the partitioning. As soon as you implement partitioning, all your relationships are no longer supported since the PK-FK relationship is no longer supported and you need to look for options or database changes to supported with secondary tables, database rules or triggers.

View full review »

It would be interesting to have a cloud based database instead of having to install it on any single machine.

View full review »

There is room to improve some user friendly properties such as input and output tools, some people may find interesting to implement MERGE as a SQL command. I am looking forward to trying UPSERT and would like to test some analytic functions definitely.

View full review »

A better export facility which is GUI friendly would be an improvement. Also if we could export data from grid that would have been helpful.I have used HeidiSQL for MySQL which is very user friendly, pgAdmin III is not that helpful when it comes to different features we need to use like export,filtering and connections.

View full review »

It needs better support for JSON and web services.

View full review »

Instead of the installation agent downloading all the packages for the install, it should allow the user to download the packages separately on their own to do the install.

In a future release, the installation agent should take less time to create all the databases, especially the small Oracle databases that I was using.

View full review »

When you get a large number of records in a database and start doing various queries, it can adversely impact the performance of the live running systems. That's an area we continue to look at and mean to improve, but it is not only because of PostgreSQL. It is also because of the way the schemas are put together, and certain events are triggered. So, it is because of both parties.

View full review »

The human resources, the HR, within the system needs improvement.

The user interface could be a bit better. 

Just the basic functionality could be improved overall.

View full review »

Scalability;

Although PostgreSQL is known for handling very well large amounts of workload, NoSQL databases performs better when scaling. NoSQL databases were built with scalability in mind, so it´s a natural advantage. 

PostgreSQL must keep improving their scalability and ability to work in HA (high availability).

View full review »

I'd like to see the following improvements:

• Streaming replication (or similar) disconnected from the version, so we can use it for upgrades (i.e., a 9.3 version master and a 9.5 slave)
• Better scaling options such as sharding tools, parallel query and star schema-aware queries
• Better partitioning support to include better / packaged partition management and the ability for the base table to return the number of rows affected even if the affected rows are in a partition

View full review »

At the fringes, you can have locking problems that can cause unacceptable pause, but that's really a factor of database design, and the limitations of relational databases as a technology than a particular issue with PostgreSQL

View full review »

Although there's documentation out there, it needs even better documentation. Another thing that would be helpful are examples of usage of it with JavaScript.

View full review »

I have a dream that a database could import data safely and securely from other databases without errors and by using a GUI to help migrate the data. 

View full review »

It is lacking some GUI admin tools and it would be nice if more could be developed by the community.

View full review »

I find, sometimes, that it is too restrictive in cross-table/view constraints. This is very annoying as I needed to change a field definition from VARCHAR(10) to VARCHAR(30) and, having a group of views depend in it, the only solution was to implement a function that would:

• Read the view definitions
• Store them
• Delete the views
• Update the field definition
• Recreate the views

It took me like three or four hours (and caused a lot of stress) to make such a simple change. To me it looks a bit too overkill, especially nowadays that application requirements and implementation change so often.

View full review »

Parallel processing of queries.

View full review »

The user interface for the clients could be easier to use as they are small businesses.
From a technical support perspective, the documentation could be improved. The simplicity and availability of documentation and transparency need a little improvement. The product also needs more service support. However, there is a good online community that can help to quickly find a solution.

View full review »

It lacks the ability to distribute queries across multiple installations out of the box.

View full review »

I believe that drivers must be better. For example, the .NET drivers could be more robust for the latest Entity Framework version.

View full review »

It requires better management tools.

View full review »

I would like to have better support for real-time applications.

View full review »

Slow count. As the number of rows exceed a couple million, the count query and queries which get to the depth of the data (like FTS) start taking too much time even with all the right indexes in place.

View full review »

• Windows versions were released ten years after the initial release • Replication is not so powerful in later versions • Postgres is not so popular compare to MySQL • PostgreSQL community has lesser support View full review »

I think that the product fully meets the needs of modern development. If there is something missing in it, then it is probably a too narrow profile function.

View full review »

I would to see the following improvements:

• Replication: Table-level replication should be built-in. However, we can do this now by using Slony.
• Backup: Currently, an incremental backup feature is not available. It should be added.
• A simple-to-use PG cluster monitoring dashboard would provide an extra advantage.

View full review »

Comercial & Supply Chain View full review »

The partitioning, is still very basic and not touched for years. View full review »

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. View full review »

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.

View full review »

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

View full review »

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

View full review »

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

View full review »

The multi-master replication feature needs improvement.

View full review »

I'd like to have NoSQL available in this version. It is available in the latest one.

View full review »

1) It tends to be slower when processing a large number of records.2) Does not support the entire ANSI SQL 92' standard.3) More open source applications (software stacks) supports MySQL, but some of them may not support PostgreSQL4) Comparatively small user community than MySQL 5) Installation and setup is bit complex and requires technical know how. Though PostgreSQL is comparatively slower than MySQL, but can handle a heavier workload, and also supports various SQL features like foreign keys, triggers, stored procedures and transaction rollback. View full review »