PostgreSQL Reviews & Product Details - Page 63

During my 3-4 years of being exposed to PostgreSQL in a professional environment, everything being transactional was quite good, partial indexes are awesome and helped me optimize things quite a bit for the application at Vonage that was running on EnterpriseDB at the time (2006-2007). At the time, the feature set was a bit better than MySQL, which was my primary expertise. We were trying to substitute Oracle with PostgreSQL for a specific task we had. There was also a rather large at the time deployment of snort logging into postgres (500 gigs or so before it started falling over)

I liked the way backups and restores were described for getting a snapshot in time, as in "backup the data even if it's changin, then backup the log files, with some function calls here and there" Review collected by and hosted on G2.com.

Replication, at least in 2006-2007 was slony and log-shipping. Slony would fail to create new replicas after about 100 gigs on somewhat serious enterprise hardware due to it recreating the database via a pg_dump method which obviously stops working after certain level of data size is reached. Was a pretty bad time, 1/5 stars, would not repeat.

Some of the commands were just dowright tedious.

processlist ? some obscure table, or function call.

kill a process ? yet another obscure function call

see all the tables and sequences ? \d, naturally

just the table ? \dt, everybody knows that

show create table, doesn't exist - have to break into pg_dump

show create function/trigger/view/event/etc - nope, pg_dump for you

Not sure if this is the same way still, but replication is the major win for MySQL currently, it's easy to have replicas, all the information and monitoring is easy to retrieve. Review collected by and hosted on G2.com.

I like standards-compliance of PostgreSQL best. As we know, PostgreSQL follows the majority of the SQL2011 standard, is ACID-compliant and transactional using multiversion concurrency control (MVCC); has updateable views and materialized views, triggers, foreign keys; supports functions and stored procedures, and other expandability, and has a large number of extensions written by third parties. It is easy to not only learn how things works but also easy to modify it according to your requirement. I often wrote queries and tested them on it when I was still a student to learn RDBMS. After I worked, I also referred to it when I am not sure about the standard. Moreover, it has lots of add-on choices (for example, remote access module) for you to add and use. Review collected by and hosted on G2.com.

The things that I dislike most is its security setting. It is hard and difficult for beginners to write the conf file to make it work. I hope it could have an option of no-"security" so that we can skip it and focus on the major things. Review collected by and hosted on G2.com.

In mysql if your table does not have a primary key , the import button is not visible. In contrast to this postgresql allows you to make use of import data from a csv into a table even if the table does not contain primary key. Review collected by and hosted on G2.com.

the POSTGRESQL does not provide an interaction graphic user interface such as mysql in order to alter the table elements. In case of MYSQL if we can easily change a data type of any column of table using mysql workbench. However postgreSQL does not provide such interactive way to change the column datatype. Also in case if you want to alter a column type such as double to character then we have to explicitly write alter command to make the change Review collected by and hosted on G2.com.

easy to install, open source, active community, lightweight but powerful SQL database Review collected by and hosted on G2.com.

replication options are limited as well as a REST API interface is also lacking Review collected by and hosted on G2.com.

Easy to use, great performance, open-source Review collected by and hosted on G2.com.

Nothing really! Perhaps I would like it was more frequently used. Some companies force use to use MS SQL or MySQL and I always miss Postgres Review collected by and hosted on G2.com.

PostgreSQL is durable and fault-tolerant by design; great effort is taken by the developers to ensure reliability is maintained.

This cautious approach does not hinder development though; constant enhancements are delivered in every release, with new features generally arriving ahead of much more expensive commercial products.

With both community and commercial support, bug fixes and security issues (although rare) are always addressed quickly, and generally resolved far quicker than most commercial vendors.

With a wide selection of both free and commercial tools to accompany it, we are easily as productive if not more than we would be with a commercial offering.

Overall PostgreSQL has excellent speed, reliability and support of SQL standards; coupled with its "free forever" licensing, there is no risk of costly vendor lock-in. Review collected by and hosted on G2.com.

There's very little to dislike about PostgreSQL, and the "free forever" BSD style licensing means you've nothing to lose in trying it for prototyping you next project. I've no idea why anyone would use anything else. Review collected by and hosted on G2.com.

* Very popular amongst Ruby on Rails developers and as a greenhorn in the field of web development, it's popularity speaks volumes to the number of blog posts and tutorial guides. That alone is a winner in my book.

* Implements the SQL standard very well

* Includes support for "advanced" SQL stuff like window functions or common table expressions

* Supports lots of advanced data types, such as (multi-dimensional) arrays, user-defined types, and more

* Open-Source! Review collected by and hosted on G2.com.

* Documentation is confusion, many of PosgreSQL versions have overlapping variety but they do include a thorough description of the issue.

* Replication is not yet as well implemented as in MySQL

* Not as competitive in the OS support as MySQL, but this is trivial if you use a a rare OS or require widespread support: http://en.wikipedia.org/wiki/Comparison_of_relational_database_management_systems Review collected by and hosted on G2.com.

1. JSON, Array support

2. Unicode support.

3. CreateDB Privilege. Review collected by and hosted on G2.com.

Actually, I have nothing dislike on Postgresql. Review collected by and hosted on G2.com.

PostgreSQL is useful for local application development. It's quick and easy to set up and view tables. Helps that it is free. Review collected by and hosted on G2.com.

Sometimes the user interface can be very slow to respond, and the application may lock up under heavy load of large tables. Review collected by and hosted on G2.com.

The combination of PostgreSQL and PostGIS. It has been the foundation of our glacier mapping system for years, and has always been rock-solid and packed with features we need. Review collected by and hosted on G2.com.

I can think of no dislikes that would not apply to any other relational database system as well. Review collected by and hosted on G2.com.