PostgreSQL Reviews

PostgreSQL is probably the most SQL-standard-compliant RDBMS on the market. It also goes way beyond standard relational paradigm combining key-value stores, arrays, and columnar stores into a single engine. With the introduction of Foreign Data Wrappers it also enables connecting various different data sources to the database, so it's possible to have, for example, a CSV file-backed foreign tables or to import a MSSQL schema into PostgreSQL.

PostgreSQL allows us to have a single database engine used for OLTP and OLAP workloads, for relational and non-relational data. Its robust and battlefield-proven replication makes us sleep better.

Logical replication would be a major improvement and it's already being worked on. It'll enable true multi-master replication and active-active setups. More OLAP-related performance improvements are also on the way with parallel query processing and parallel background workers being to most significant ones.

v9.5 came out at the end of last year, but I've used previous versions as well. At the moment all the new deployments I'm installing are based on 9.5 since developers are very keen to adopt it and administering it is a breeze.

PostgreSQL is the most advanced open source database in the world and therefore is considered by some to be complicated, but it's not. Deployment is easily done in major GNU/Linux distros.

PostgreSQL is rock-solid-stable, once set up and configured correctly it just continues to work.

There are plenty of clustering solution/ideas that enable horizontal scalability.

PostgreSQL has a very active community and in most cases that's enough of a support. There are a few commercially focused companies, and a lot of freelance consultants [with the writer of this amongst them]. Bugs are always resolved in a timely manner.

If you can type "apt-get install postgresql", you can consider yourself expert in installing PostgreSQL.

While the initial setup is easily done by any member of Ops team, it's important to have a dedicated DBA resource to take care of it. PostgreSQL has superb documentation, it is probably the best documented IT project. We have an in-house team and almost never have to use external consultants. PostgreSQL is very much different from the most popular RDBMS, so it's best to seek a PostgreSQL-focused professional for the in-house team.

I work with few other RDBMSs, but nothing compares to PostgreSQL when it comes to ACID and SQL compliance, stability and the ease of administration.

Get a dedicated, PostgreSQL-focused resource, it's hard to convert DBAs with background in other denominations.

There are many valuable features, but the most valuable to me are Windows functions, Python scripting, and the fact it has a good PGSQL language.

It provides standardization on the database and related skills.

Parallelization and some connection to analytics is needed.

We had no deployment issues.

The product is quite stable.

It has the ability to scale up into products like Redshift.

The online manual is superb.

It's very easy, and you only need to familiarize yourself with its file structure. Sometimes you need to write your own plugin, so sometimes it is better to have it implemented by a vendor.

It's free as it's open source.

It is a superb database. What keeps it from being 10/10 is a lack of analytics specific optimizations.

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.

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

The product is free, which is a huge benefit. There are options to create clusters and maintenance on the databases is easy and fast. The management studio with product is create and intuitive.

We used this product for applications which require a database. Since MS SQL Express has limitations and regular MS SQL requires pricey licensing, PostgreSQL was an easy choice. The deployment is quick and easy and works with very little configuration, if any at all.

The commands for PostgreSQL work, but are behind the curve compared to Microsoft SQL and MySQL. Adding additional functionality to be move comparative to Microsoft SQL would be a nice to have. For experienced users needing to make configuration changes, it is straightforward, but for users who are new to PostgreSQL they need some help working within the config files, a GUI for config may help with this.

We've been using it for four years.

I've never had any issues performing multiple deployment.

There have been no issues with the stability.

We have had no issues scaling it.

I have never had to contact support, but the documentation they have is very good and extremely detailed.

We use Microsoft SQL (all versions), MySQL, PostgreSQL, SQLite, etc. We use PostgreSQL when the application supports it and where it makes more economic sense to use it.

Following the setup documentation was extremely straightforward and simple to follow. We have no issues with the install, config or operation of the application.

We did an in-house implementation for PostgreSQL. The documentation made it easy to do and was very simple to follow.

PostgreSQL is free to use.

Ensure its a good fit for the application you are using and integration you may have planned. Review all documentation prior to moving forward and always test the new versions before just cutting over.

By far indexes is the most useful and robust feature. Also, the query optimization engine is simply great. It is very complete, clear and useful documentation, forums and diverse information channels.

Most of the enterprise I have worked has been startups and small to medium software industry and data analysis. One of the most improvement it is not in the mean time but in the middle to long time. At first sight it seems to an overkill implement a product as PostgreSql for small projects; even managers and investors tend to put some resistance to it. Then, as soon as projects start scaling and data set increase in size, concurrency, consistency and data types, is were you think PostgreSQL was one of your "hit" on the project design, time give you lot of credits.

I think that data types that decrease the breach against NoSql Databases will be the next steps. I am not talking about changing to a pure NoSql DB but to some features that will face the big change in data analysis and maintenance that that DB are facing nowadays. Also tools for distributed replication and clusters should be more researched and improved; anyway nowadays there is some of them.

I have been using PostgreSql since University where I teached students some DB theory concepts. The course was focused on indexing and benchmarking. Also I use it on software industry, as a DB manager, designer and operator; common tools were PL/pgSQl, indexing and tuning; using about 3.0M per month DB tuples inserted and about 500tps on peak points. Finally I use it on personal projects, for small data sets (~1.000).

We have had no issues with the deployment.

I have faced just a few issues working with PostgreSql, one of them was specifically on Hash Index (see as example http://www.postgresql.org/docs/9.2/static/sql-createindex.html.

We have had no issues scaling it for our needs.

Most of the great value of PostgreSQL is the variety of technical support you can find Consulting, lots of forums, and big communities who have been using and documenting PostgreSQL for a long time. I have never faced a problem or question that couldn't be solved using these channels.

I have worked with MySQL and Oracle solutions. Against MySQL, performance is the big difference. PostgreSQL is far more robust and mature than MySQL, especially when you think about keys and indexes. Against other databases, such as Oracle, the easy installation steps of PostgreSQL is the best difference for me.

I have faced a few issues while installing it and configuring it; most of them related to incompatibility while using old Ubuntu Linux versions.

I have always implemented it in-house, and as all solutions for everything on vast areas, is highly recommended read guides on how to install it.

ROI is by far fair enough for startups and enterprise projects that are expecting a big grow in the mean time.

PostgreSQL license is a fair enough for small to medium size business solutions.

Just read the comparisons between different database engines, and read some documentation so you can exploit most of the powerful tools and functions it has.

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.