PostgreSQL Reviews

We use it to convert the databases. We also use it to make a request from my PMS with the Oracle-based server through the third-party interface.

We use this solution for the interface between our property management system and the cloud-based system. It works from both sides.

It is very simple to manage.

It is easy to use.

My main concern is that I can use it to connect with the interface. It is simple, it's good.

It needs more integration.

I have been using this solution for two years.

I have not explored the scalability of this solution yet.

I will continue to use this solution but I don't have any plans to increase our usage.

I have not contacted technical support.

The initial setup is straightforward. It was easy to install.

It took only one day to install, and two to three days to connect with the database.

We have a team of three, two admins, and one engineer to maintain the solution.

We had help from a company from Norway, one from South Africa, and one other from Dubai.

We do not pay for licensing.

Depending on the type of work the user wants to do with the interface I would recommend this solution or not.

I would rate PostgreSQL a five out of ten.

The solution is primarily used to develop the databases for your application. I used it personally for a college assignment.

The solution is open-source and therefore free to use.

You can do the same actions as you can with the SQL Server.

It's a standard reliable database management system.

The solution comes with an option to work in dark mode, which I appreciate.

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.

We've only used the solution for a few months. We used it for two projects. It was basically used across two semesters. We have used it in the past year.

The solution is not as stable in comparison to Microsoft SQL Server. I had some issues with a version, and I had to re-install it last year. Now, however, it's working fine. That said, they are always launching new updates and they seem to release them too early as they are not so stable.

I'm not sure if I will continue to use the solution. I used it for an assignment, and that's it. 

I did not contact technical support. I've never reached out to them directly. Therefore, I can't speak to how helpful or responsive they are.

I've also worked with Microsoft SQL, and I find the product to be much more stable.

The initial setup could be a bit better. They have some improvements to do especially with regards to the additional tools they propose. That part is just a little bit messy. Other than that, I thought it was very easy to install it. It's not overly complex.

I was able to handle the implementation myself. I did not need the help of a consultant or integrator. 

The solution doesn't cost anything to use. It's open-source.

I'd rate the solution at an eight out of ten. I'm mostly happy with its capabilities.

I wouldn't necessarily recommend this product for beginners. 

I am using the solution for data analytics, mainly for ERP because we use Hadoop and Hadoop is a dependency of PostgreSQL through the platform.

We are able to create many different types of jobs and items with this solution making it one of the most valuable features.

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

I have been using the solution for two years.

I think the technical support should improve for this solution.

I have previously used MySQL and am currently using it for other projects. MySQL is a little easier to use.

The installation is more difficult to install than other solutions I have used.

I rate PostgreSQL a seven out of ten.

The solution has many valuable features such as it easy to use and the interface is intuitive.

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.

I have been using the solution for a couple of months.

I have found the solution to be stable.

I have not fully tested the scalability but it has been good enough for what I have been using it for.

I did not experience any technical issues to call the support about.

The installation was easy even though it took approximately four hours. The time accumulated from downloading automatic packages from the VM tunnel. You have to download the whole package on your machine.

The solution requires a license.

I recommend this solution for small organizations.

I rate PostgreSQL a seven out of ten.

We design it and put it as part of our system and sell the system to various airports. We've designed our own schemas, and we track events that are meaningful to airports so that they can create their reports, view statistics, and make meaningful decisions that make sense for them.

It has completely met our needs. It works, and it is robust. We haven't had any problems with what PostgreSQL does for us and the way it does it. That's why we've been using it for so long. We understand it, and it does the job.

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.

I have been using this solution for 18 years.

It is pretty straightforward.

I would rate PostgreSQL an eight out of ten.

We use it as an intermediary database for the collection of a variety of data points out of our data systems.

There are many departments that have different data, single points of truth. We asked them to give us different datasets, and we accumulated them in our Postgres-stored database.

It's an intermediary for a machine learning model.

I am more of a fan of doing things straight out of Python, but with the size of the data sets, we were forced to do it in SQL.

What I like is that it's quite powerful in terms of performance.

Part of the reason we use this solution is because of its simplicity and because it works. It does all of the basic things it's supposed to do and it's not anything fancy.

They are fulfilling their customer's needs. 

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.

I have been using PostgreSQL for one year.

