PostgreSQL vs Percona Server Comparison

It's relatively quick and reliable. We have used a PostgreSQL database for one of our systems for years and have never had a single problem.

The pgAdmin GUI seems a bit clunky to me. I much prefer the MS SQL Server Management Studio interface for SQL server.

Postgresql is friendly to the web developer learners, small projects

this database is not as powerful as RDBMS like oracle and sql server

This is very easy to use and manages. Easy to handle JSON data type and having lots of data type available. Table partitions available for increasing performance.

Creating store procedure are still very complex and not good as compare to sql server.

Cost saving was the main benefit. We switched for the cost saving and also to stay in synch with our vendor Ellucian.

The transition period was challenging. In particular, we needed to bring on a temporary staff member to help rewrite our 1000+ reports and dashboards from the Microsoft SQL Server language to PostgreSQL. We used the free (unrelated) tool from SQLines to help with this task: https://sqlines.com/sql-server-to-postgresql. I wish the PGAdmin software had a better built-in search feature, but otherwise it seems to have all the same functionality as SQL Server Management Studio.

PostgreSQL is a great and powerful database system, used in the management of object-related databases, bringing great performances on concurrency, transactions, and schema controls. Furthermore, PostgreSQL keeps focussing on the data secure through the different kind of authentications and access control process. Moreover, PostgreSQL is an open-source license, being very convenient for any company, and any professional developments, counting with complete documentation and community support.

PostgreSQL has proved to be a great tool, having a great performance on hardy scenarios. However, when is used on a huge amount of object-related requests, the server could show lag issues if the database isn't properly normalized by the developers or database manager or if you have a very low spec server.

I have not used the software directly but have used along with QlikSense. Its easy to use and being experienced with other relational databases, it was easy to configure and use.

I feel that it it slower than other counterparts like mysql/ sql server. could be a drawback of being a open source software

very fast open source database, represent very good solution for entreprise especially it is free to use and give a good performance

lack some advanced feature that exist in the other database like SQL Server and Oracle to work in some field like BI and AI

Postgre help user to manage data with supporting all Basic need s of relational database management system.

It's syntax is almost same compare to other SQL server but require most attention like double quotes are required with table and field names.

Easy to use and scalable Open Source Database. Good indexing and search features, plus with json support you can easily make tables extendable and adaptable without schema changes.

Indexes aren't as quick on json fields, but are amazing for optimising standard fields. Importing and exporting data isn't quite as easy as SQL Server.

It support the JSON. With Citus, an open source extension to PostgreSQL, it's now easy to scale out PostgreSQL across multiple nodes and intelligently distribute transactions and SQL queries to get massive parallelism, as well as a much bigger compute, memory, and disk footprint for the database.

Till have not found anything, except one thing. Sometimes it takes time to run the query. Don't know whether it's because of PostgreSQL or server.

You can have a database with high performance, besides it is an open source technology that is common use with Ruby on Rails, Python or .NET Core

You need to have some experience to implement it in a production environment or linux server, generally the most common mistake is handle the users.

Relatively small memory use, good performance and easy to learn and use. Good price for the package.

The chance to become private like Mysql and others. It can have a better customer support, the server runs on Linux which is not easy for some people.

PostgreSQL is a robust database that provides highly scalable value, offers superior performance to the options presented as their competitors specially for complex queries, provides flexible data types ,it have many extensions one of them is postgis that adds support for geographic objects.

Hard learning curve, a lot of GUI controllers are buggy and that is very clear when working on multiple server versions (Backups & restore), the documentation is a bit messy

PostgreSQL has several advantages. It is lightweight and reliable. Search filters are very easy to understand. People who know the basics of the SQL language can do several queries, since PostgreSQL assembles selects. I can change it within the table itself, so I don't need to do the update command. On top of that, it's free and open source!

Sometimes the connection to the database drops (internal server error 500), and it is necessary to connect again. When the query has many records, the data return is slow. They are the only negative points of this tool.

This DB server has a powerfull set of functions that has permitted to our DB Admin to generate more efficient reads and writes on it. The fact of having this kind of DBMS available on OpenSource is very good for organizations that needs to save some money in IT platform

According with us, configuration of PostgeSQL may result complicated, because of this is an advanced DBMS. Interfaces to manage are not simple, at least for me.

It has a clean interface and does not tries to get an attractive UI for you. It has very less query time. It provides a good architecture for code first approach projects. We set it up on Linux and it does behaves pretty nice on it. We get to see what what we need to see while querying. It is quiet easy to edit the datatypes and design your schema. Also it provides some nice mining tools which can operate on our data. And the best thing about it is source code availability. We can do whatever we want.

