PostgreSQL Reviews

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.

• Stability
• Performance
• Ease of administration

It is a world class, performer, a scalable database that is free and open source.

At the fringes, you can have locking problems that can cause unacceptable pause, but that's really a factor of database design, and the limitations of relational databases as a technology than a particular issue with PostgreSQL

I've been using different versions of PostgreSQL for the past eight years.

There was other a foreseen issues with pushing it to the edge.

It's a very stable product.

It's easily scalable.

The amount of community support for the solution is good.

We've got experience with a number of RDBMS, but PostgreSQL has always stuck out to be the most economical and sensible product. That being said, we do have instances of Maria, and various NoSQL's floating around.

We did it in-house.

It is an open source solution and that is a database engine very powerful. Besides it is highly configurable. I prefer PostgreSQL over MySQL or MariaDB because you can create several databases with many schemas and create roles like owners, and not only grants over tables, or procedures. On the other hand its very easy and intuitive to administrate the connections by hosts, databases, and roles.

PostgreSQL is a powerful dateserver although not like Oracle. So we can make many developments in a cheaper way with high availability. Besides, its very useful tool for debugging with a soft learning curve.

It needs to be able to cluster. We have implemented the high availability with a master-slave mode and one host in only read mode. This is the worst feature of this product and the quality sign of Oracle.

I have been using PostgreSQL server for three years.

The upgrade from v8.4 to v9.3 was a little hard, but this was executed finally well.

We had no issues with the stability.

We've had no issues with scaling it for our needs.

I've not had to contact them.

I use MySQL, MariaDB, and Oracle. I chose PostgreSQL or others depending of the project. For Java implementations I prefer PostgreSQL, and for PHP development, I prefer MySQL or MariaDB,

In my opinion the initial setup is easier than MySQL because it is more intuitive, but you must to edit a couple of config files, and become more aware of the entire infrastructure.

It's open source code, so you get it for free and need to contribute to debugging errors and improving the code.

Be patient! Like most open source tools, this requires commitment and a little knowledge.

* pg_hba.conf

* A fragment from postgresql.conf

* How to access to database-server using psql client, and create a database

Create a user/role and be owner for a database. We can list all databases with "\l".

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.