What needs improvement with PostgreSQL?

Postgres should focus on building a stronger knowledge base. They also need to expand their integration capabilities, so more tools and resources are available to manage it. But it is more secure than MySQL.

I don't think PostgreSQL supports bulk databases, so it needs to have more capabilities in terms of managing the bulk data. AI capabilities would be a good feature to be included in the tool.

Sometimes, it becomes slow because of the network. So, there is room for improvement in performance. Also, one more issue is that Postgres SQL doesn't allow multiple users to access locked tables at a time. I would like to see this feature in future releases.

Sometimes, the views create problems. If you don't have the view, sometimes what happens is you need to have the drivers properly set up for PostgreSQL. Mainly, I think issues occur when applying patches to views; other than that, there aren’t many significant issues.

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.

We often find the solution's datetime datatype challenging.

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

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.

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.

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

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.

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.

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.

PostgreSQL could improve by adding data warehousing tools.

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

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.

The performance of PostgreSQL could improve.

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.

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.

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.

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.

The solution could improve the integration.

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.

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.

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.

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.

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.

PostgreSQL uses high memory compared to its counterparts when a highly demanding load is involved, 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.

PostgreSQL doesn't have a feature for temporal SQL, which is useful for selecting version(s) of a row. Specifically the syntax SELECT FROM FOR SYSTEM_TIME AS OF ... This feature should be included in PostgreSQL. This feature is available in MariaDB, SQL Server, Oracle Database, and DB2.

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.

The pricing could be better.

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.

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.

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.

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.

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.