It is slow for small database sizes but the issue erodes with database size increase. Also it has different syntax which might look complex to some.

PostgreSQL is great for beginners as well as advanced users. It is designed to make SQL and querying more simpler and user friendly.

While PostGreSQL is great for being the most user friendly, it can also be a drag. PostGreSQl has different syntax as compared to other SQL databases and hosts. This can lead to someone messing up when going across different systems.

I like PostgreSQL for different reasons: - It has flexible implementation options. - Large volume databases can be stored. - It is possible to have multiple databases on a single server and have different configurations for them. - PostgreSQL is completely free. - Its base language is SQL, making it very easy to manipulate. - It has excellent administration toolkits.

I dislike PostgreSQL for different reasons: - I don't like that the more detailed documentation is only available in English. - It has a high CPU consumption.

PostgreSQL has a wide support of server operating system e.g. windows, UNIX, Solaris, Linux, FreeBSD, Open BSD and OS X. Large support of APIs like ADO.NET, JDBC, ODBC and native C library which makes it easy to connect with any module. Good support of programming languages as well i.e. C, C++, JAVA, .NET, PHP and Python.

Wide support from community but some times its difficult to track any issue and get support. Reading speed is bit low as compared to other DBMS. Documentation is only available in English.

PostgreSQL is a full featured SQL server solution. it is free and open-source, PostgreSQL can be installed on many different platform like Linux, Windows, macOS and other. being open-source if has lots of contribute tools from the open-source community providing wide range solutions, PostgreSQL is also available in the cloud from all the major providers.

Management is less comfortable and some settings needs to be done in PostgreSQL configuration files, also database schema management tool is not so comfortable, but you can use 3rd party tools for that also

PostgreSQL allows to control high concurrency, offering security by domain definitions, who can access the database server, the backup copies of the database can be made completely or only a table, according to the request, restorations and tasks maintenance, in addition to replicate in case of disasters. It also allows to activate triggers to execute in tables or views in special cases or eventualities. It...

Read more

There is no online or telephone support. Only official forums are available where users expose their doubts that other users of the community respond to, ademas it consumes many resources

Very strong consistency and reliability Feature set is growing rapidly Very fast and efficient Very developer friendly Very extensible

There are lots and lots of configuration options and the defaults aren't right for modern hardware

is an object-relational database which allows it to be compatible with user-defined objects, this makes postgresSQL a flexible and robust database, it supports an extensive amount of data types among them, numeric, comma types floating, array, among many more, allows to create a wide functionality through its trigger system (triggers). It has a support for distributed transactions which supports the integration in a distributed system consisting of several resources such as a PostgreSQL database, another Oracle, an IBM MQ JMS message queue and an SAP ERP managed by an application server.

the transactions abort completely if a fault is found during its execution, which can cause the loss of information, it is slow in the insertions and updates since it has intersection headers, the object orientation support is a simple extension that offers benefits such as inheritance, not full support. The current versions of PostgreSQL have a serious security problem that will be fixed in the next versions of the product.

Since it was developed to comply with SQL standards, there are no problems migrating from other RDBMS. I think the popularity of MySQL as an RDBMS is split in two, but PostgreSQL does not have the following MySQL keylogging problem, so it can be said that it is an RDBMS with little custom. We recommend PostgreSQL as the first choice for RDBMS unless otherwise specified because it works stably and can support real operations. When a small business is a customer's system project, the RDBMS license fee is often too high to pay. In such cases, customers will be happy to propose PostgreSQL, which is stable, reliable, and free to use. Unless it is a situation that requires a paid database, I think PostgreSQL is sufficient. It is not inferior to the function.

When you are looking for something you want to look up in a manual, it is often difficult to find it and, in the end, you often consult blog articles written by experts instead of the manual. I want the structure of the manual to be easy to understand.

PostgreSQL is one of the best from the range of DBMS i used in my career. Features like Stored Procedures is one of the reason i prefer this tool. It helps me take off a huge amount of workload from the API server as same data need to format differently for different APIs. Along with it the availability of builtin functions like JSON functions, Regex Functions etc helps a lot in the data processing field. Connectors support for various languages is one of the main reason for using this tool. Connection Pooling helps me execute multiple queries without slowing the system and losing any data.

It is not suitable for beginners. Designing a efficient and effective Database workflow need a skilled DB Admin so a beginner need some time to get to familiar with the system. Another drawback is its management tool pgAdmin 4. Its a disaster compare to pgAdmin 3. It is a web App and lags a lot. I face problems in multitasking in version 4 that is not the case with version 3. I Hope someday somebody provide backward compatibility of PostgreSQL 10+ with pgAdmin 3.