The EDB Postgres Advanced Server is an advanced deployment of the PostgreSQL relational database with greater features and Oracle compatibility, from EnterpriseDB headquartered in Bedford, Massachusetts.
N/A
PostgreSQL
Score 8.5 out of 10
N/A
PostgreSQL (alternately Postgres) is a free and open source object-relational database system boasting over 30 years of active development, reliability, feature robustness, and performance. It supports SQL and is designed to support various workloads flexibly.
We chose Postgres Plus Advanced Server because we had the finances to do so and needed the robust featureset, along with the power to optimize our performance and integrate with the development tools of our choosing. We audited a number of options, exploring potential solutions …
PPAS proved better for our customer's data-centric apps than Oracle in all but a few edge cases (encryption at rest and multi-TB database-tier backups) because it is simpler to install/maintain, runs nearly all Oracle-syntax SQL as well as ANSI SQL. PPAS has much more JSON …
First It's open source and it's cost-effective compared to other databases.PostgreSQL can be easily integrated with numerous platforms. It is well known and appreciated so relying on it as our system database can be easily accepted by our customers. And if your developing a …
For our use cases, PostgreSQL is just as feature rich as other options, costs less, and is simple to get up and running. There is also a plethora of documentation to support it which makes it a great option for a small scale startup without needing high levels of expertise to …
In this case, Postgres is preferred because it handles large data sets and requires fewer hardware resources than its competitor, MySQL. Compared to PostgreSQL, Microsoft products are excellent, but the installation process for MS SQL is lengthy. PostgreSQL has an advantage …
I've been using different databases for the past 20 years, solutions like MS SQL Server, MySQL, MariaDB, Interbase, Firebird, DB2, etc., and by using them I wasn't able to be neither close to the performance PostgreSQL deliver. Also, it is one of the most popular databases on …
Although the competition between the different databases is increasingly aggressive in the sense that they provide many improvements, new functionalities, compatibility with complementary components or environments, in some cases it requires that it be followed within the same …
We evaluated both PostgreSQL and MySQL, two popular open source relational databases. While they are very similar in most areas, PostgreSQL's reliability and performance won us over, plus it has much better support from cloud vendors we also work with.
Postgres stacks up just [fine] along the other big players in the RDBMS world. It's very popular for a reason. It's very close to mySQL in terms of cost and features - I'd pick either solution and be just as happy. Compared to Oracle it is a MUCH cheaper solution that is just …
A free corporate professional product. Who does not want to have such a thing, we hesitated because we did not know the product before and frankly we did not want it at first. But when we give it a chance, it has been running smoothly for years.
When we were originally evaluating Redshift we ran into some issue with dates. Either way, Postgres is a better choice than Redshift because it avoids vendor lockin. We ended up choosing Postgres over MySQL because it was easier at the time to get a hosted Postgres cluster up …
As I have been telling all along, PostgreSQL is much cheaper compared to the other RDBMS solutions. It has got better performance with some of the application services that we are using and is easy to maintain. Overall, we are satisfied migrating to PostgreSQL database clusters.
Much more mature and stable when compared to MySQL with features such as MVCC, complex subquery plans, ORDBMS, and NoSQL support. With Oracle retaining rights to MySQL its future as an open database is less secure and is no longer in the hands of the community. PostgreSQL also …
Its main characteristic is the integrity of the data. In addition, being free software, it has no costs associated with its license, which allows the number of installations to be scaled without problems.
The technical staff quickly learns about its installation, configuration …
Both Oracle and MS-SQL database option fell when we evaluated the effect on our overall solution cost to our customers. customer examine the overall cost of the solution they buy, selecting Oracle or MS-SQL would leave less money in our pockets. We are Linux based solutions and …
PostgrPostgreSQL as a transaction db engine against oracle and sql server works well. TPM wise compared to MySQL and MariaDB, on an evan scale. SQL function supports, far outweighs compared to MySQL and MariaDB. PG Extensions allow for flexibiltity and scalability. Allows …
We selected PostgreSQL due to the number of employees who have used it in the past. The data consistency guarantees. The multiple transaction isolation levels support.
PostgreSQL outperforms every other option. It is faster, more flexible, more reliable, easier to maintain, and more consistent in behaviour than any of the other offerings.
The main reason for select PostgreSQL against MS SQL Server Express edition is the necessity to use open-source platform, without any issues for licensing, client licensing, etc. etc, which is usually follows developers and project managers when they start to use products and …
SQL Server is an excellent product from Microsoft, it is a derivative from Sybase which originally developed the SQL Server form Unix and Linux, and Microsoft purchased it to migrate the DBMS to Windows Server. But the cycle comes full circle, and now Microsoft recommends its …
It's a viable alternative, with a rich feature set and a reliable system. PostgreSQL is one of the best RDBMS's currently on the market in 2020, it serves just as well as a starter, PoC DB for any software idea as a final, highly valuable database solution for big systems.
MySQL: As I mentioned before, MySQL has superior write performance. However, Postgres has super read performance and safer ACID transactions, i.e. less potential data loss. Elasticsearch: we use Elasticsearch to store free-form customer data, but that's a different use-case. …
PostgreSQL is rich in features and free to use which is perfect for our organization. PostgreSQL is our goto RDBMS if we want to create an application or services backend with the database if there's no specific requirement. For example for the most important and largest …
PostgreSQL beats every other RDBMS offering for being truly Open Source. Since it does not belong to a specific company it is poised to remain as such for a long time to come. PostgreSQL has a huge user base and active community. The releases are coming out often with …
Very well suited to applications mixing relational with NoSQL and/or complex data types, such as network analysis, JSON, key-value-pair, etc. Excellent if you have multiple programming languages in use (Python, Perl, R, etc.) because PPAS supports so many languages natively. Not well suited if you need encryption at rest, compressed data or very large database-tier backups. [Large backups should be done at the storage tier if possible.]
PostgreSQL is ideal for handling databases that contain large volumes of information due to its efficiency, speed and above all because of the good management it makes of our resources, it also behaves very well in distributed environments of high demand, if you want a database of stable data and excellent performance PostgreSQL is one of the best.
PPAS Oracle compatibility, especially the PL/SQL syntax, has made migrating database-tier code very simple. Most Oracle packages do not need to be changed at all and those that do are generally for simple reasons like a reserved word in PPAS that is allowed in Oracle.
PPAS xDB, the multi-master replication tool, is simple and - most important - does not break with network or other interruptions. We have been able to configure and forget, which our customers could never do with other multi-master tools.
Most people had no idea that PPAS and PostgreSQL have full CRUD support for JSON. They think you need a specialized product and/or that JSON is read-only. Every organization that I have worked with is evaluating adding JSON to their relational model.
Documentation is excellent but spread out across many resources and can take a while to wade through—would benefit from having more intro level, getting started guides for various languages.
Ruby support is excellent but more Ruby examples and beginner-level documentation would be nice.
It is sometimes hard to find a community of users on StackOverflow so a larger community, and a dedicated forum with active members to answer questions and work through issues would be nice.
The performance of PostgreSQL has been enhanced through the years, but always is better to have as much performance as we can.
The replication services could be done directly within the database, and more easily.
The Object Orientation of the Database could be extended, and albeit it manages inheritance of tables, and accepts XML and JSON as primary types, it would be wonderful if one could attach methods more easily to tables (to make them more like classes), and instances (rows for example).
Postgresql is the best tool out there for relational data so I have to give it a high rating when it comes to analytics, data availability and consistency, so on and so forth. SQL is also a relatively consistent language so when it comes to building new tables and loading data in from the OLTP database, there are enough tools where we can perform ETL on a scalable basis.
The data queries are relatively quick for a small to medium sized table. With complex joins, and a wide and deep table however, the performance of the query has room for improvement.
AWS, Heroku, and Digital Ocean all provide Postgres-as-a-service, where you pretty much never need to administrate it yourself but they do it for you. The Postgres community also has developed awesome and reasonably priced extensions, such as Citus DB and CockroachDB in case you need additional support for running it. If you need documentation, Postgres's docs are super thorough and their official forms are active.
The online training is request based. Had there been recorded videos available online for potential users to benefit from, I could have rated it higher. The online documentation however is very helpful. The online documentation PDF is downloadable and allows users to pace their own learning. With examples and code snippets, the documentation is great starting point.
We chose Postgres Plus Advanced Server because we had the finances to do so and needed the robust featureset, along with the power to optimize our performance and integrate with the development tools of our choosing. We audited a number of options, exploring potential solutions at various levels of robustness and decided that this was our best option moving forward.
In this case, Postgres is preferred because it handles large data sets and requires fewer hardware resources than its competitor, MySQL. Compared to PostgreSQL, Microsoft products are excellent, but the installation process for MS SQL is lengthy. PostgreSQL has an advantage over its competitors in that it can adapt or configure third-party programs, applications, or settings.
Postgres Plus Advanced Server is quite complex and may take longer to implement certain things than simply using PostgreSQL depending on developer familiarity with the platform.
Getting up to speed can be daunting so again, there is an upfront cost in time spent learning the platform, besides the potential for extra time spent on a feature-by-feature basis.
The cost of Postgres Plus Advanced Server should be weighed against simply using PostgreSQL to decide which is the best solution for your business needs.
Easy to administer so our DevOps team has only ever used minimal time to setup, tune, and maintain.
Easy to interface with so our Engineering team has only ever used minimal time to query or modify the database. Getting the data is straightforward, what we do with it is the bigger concern.