PostgreSQL Reviews

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.

HStore is a data type in PostgreSQL database that gives the flexibility for storing sets of key/value pairs which is quite an awesome feature.

Slow count. As the number of rows exceed a couple million, the count query and queries which get to the depth of the data (like FTS) start taking too much time even with all the right indexes in place.

I've used it for two and a half years.

We use RDS Multi - AZ deployment which takes care of it all for us.

We've had no stability issues.

There have been no issues with scalability.

I've never had an issue with the product, and therefore never had to reach out.

We tried RethinkDB a couple of years back, and it was unstable at that time. Also, MySQL didn't have a JSON type back then. We switched to PostgreSQL and never looked back.

I do remember facing problems with the initial setup, but the overall documentation and SO answers has increased since then. New users face much less problem now. But there is still scope for improvement here.

I'd recommend reading Greg Smith's PostgreSQL High Performance.

The reason why I started with PostgreSQL database was the (geo)spatial support. GIS software, such as Quantum GIS (QGIS) or PostGIS, is a good example of where you are able to use this feature. Nowadays, the solution is on a competitive level to other commercial software solutions, especially for small companies.

PostgreSQL (geo)spatial support is stable, and you can add, remove, and edit all standardized GIS features. Thanks to projects such as EDB, Bitnami etc., PostgreSQL can be used by people on pure user level, without deep knowledge of OS administration, programming.

There is room to improve some user friendly properties such as input and output tools, some people may find interesting to implement MERGE as a SQL command. I am looking forward to trying UPSERT and would like to test some analytic functions definitely.

I've been using v9.4 for a half year. I also have experience with previous versions of PostgreSQL. Currently we have PostgreSQL 9.4.7 on Fedora Server 23 and PostgreSQL 9.4.5 packaged by EnterpriseDB (EDB) on Windows 10 Pro.

I had trouble with the reinstallation of EDB. If I have a previous version on my Windows PC, I have to take some steps to clean the registries and folders, then everything is OK.

If you are interested in you can find answers for troubleshooting. Many companies, I have mentioned above, are there for service and support. I didn’t find any big bug in the latest stable release over the last few months.

If you are interested in you can find answers for troubleshooting. Many companies, I have mentioned above, are there for service and support. I didn’t find any big bug in the latest stable release over the last few months.

I recommend Linux installation, but it is also possible to use Windows. With PostgreSQL you don't have to pay much money which is a good advantage. You have to take into account that you will spent some time finding out how to implement something or what is the right tool you have to use.

PostgreSQL is a long-lasting investment for people who like computers and don’t want to spent much money for database layer implementation.

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

JSON data support is most valuable to me as it saves design and maintenance time. It is a very safe and stable solution.

We are spending less time parsing API response and more time exploring data. We spend time understanding APIs and how to interact with them, If we can load responses directly to the database that saves many man hours for a project.

A better export facility which is GUI friendly would be an improvement. Also if we could export data from grid that would have been helpful.I have used HeidiSQL for MySQL which is very user friendly, pgAdmin III is not that helpful when it comes to different features we need to use like export,filtering and connections.

I've been using it for one year and am still exploring it.

We had no deployment issues.

We had no issues with the stability.

We had no issues scaling it.

I have worked with MySQL, Microsoft SQL, db2, and Oracle. We chose PostgreSQL for its JSON support as our APIs are sending JSON responses and PostgreSQL is like home for JSON. Choosing it has helped our cloud computing requirements a lot.

On Windows it's straightforward, but on Ubuntu, it was a bit complex when it came to database and tablespace division through PSQL.

We did it in-house.

If you are thinking of using PostgreSQL, all database names, table names and column names should be in small letters. PostgreSQL requires every capital letter to be quoted which makes life difficult for developer.