PostgreSQL Reviews

It is easy grow it from a small environment to a large one.

We use PostgreSQL as the basic tool for offering our data warehouse and BI solutions. This way my customers have a free tool and I can offer a lower price for our services.

It should have a better native client tool to manage the databases.

I've been using it for nine years.

We have had no issues with the deployment.

There have been no performance issues.

It's been able to scale for our needs.

I've never used it , but this tool has a big community and they are always open to helping.

We had some problems with bigger customers using MySQL so we moved to PostgreSQL.

It's very straightforward if you are using the default configurations. It can become complex when you begin to change these configurations to adapt it to fit your environment.

In-house because we a are a technology company. I always advise to look for a consulting company, sometimes the default configuration is not enough and the tool can become a bottleneck if it isn't properly configured.

My advice is to always begin with the free licenses, and if you see that your tool is becoming a strategic solution, you can look into obtaining professional licenses.

• Stored Procedures
• Full Text Search

One of our products crawls information from different web sites and then detects if some keywords are there based on a business logic. The business logic was programmed in Stored Procedures using Full Text Search to detect keywords that we wanted in the extracted text. Doing it this way, we keep the logic in the database and we only need to constructs need crawlers that feed the database with more text to process.

The Full Text Search functionality saved us a lot of time because we didn’t need to program that ourselves.

We don’t have any real database expert in the company, we are mostly developers. So I wouldn’t know if something would need improvement or we just haven’t learn how to use it properly yet.

However, less advanced programmers may have a bit of a learning curve. Also, it will make a difference with your database only once you get past the basic levels.

I've used it for over three years.

We've had no issues with the deployment.

Very stable product.

There have been no issues with the stability.

Haven’t try it yet. We solve our problems ourselves for the moment.

Straightforward, however, we are all advanced programmers so the learning curve might have been easier for us.

In-house. There is a lot of good information on the web and stackoverflow.

PostgreSQL is free, so great ROI!

We compared it to MySQL, Oracle and we though PostgreSQL Full Text Search functionality was the best for what we needed.

At basic levels the database won’t do much difference, focus first in learning how to build queries properly, create index, etc.

An image of our product achieved with Full Text Search.

It is fast, compact, flexible, and scalable. I like the fact it is not tied directly to a server OS, such as Microsoft SQL Server. Being open source it is very budget continuous for our clients.

There are a few little odds and ends like all SQL servers that differ from other SQL servers. The way it handles logical, the fact it does not support primary keys on views etc. My experience is all SQL servers have little differences from each other. PostgreSQL is far more robust and built for production use than MySQL which I have also used.

I would love to have primary keys on views. This function missing has made PostgreSQL harder than need be with Microsoft Access as a front end.

I have been using this as a back end server for various front end applications for about five years now.

We have had no issues with the deployment.

There have been no issues with the stability.

There have been no issues scaling it.

Like all open source community supported products, the technical support is hit and miss. I have found tho, there is a large user base and I can usually get good ideas how to do a work around within a few hours, day or two at the most.

We used Oracle, MySQL, Microsoft SQL Server. Oracle and Microsoft SQL Server were simply too expensive for smaller customers. MySQL had too many short comings to make it a workable solution.

The initial setup was pretty straightforward. A lot of the setup for a typical installation is a Linux scripted Boot-Install disk. Answer a few questions and you are off to the races.

Did the implementation in house. Not for everyone, but then, if you are installing and utilizing a standalone SQL Server you have to be a pretty computer savvy person.

Being open source this is not really applicable.

PostgreSQL is a great SQL database, powerful, flexible, but it is not something to be considered over other things. The most important issue for a database, if what back end do your mission critical front ends support. With PostgreSQL we found next to nothing we would not do with other open source applications.

Our primary use case for PostgreSQL is data storage. 

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. 

I do not use PostgreSQL regularly but I have been running a project that has been utilizing it for six years. I head a tight-knit group that includes a front end developer, backend developers, and hardware people. They deal with PostgreSQL and I do not have hands-on experience with this solution. 

PostgreSQL is stable and easy to use. 

It is very scalable and comes with a bonus: no licensing issues as you scale with your databases. 

Currently, 15 people use PostgreSQL at our organization. 

I am satisfied with PostgreSQL's technical support. 

The initial deployment was fine. If you read through the steps, you should be OK. 

The licensing is fine. It is not a paid database license. 

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

• Replication which enables us to use it for High Availability.
• The Foreign Data Wrapper means we can integrate it, and provide interoperability with other databases.
• Multi-master Replication helps us to distribute a database geographically without any hassle or performing maintenance for synchronization as this it is all done during the replication process.
• PostgreSQL has a cleanly designed object basis RDBMS, so there are many opportunities to hook/plugin the PostgreSQL to get more functionalities and features.

Before using PostgreSQL, we had a database issue that we were trying to solve with Oracle. However, Oracle is quite expensive and I heard from a colleague that Oracle increases their charges year on year.

There are many places that it could be improved through the provision of more plug-ins and extensions, such as data distribution, load balancing, new data types, indexing and searching, etc. They could also make it easier to access data manually.

