PostgreSQL Reviews

It allows people to use whatever multiple procedural language they are trained in, such as Java, Python, Pearl, or C and it is not limited to PL/SQL or PGSQL. Also, I love the PostGIS extension and I do not know of any other product like this.

I can integrate solutions quicker than with other RDBMS'. At the same time, I am able to keep an RDBMS' integrity, robustness, and High Availability which is the most important thing for all my production environments.

It is lacking some GUI admin tools and it would be nice if more could be developed by the community.

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.

It's the best in my opinion because have now found what I need to enable me to quickly deploy into my production environment. Go to a professional and ask for your needs, maybe you will surprise with a variety of solutions that you never thought existed.

• Very good indexing solutions, especially for arrays and text search on large quantities.
• Very good behavior on large databases (>800GB) and large tables.
• Datatypes - support for vectors, XML, JSON, UUID and the functions and operators for them are very useful.
• Programming languages - I deeply appreciate the extensibility of the server to allow more than one language for scripting functions. We mostly use PL/SQL, but recently I've tried PL/v8 and was astonishing to see that it works.
• Execute with Query Parameters is a big plus for us as there are no type conversions needed to run dynamic queries reducing the run time by approximately 25%
• There is a huge amount of community interest in developing and supporting the product.

All of our BI needs are implemented using PostgreSQL functions. Our tools are designed in such a way that the BI is implemented as much as possible through our database. We need a lot of flexibility to extend the BI logic on a specific installation.

Synchronous replication is needed, and although I have only searched the web for a couple of hours the only solutions I could find were at the application level of the database.

XML and JSON manipulation functions need to be improved as for some applications we need to add new elements to these "structures". To do this with JSON I currently use a PL/v8 extension.

We have had no issues with the deployment.

There have been no performance issues.

It's been able to scale for our needs.

Try it out! Sometimes, due to the high degree of configurability and extensibility, you might see some issues arise, but it's not that difficult to figure out what's happening. You will definitely be amazed by the SQL features and extensibility.

PostgreSQL has excellent support for many programming languages. We've been able to integrate it with Java, PHP, Perl and .NET without any issues. 

Replication is also working pretty good in a master to read only replica setup in AWS. 

We've been able to cut costs on databases over our previous solution with Microsoft SQL Server and migrate many applications into Amazon web services. Performance has been decent. 

By far the biggest limitations are in replication support. A native master to master replication option would make things much easier as we're in need of an easier method to load balance traffic with Spring Data.  

PostgreSQL is slower than MySQL with insert performance. While using COPY can make an application fast, we often use ORMs which cannot benefit from this. 

9.4 seemed to have some regressions with the query planner and multi table joins are slower than in previous versions. 

I've been using PostgreSQL for 5 years.

Finding the right configuration to balance performance and connections was a little challenging in our setup. 

We've encountered some CPU bound scalability issues with multi table joins (3-4) and the query planner seems to ignore indexes at times. 

Initially applications at my current employer used Microsoft SQL Server. The cost for licensing/maintaining windows systems was more than we liked. PostgreSQL has offered similar performance for our workloads with lower cost. 

It has the same features as paid-for databases such as Oracle and SyBase.

It's saved us money as it's free.

Eliminate the transaction wraparound possibility. If transaction wraparound occurs it can be a major problem.

I've used it for two years.

There were no issues deploying it for us.

We've experienced no issues with performance.

There have been no issues scaling it for our needs.

There is none available as it's a community driven solution.

It's simple to get it up and running.

We did it in-house.

We tested a big portion of our online API product using SoapUI and it was very fast and efficient.

Use this product for simple needs if you do not have PostgreSQL expertise. If you have PostgreSQL expertise you can run your business off PostgreSQL.

It has allowed us to run a Scada database, which reads data every 2 minutes. It does it in a very smooth way.

I would like to have better support for real-time applications.

I've been using it for three years.

No at the time. Our application fits very well.

No at the time. Our application fits very well.

No at the time. Our application fits very well.

I have used online free help.

MySQL but not in the same scale.

We implemented it in-house.

Analyze very carefully the hardware requirements.

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.

PostGres is a fantastic modern RDBMS and its open nature allows you to get as low level as you need. You can define functionality, you can call from SQL and dig deep into the query planner with it's excellent explain functionality. The true open community is loaded with helpful people who believe in OSS. Every feature in PG is first, present, but secondly mature and just works. You may have bugs in your code but PGSQL will never be the cause of it.

It drives our enterprise architecture we are building.

The only thing that could potentially be improved is PGAdmin3, the DB Client that's has not been updated in quite a while. PostGres keeps ahead of the curve on it's feature set. For instance the new JSON column that's come out recently to provide nosql functionality that has been benchmarked to outperform mongo.

We had no deployment issues.

The product is quite stable, and provides awesome performance.

There's been no issues with scaling it for our needs.

It has a great support community.

I started with this product.

It's very straightforward initial configuration if you start with your distro packeges.

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's go good reliability and is very compliant with standards. If you are installing relational DB you likely know how to use one. If you're not familiar with RDBMS's make sure you look into and use the features of the DB like views etc. They all serve a purpose and will improve your development if leveraged properly.Huge feature set.

• Stability
• Standard SQL for ease of development with pre-existing knowledge

Postgres is for our systems a very solid database, easy to use in development and easy also to manage in production environment, and that's valuable because in the end it cuts a lot of costs (also during the upgrading processes).

The Postgres team is already doing an amazing job in putting in features to ease the life of developers and sys admins, such as JSON support and database replication.

A feature that is still a work in progress and it would be nice to have would be native master-master replication, we don't have a need for it right now but it's something that should be addressed in the future.

I've used it for five years.

There have been no issues with the deployment.

We have had no stability issues.

It has been able to scale it for our needs.

I've had no need to use any.

I've had no need to use any.

I used MySQL and Oracle previously, PostgreSQL is open source and fully ACID and SQL standard

It was easy.

We deployed it in-house.

It's a great database engine that is easy to use, powerful, and scalable.