I had an issue where we couldn't find the fault, and it happened on occasion at the end of the day. Some of my basic queries would stop running. 

I had some queries run for two days and some run for a day, then I would have to try it again the next day and it would complete in 20 seconds. Sometimes, it seemed to catch itself.

I haven't had any contact with technical support from PostgresSQL. I do my research using Google.

I did not initialize this database, but from what I understand it's very basic. It was simple to do.

I would prefer programming languages to query languages. Scripting, for instance.

If you have a relational database then you want to use PostgresSQL. I would recommend this solution to others who are interested in using it.

It's suitable for everything we use. There was nothing exceptional from my perspective, but it did everything we needed it to do.

I would rate this solution an eight out of ten.

The database is used for our customers' products. We also offer some products on our POC system, and our customer's POC systems post some data stored on PostgreSQL on the cloud. Our company's data doesn't store at PostgreSQL. We still have our system MS SQL and Oracle.

The solution is very easy to use. You don't have to be extremely knowledgeable or technical to take advantage of it.

The product is quite flexible. 

We find it to be one of the cheapest options on the market. It's not expensive to use. 

The pricing could be better.

We've used the solution for ten years at this point. It may even be longer.

The solution is quite stable. We haven't had any issues with it. We haven't experienced bugs or glitches. It's reliable.

The solution is scalable. We've made some upgrades on our system, and it was so easy to do for the actual upgrades. In terms of the database itself, we haven't really had any issues with it.

I don't have any experience with technical support. Other teams in our company end up handling that. I can't speak to their knowledgeability or responsiveness having never worked with them.

I don't recall us using a different product.

In terms of the initial setup, we generally use the cloud system. The cloud system is very easy to set up these days. If you choose some with pre-installment, you trigger the system, and it's pretty automatic. You don't need a lot of things configured. After that, after you start to use it, you can tune it as you like. We made some adjustments on the system - such as additional storage or additional RAM or other resources - and we were able to add those in very easily.

The production system we use for reporting is a read-only system. Due to this, if we use the production system for reporting or other kinds of big data, the system can be slow on the customer side. However, Postgres can still service all the tasks which we need.

We haven't needed too many people to handle deployment and maintenance. There's been around ten or so that have been on it.

The pricing is reasonable. Of course, our economy has been hurt a little due to COVID-19. The pandemic has affected a lot of us. It's been hard for the companies that sell services with a database cost. You really have to choose the lowest-priced options right now. Postgres offers a fair price on the market, currently. That said, it could be less expensive, especially right now.

We definitely plan to continue to use the solution in the future. It's been quite good for us.

That said, I'm not in the financial department and I don't know the exact cost of the solution.

We're just customers and end-users.

We generally use the last version, as we try to ensure all of our programs are the latest technology. Therefore, we generally use cloud platforms like Amazon or Microsoft, which is Azure. Whichever version is on the cloud, we generally use that version.

That said, some of it is on the cloud and some of it is on-premise. In Turkey, we have some legal requirements that require some data to be stored in our country. We have to store it locally. Therefore, we can't use the cloud completely.

I'd recommend the solution to other organizations.

I would rate the product at an eight out of ten.

One use case is that we installed it and built it for a customer so that he has access to the database, and he can create whatever he would like to create on it. 

We have deployed it on-premises and in the cloud.

It is easy to install and easy to manage. There is no license on it, so it is free. 

There is high compatibility with Oracle, and there are many tools for the migration of data from Oracle to Postgre. 

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. 

I have been using this solution for almost one year.

I didn't have any issues, but I think Oracle is more stable.

I didn't have experience with that because we didn't make any changes since we built it. All I have is one server, and I can only have one standby, nothing more. 

We didn't contact them. We didn't face any serious issues that required support.

I am also using Oracle Database. The main difference is the scalability. PostgreSQL could be used for small to medium databases but not for a huge production database. I still prefer to have Oracle Database.

The initial setup was straightforward. It did not take too long. It took maybe one hour to do the installation.

It is free. There is no license on it.

Go ahead and implement it. It is a nice product, but keep a backup and try to use it for small to medium projects or companies. Some of the customers are demanding PostgreSQL nowadays, so we will keep on implementing it.

I would rate PostgreSQL an eight out of ten.