PostgreSQL Reviews

We use this solution as part of our backend to store data that is coming from the sensors. 

It is needed to save the meter data from the sensors.

It is easy to use.

It could be more secure.

I have been working with PostgreSQL for approximately two years.

I am using the latest version.

PostgreSQL is a stable solution.

We use this solution for organization's applications at the backend and it is not used directly by the end-users.

I have not contacted technical support.

It is a bit different from Oracle, with respect to security.

The initial setup is straightforward.

It was a token installation, I can do it myself.

I would recommend PostgreSQL to others who are interested in using this solution.

I would rate PostgresSQL 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 primarily use the solution for management. We have a managed ERP solution, however, it's all in-house.

The ease of use has been a great benefit for us in the organization.

The solution is very easy to use.

The database has excellent performance.

It's easy to audit the database. When the user makes some changes to the database, it's easy to audit the changes. It's fairly easy to manage.

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.

I've been using the solution for two years at this point.

The stability is very good. It doesn't crash or freeze. It's not buggy and it seems to be glitch-free. It's good.

Really, I didn't have any problems with scalability. If a company needs to expand it, they can do so.

We only have developers that use the solution. 

We don't plan to increase usage in the future.

We don't use technical support, and therefore I can't really evaluate them. I have no idea if they are knowledgeable and responsive.

They do have documentation and manuals that are okay. They're pretty helpful.

The company used a Microsoft SQL Server previously. I don't know what the reasons were for changing, however, due to the fact that, when I arrived at the business, they already had Postgre.

I don't have any experience with the implementation. I didn't handle the process personally.

I'm unsure as to how long deployment takes.

You don't need too much staff for maintenance. We have one person that handles it.

It's my understanding that the solution was handed in-hours. We didn't use an integrator, reseller, or a consultant for the deployment.

I'm not sure what the licensing costs for the solution are.

I believe we are on version nine of the solution. It's one of the latest versions.

I'd advise new users to maybe be aware of the syntax of the sentences of PostgreSQL due to the fact that it's a little different than SQL or Oracle.

Overall, I'd rate the solution an eight out of ten. So far, we've been using it and we haven't had any problems.

The new JSON data type that allows to use some NoSQL-like functionality.

This is great because brings some of the most valuable features of NoSQL databases to relational databases. You can have a column with JSON datatype and then query that JSON inside your regular SQL queries. 

So basically, you are mixing together the relational and NoSQL world in just one database, one powerful solution. 

We use it as main database for our SaaS product.

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

I've used this solution for four years. 

No. 

See answer to 'Room for Improvement' question. 

We had several performance issues with MySQL.

Yes, MySQL.

Explore all the features.

• PostgreSQL streaming replication
• PITR-based backups
• CTE SQL
• SQL windowing functions

• 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

Get some expert help; I cannot stress this enough. We often walk into DB setups and architectures that are a wreck because the team "knew enough to be dangerous". Even more often, we see database isolation, meaning the DB is not connected to the enterprise data architecture. That mistake leads to expensive problems down the road.

It's an open-source, license-free product that can go head to head with the likes of Oracle & DB2 and hold its own in terms of features and performance, in many cases beating the competition.

• Stability
• Performance
• Ease of administration

It is a world class, performer, a scalable database that is free and open source.

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

I've been using different versions of PostgreSQL for the past eight years.

There was other a foreseen issues with pushing it to the edge.

It's a very stable product.

It's easily scalable.

The amount of community support for the solution is good.

We've got experience with a number of RDBMS, but PostgreSQL has always stuck out to be the most economical and sensible product. That being said, we do have instances of Maria, and various NoSQL's floating around.

We did it in-house.

We deployed the Postgre database on CentOS, which is a version of Linux. We have experimented with our replication and other operations. It works perfectly well. We are using the open-source version and do not plan on using any enterprise database.

PostgreSQL could improve by adding data warehousing tools.

I have been using PostgreSQL for approximately eight years.

PostgreSQL is stable.

The solution is scalable, it is very good.

We have approximately 100 users using this solution.

There is a lot of community support online to help with many things, such as updates. The online support is very active.

The installation is straightforward and simple, it took only half an hour.

We did the implementation through an in-house IT engineer.

We have a team of approximately five engineers that manage the solution.

We are using the free version of PostgreSQL.

I would recommend this solution to others.

I rate PostgreSQL a nine out of ten.

PostgreSQL provides a lot of valuable documentation and there's widespread usage of it.

I use it for personal projects. It's been really easy to learn and it's been useful since ramping up it use.

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.

I've used it for six months.

There were no issues with the deployment.

We have had no issues with the stability.

We had no issues scaling it for our needs.

I haven't had to contact technical support. There's been no reason to do so.

It was straightforward and well integrated into Rails applications across open source world.

Compare and contrast various database optimizations based on your needs. And when you come across issues, don't reinvent the wheel -- someone has probably had a similar problem to your own.