Please share with the community what you think needs improvement with PostgreSQL.
What are its weaknesses? What would you like to see changed in a future version?
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
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.
We all know it's really hard to get good pricing and cost information.
Please share what you can so you can help your peers.