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.

Common Table Expressions(CTEs). It's powerfull, easy to write and read and very flexible.

JSONB (Binary JSON storage), because I can have both relational and non-relation data storage at the same time with this data type. In addition, by using Generalized Inverted Indexes (GIN) it supports fast lookups and simple expression search queries.

Replication is not yet as well implemented as in MySQL.

I've been using it for one year and five months

There are some issues around different OS, but not a big problem.

There are some issues around different OS, but not a big problem.

There are some issues around different OS, but not a big problem.

The documentation could be written better, but there is a huge community committed to help.

I used MySQL, but for safety and consistency issues, I moved to PostgreSQL

Straightforward, easy and intuitive.

In a vendor team, we develop products for different segments stores. In the implementation, keep in mind the configurations and platforms that are available, it certainly will save time and avoid potential problems.

Currently this is one of the best solutions on the market. It is a tool without cost, powerful, easy to learn and with a large active community.

It's reliability is key.

It allows us to deploy test functionality on a very simple normal computer and not on a server.

I'd like to have NoSQL available in this version. It is available in the latest one.

I've been using it for six years.

We had no issues with the deployment.

I've had no stability issues.

It scaled for our needs.

8/10

I switched as I needed to increase the volume of data.

It was a bit complex to setup, although I think this was due to ignorance on the project.

We did it in-house, but only to test different databases.

Use it, to change the default database, it's a good option.

• Flexible stored procedures and external functions
• WITH clauses
• Partitioning
• Large open-source extensions, modules and software helpers eco-system

The documentation is very well written and detailed, it helps to implement the right features for your needs in a timely manner.

Parallel processing of queries.

I've used it for 12 years.

There's been no issues deploying it.

The product always worked as described.

We've had no issues scaling it.

There is no tech support, however there is a lot of information available in forums or sites like serverfault.com.

I used MySQL. PostgreSQL syntax is much clearer and consistent, and its stored procedures are powerful and fast. The documentation is also much better and of more help.

On Debian, the provided packages are very easy to install and provide automatic updates. On Mac OS X, EnterpriseDB provides packages that work very well but as not as well integrated than in Debian.

I implemented in-house. PostgreSQL databases needs some maintenance but that can be easily automated by a skilled administrator.

PostgreSQL is free and open source.

Read the documentation.

The h-stores are very powerful for handling collections of key-value pairs. The query syntax and functions are well documented and easy to use.

PostgreSQL is a powerful and open source database, which is central all data processing.

We'd like to be able to start using JSON objects for easy code representation. This feature is available in v10.4.

I've been using it for eight years.

We've had no issues with the deployment.

There have been no stability issues.

It's been able to scale for our needs.

I use online documentation, which met my needs.

We were using version 8 before, and also an earlier Oracle instance. We chose the product because it is powerful, well documented, and open source.

I did not set up the actual installation. I did set up the schema, tables, foreign keys, etc. That was straightforward in that it was well documented.

In house. You do need someone that knows PostgreSQL or that can spend time learning about the product.

It's open source. ROI is a matter of time.

The challenge with this product would be finding the IT resource that can implement the product.

Many supported features out of box like fulltext search, partitioning, easy replication - slony, pgpool-II and streaming wal and additional features such as JSON, XML, arrays in columns, and many extensions for it as PostGIS.

I'm working as architect for a custom software development company and we are using Microsoft SQL Server, Oracle DB and PostgreSQL as our main databases, in recent years Postgre is offering more and more useful features which we can use. For its open source model and very good documentation is very easy to optimize queries within bigger databases (100GB). Also its free and its lowering price of our solution so we can (and we are) address smaller customer.

The biggest issue that we are having is upgrading and moving databases between servers and versions. Restoring database is slow with pg_restore because indexes are need to be rebuilt. What I'm missing is a query profiler similar to what is in Microsoft SQL Server. PgAdmin should also be easier to use for beginner users.

We have been using PostgreSQL for about 10 years.

After many years of usage we are not experiencing any unusual problems with PostgreSQL.

After many years of usage we are not experiencing any unusual problems with PostgreSQL.

After many years of usage we are not experiencing any unusual problems with PostgreSQL.

We are not using customer service or technical support.

We are not using customer service or technical support.

We are using PostgreSQL for new installations and new versions of our solutions where it's possible, and the customer does not require a specific SQL server. Nowadays it's covering all of our needs.

Depends, for basic setup, it is quite straightforward but for more advanced features (like WAL streaming and hash indexes) it is a bit harder during the first few days because of a lack of documentation and experience.

We did it in-house.

There are no license fees for getting PostgreSQL and we don't yet have experience with paid support such as from EnterpriseDB, but we never needed it.

Your first investment is only in people working with PostgreSQL, and it is the same as with Microsoft SQL Server, but less than with Oracle. Hardware costs are lower for PostgreSQL and Oracle but those are not significant.

My advice is to read documentation thoroughly and don't be afraid to look into source code. A great source is https://momjian.us/main/presentations/overview.html

Speed and price, it’s fast and reliable, and free.

Due to budget restraints procuring software is always an issue, and mainly production systems are well maintained. However development systems are not usually so well off. As PostgreSQL is free, this enables us to develop applications without having to think about budgets, and give us greater flexibility. There is still reluctance by business to accept free ‘Open Source’ software, but proof of concept development can be achieved at no to low cost.

Simplicity in design and improvement with programming languages like PHP.

I've used it for four years.

In development it’s super sensitive with comma, quotations, and letter cases. It should not be. If we use uppercase sometimes it works and sometime not, and its need to be single quote sometimes but sometimes double quote.

There have been no issues with the stability.

We've had no issues with scaling it.

I've never used customer services, but it needs a better documentation.

We use both MySQL & PostgreSQL, some applications have better compatibility or built in tools, this decides which database we use.

It's straightforward.

So far we have not had any issues with this database are we are using this in development and production systems.

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.