PostgreSQL Reviews

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

The use of extensions for integration with different databases is valuable.

Our organization has MySQL, Oracle, PostgreSQL and flat files in our processes, and the use of extensions has facilitated the integration between these processes. Also, it's only 7-8/10 when comparing it to an Oracle database.

The use of XQuery besides XPath into PostgreSQL. It would also be nice for them to add some backup features similar to the one that Oracle Recovery Manager has. Also, a tool to query archive files would be a nice addition, and being able to change the execution plan through hints like we do in Oracle. There are some more but these would be my favorite ones.

I've got six years experience with PostgreSQL, and 18 with Oracle.

No issues encountered.

No issues encountered.

No issues encountered.

I'd rate it as 10/10 as an open source product with an active community.

I'd say it's good.

We initially only used an Oracle database, but we decided to add PostgreSQL as an option because of its similarity to Oracle. Also, it's free and is the best open source database.

It is simple, especially when you know the main components of a database.

We implemented it in-house.

We didn't have any setup costs because it is free.

• MySQL
• SQL Server
• Sedna XML

I'd say go for it. It is stable, and easy to use but you should get an understanding of it to implement backup strategy.

I had many problems on v8.3 when I needed to use SSL client certificate authentication but on version 8.4 my problem was resolved, I’m an information security specialist and my focus is it so all features about security for me is important and the security on PostgreSQL after 8.4 was good.

I can say that PostgreSQL increased the database possibilities within the company.

I have a dream that a database could import data safely and securely from other databases without errors and by using a GUI to help migrate the data. 

I've been using it for years.

We have had no issues with the deployment.

There have been no performance issues.

It's been able to scale for our needs.

In my last company, we had been using Access. We changed to PostgreSQL as we needed something more robust and usable. This was provided by PostgreSQL which at the time was the perfect solution for what we needed.

PostgreSQL is a perfect database to be used by small to mid-sized companies. Many years ago when I worked with medium companies I would have given it a 10/10 but as the database community has grown, it has decreased.

PostgreSQL is the only open source and multi-functional database solution out in the market today. I have used it to replace Oracle (RDBMS) up to MongoDB (Document DB). Postgres has very rich SQL and NoSQL features that gives it a special place in database industry. It’s easy configure and manage features helped to increase adoption in last decade or so.

PostgreSQL is the most flexible database I have worked in my career. For example, when I need geographical data processing for my application, I can use PostGIS. It is the best GIS solution out in the market, by installing extension the extension onto the database. Additionally, PostgreSQL's full text search functionality helped a quite a number of times to avoid introducing another system for text search and use PostgreSQL.

PostgreSQL has introduced number of new features to achieve out of the box multi-master replication and reach JSONB features, horizontal and vertical scalability and parallelization features. I’d like to see them to be production ready. As the number of users of application grows, the multi-master replication will helpful to replicate systems across the continents. We have started using JSONB in number of application, I would like to see some extended features to make JSONB data type more reachable. The horizontal/vertical scalability & parallelization features will help our big data analytics processes faster to improve application response time.

I've used it for approximately 10 years.

I have experience working with over dozen of database and datastores in production environments but PostgreSQL has been the most stable database I have worked so far.

It is missing some key scalability features such as sharding and automatic failover, but the Postgres developers are working on adding these features.

Postgres community is very thriving and Postgres ecosystem is very strong. The product is open source but it has the best documentation and readable code among other open source products. The turnaround time for logged bug is much faster than some of the commercial vendor’s support team. Additionally, there are a number of PostgreSQL professional support companies in the US and all over world.

I used to be an Oracle DBA over decade ago. I have used over dozen of database solutions ranging from MySQL to MongoDB in the distributed production environments but Postgres provides superior features but not limited to; extendibility, performance, scalability, analytics queries.

PostgreSQL is easy to setup compare to any other commercial RDBMS out there in market. It is easy to install and configure.

Postgres has great documentation and various open source tools available for maintenance. However, it is recommended to work with Postgres consulting services companies to expedite design and implementation.

PostgreSQL is truly open source database system so the licensing cost is zero. If you are migrating from any commercial database system, you are saving licensing and recurring support costs.

If you don’t have experience with PostgreSQL, I recommend to attend some of the local PostgreSQL user group meetups and/or conferences to learn how it is being used. If you need help discussing about the solution, you can reach to any of the Postgres consulting services company.

• Easy to use
• Vastl documentation
• Tough product

We used it from scratch of the organization. It helped a lot since we could improve our hardware, and we upgraded the Heroku plan as we grew.

It could be easier to perform some fragmentation in the database. It's possible, but still a hard job.

I've used it for about three years. Currently we use PostgreSQL provided by Heroku and AWS. On Heroku we use a premium 6 plan with v9.4, and on AWS RDS the version is also 9.4.

The biggest problem we found so far is not in the product exactly, it's in the service provided by Heroku. Heroku locks us in hiding some features that would make a lot easier moving to another PostgreSQL provider.

We have had no issues with the stability.

We have had no issues scaling it for our needs.

7/10

7/10

I used other solutions in other companies I've worked for before. When I arrived at my current company they were already using PostgreSQL.

I wasn't involved in the setup as it was already in place when I joined.

We implemented it through a vendor as using this kind of service is easy and fast to get started. You don't need experts, and you can keep concentrating on your core business. However, when you grow the costs grow, and as in our case, it might be hard to leave the vendor.

It does what it's supposed to do, as simple as that. We don't regret any choosing this solution.

• Security
• HA and DR
• Performance
• Maintenance

I worked as a consultant/trainer. I have a few installations of Dev/Test in my VMs, and I don't have anything in the production installation in our organization.

It's not very user friendly, as it is open source and has no immediate support. You can download the Enterprise version of Postgres that is a GUI installation and also have a support contract.

I've been using it for five to six years. I did the PostgreSQL DBA’s training and led the implementation and data migration projects.

We also use the EDB Postgres Plus Advance Server v9.3 (EnterpriseDB). We use it to evaluate the Database migration from Oracle to Postgres. The data level migration was successful but for objects, and at the security level, you have to fix issues manually.

We've had no issues but setting up the replication, security, and login is different from other databases.

We've had no issues with the stability.

There have been no issues with scaling it for our needs.

As mentioned earlier, there's no support contract for open source but with EDB (EnterpriseDB) you have the open to purchase the support contract. I don’t have any experience with EnterpriseDB support.

It's straightforward, as it's an open source product.

We did it in-house.

As it's open source the ROI is quick.

The core product is free but you have to pay for third-party utilities / plugins and support.

I have evaluated MySQL and Ingres previously and then PostgreSQL. My personal choice is PostgreSQL. I also worked on a migration project from Ingres to Oracle.

• Positive - 100% free as it's open source
• Negative - it's hard to find expertise

If you are planning to migrate an existing environment, please go through with the full UAT cycle at data, connectivity, objects and apps level.

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.