PostgreSQL Reviews

I have implemented costing models. I use it to capture item costs and then do calculations to compare costs.

The built-in code procedural language is the most valuable. It has a built-in layer for code procedures. 

Its installation is very easy and quick, and it is free. It is also stable, and its performance is also good.

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. 

I have been using this solution for six to seven years.

It is stable.

For my use case, it was good enough. I didn't use cluster or other such things. In my previous organization, we had 10 and 20 users. In my current organization, we don't have any other users.

I haven't used the paid support. I always find information from open forums and technical guys on the web.

I was previously working in a research organization, which favored open source. I have also used Oracle, Sybase, Microsoft SQL Server, and Ingres databases.

Its installation is very easy and quick. I am running it on Linux. It took a few minutes to install it.

I do it myself. I have been doing it for a long time. For its deployment and maintenance, one DevOps person is sufficient.

It is free, but if you need support, you can go for the commercial version called EnterpriseDB. They provide paid support, and they can even do hosting for you if you want standby and support.

For our current use case, I'm evaluating PostgreSQL versus MariaDB. I am probably going to use MariaDB because I need the temporal SQL feature, which is not available in PostgreSQL.

I would 100% recommend this solution to others. I would rate PostgreSQL a nine 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.

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.

I am using it to gain knowledge of the product, as I am an implementation engineer. Some clients are public organizations, migrating from Oracle to PostgreSQL.

We use it daily.

The most valuable features are:

• The price
• Stability 
• It is scalable and is used by our clients in small business environments
• It is a simple product to use.
  

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.

I have been using PostgreSQL for one year.

The product is very stable.

The setup of PostgreSQL is straightforward.

We use an in-house team.

I would rate PostgreSQL a ten out of ten. 

We use PostgreSQL for most part of our mission critical applications.

The solution has a very robust backup and recovery integration, and has good ANSI SQL language.

We are considering migrating to this platform due to its robust backup and recovery solution, among many other features.

• Robust backup and recovery integration.
• Follows ANSI SQL.
• opensource
• easy to integrate with applications and high level programming languages such as; python, ruby, java, C, perl, php...

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

No issues.

Yes, as the database grows, one has to perform a full vacuum in order to continue to work on the database.

Another issue is that the "archive_command"s are executed in sequence, instead of in parallel, and as the WAL size is fixed to 16MB, and it is not possible to change in a configuration file, this will have a huge impact of protecting the WAL logs to a backup system.

Customer Service:

10 out of 10.

Technical Support:

10 out of 10.

We switch to this solution due to its stability and that it is open source.

The initial setup is simple.

We implemented it in-house.

The software is free, and very easy to find for skilled people.

Use backup software that integrates with the solution.

We selected "DB Protection for PostgreSQL", which has some nice features to perform block level incremental forever using IBM Spectrum Protect.

Yes, we reviewed MongoDB, MariaDB, and MySQL.

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.

It works great out-of-the-box and it opens up many opportunities in project development.

I first install the regular version. I only configure complex things when they are needed.

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.

I've used this solution for two years.

There were no issues with stability.

There were no issues with scalability.

I would rate the technical documentation as an eight out of 10. I never spoke with the support team.

I used MySQL. I switched because at that time, because some things were complicated with MySQL. For example: scaling, sparse data JSON, and other issues.

Both projects have the same query syntax, and the transition for me was almost painless.

The setup was easy.

As far as I know, there are no problems with the license for free use.

I explored many different databases: Redis, MongoDB, MySQL, Elasticsearch, and others.

I use some of them in conjunction with PostgreSQL. However, if we are talking about relational databases, then I only use MySQL.

I think this is the only decent solution for a relational database in web development.

PostgreSQL is an open source database, so there is no associated licensing cost for the software and we always have a new version easily available. It runs on all major operating systems, although I have always used it on UNIX platforms.

It also supports storage of binary large objects, including pictures, sounds, or video. It is highly scalable, both in the sheer quantity of data it can manage and in the number of concurrent users it can accommodate.

PostgreSQL runs stored procedures in a lot of programming languages (Java, Perl, C/C++, etc.). It includes many built-in functions from basic math and string operations to cryptography and Oracle compatibility. Triggers and stored procedures can be written in C and loaded into the database as a library. PostgreSQL uses a multiple row data storage strategy called MVCC to make PostgreSQL extremely responsive in high volume environments. Allow hot backups.

I have worked at the Ministry of Economy in the IT area, for more than 20 years ago. Since then, the main developments have always used PostgreSQL for their robustness, reliability, stability, and conformity with the standard SQL.

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

We had no issues. PostgreSQL statistically does not suffer falls, it simply works.

We had no issues. We had to modify some configurations but the impact was almost transparent.

All the obstacles that we encounter are solved with information obtained on websites. PostgreSQL has a community of thousands of users and professionals who contribute their experience, so I always have found a solution for all my issues.

I have used other solutions for over 20 years and the problem of licensing has been our biggest drawback because of the costs and dependence we require from the provider.

It is extremely simple. In addition, we have several databases in production so we always start with a configuration model already tested and reliable.

I recommend PostgreSQL without doubt because my experience of almost 20 years with this product has shown me that PostgreSQL has certain features that make it highly reliable: high scalability, robustness, available for multiple platforms, extensible with little effort and without additional cost, designed for high volume environments, easy to manage and extensive online support.

I recommend everyone to get into the PostgreSQL world, with no licensing costs. PostgreSQL uses a flexible and business-friendly license because it does not restrict the use of PostgreSQL with commercial and proprietary applications. Those who choose PostgreSQL forget the dependency on a provider, the price of the licenses and the changes in the license conditions.

We got carried away by the experience of a team member with experience in PostgreSQL and first we used the tool in applications of low concurrency of users but with storage of files pdf, doc and xls in the tables. We were surprised by the results. This is how we trust in PostgreSQL and we demand more and more. We always get good results. Sometimes we have had to migrate to a new version of PostgreSQL, but have done so without any problem(s).