PostgreSQL is Open Source Project, it is never ending development process and maintenance. Since 1996 up to now already 20 Years, PostgreSQL has been borne as Open Source, while before it was an academic research. There are already some improvement actually, such as: Load-balancing can be achieved by Multi-master Replication or PostgresXL with real clustering model. Multi-master replication a.k.a Bi-Directional Replication is best implemented in data distribution topology.

There are many solution from that new features. It already a time to go to implement it on High Performance Transaction system, huge system implementation, mission critical system, most of the time, PostgreSQL is implemented in the financial and service industries, including banks, insurance, loan companies etc.

As an Object based Relational Database, there are many opportunity for expansion of PostgreSQL in many ways. We can create another data type, we can create another programming languages for functions. etc. There are limitless opportunity for expansion of PostgreSQL features, and it is already surpassed Oracle, in terms of Performance, Capability and Enterprise Features.

We've been using it since 2003, when it was v7.x

We have had no issues around the deployment.

Usually stability issues are caused by misconfiguration or misuse.

We've been able to scale it for our needs.

Since this is open source it doesn't have its own support. Therefore, my company provides support as a Maintenance Service Provider. We offer 24/7 support as well as the delivery of sophisticated deployment, tuning, consultation, and support of PostgreSQL.

It was straightforward.

We were helped in the implementation by the vendor. You should always let an expert do the implementation as if it is configured incorrectly it can have a big impact on performance.

I would recommend PostgreSQL to anyone who wants to save costs and deploy a reliable enterprise class database server.

The graphical query plan analyzer in pgAdmin III tool is a very valuable feature. Fast bulk data load and extract feature using COPY is a very useful feature I have used.

Helped solve my problem to extract large amount of data in a specific order on a Greenplum application.

String manipulation functions can be improved. I could not find reverse string function and ended up writing my own. Similarly array functions like length of array etc where not available and we created our own.

I've used it for 4 years now.

PostgreSQL provides the perfect combination of freedom, reliability, stability, security, performance, power, and ease of use. Freedom because it is the only world-class RDBMS not owned by a company. Reliability because anyone looking among the tons of public bugs from other RDBMSs such as Oracle or DB2, and does a comparison with PostgreSQL bugs, will feel confident. PostgreSQL is secured by design, with their own firewall for host-based authentication. PostgreSQL has a superior optimizer, the performance is very good in heavily loaded environments, and it has unique features such as partial indexes and full text search support with GIN indexes. Regarding power, PostgreSQL is a best of breed RDBMS in terms of SQL capability, procedural languages (many of them), programming language and datatypes support (including JSON) and async LISTEN/NOTIFY. Finally, the ease of use or autonomy, is a very valuable factor; PostgreSQL have all the configuration in two single files (postgresql.conf and the "firewall" pg_hba.conf).

We have migrated some databases from Oracle to PostgreSQL lowering licensing fees and reducing the vendor lock-in, gaining sovereignty.

The are many items in my wish list - parallel access (in development), incremental backups, standard MERGE statement (there is a similar INSERT/ON CONFLICT DO), snapshot queries (SELECT AS OF TIMESTAMP), better monitoring stats views, a "trace" feature for a specified running backend, allow streaming replication for a standby from a previous major release in order to minimize downtime during upgrades (this could be difficult with physical standbys, maybe could be easier with logical replication). Of course, everybody needs to keep in mind that any wish list needs to point to the core features, because PostgreSQL is FOSS, and there are other ecosystems out there developing third party features. Here, my wish list for third party software factories is the HTTP->PL/pgSQL adapter, that will enable the development of an Enterprise Web Application Development Framework with just a database (like Oracle APEX).

I've used this solution for more than six years. I started using it in 2009.

Deployment is very easy in PostgreSQL.

Regarding stability, I never viewed runaway processes, nor needed to execute kill or use the Linux IPCRM command against PostgreSQL resources, unlike Oracle and DB2.

It is possible to scale-up (simply adding resources), on demand and without restrictions because PostgreSQL is free. Further, it is possible to realize read scalability with hot standbys.

Very good, based on the few opportunities where I have had to post a problem. I always got an answer quicker in the PostgreSQL forum than opening Oracle SRs or IBM APARs, and the resolutions were also more accurate.

I have more than 10 years of DBA experience, working with Oracle, DB2 and MySQL too. All of them have pluses and minuses, and I usually need to explain that nobody can claim "X is better to Y", at least with the universe limited to world-class RDBMS like PostgreSQL, Oracle, DB2 and MySQL. Of course, certain scenarios can mean that one RDBMS is better positioned than another to handle.

The learning curve is much friendlier with PostgreSQL than with Oracle or DB2. In fact, this could be a risk, because heavily loaded production environments usually needs DBA monitoring and intervention.

I did it in-house. The only advice is to read and learn from PostgreSQL documentation and related books or blogs. PostgreSQL is easy to start, but is a complex RDBMS with many screws to adjust.

There is no pricing/licensing at all. Of course, there are many companies offering PostgreSQL support at different costs and some specialized in several languages/countries.

Ask the community. I believe any committed PostgreSQL user will be happy to help and provide advice.