PostgreSQL Experts

Is getting top quality support your concern when using open source Postgres? Our new subscription plan combines open source Postgres backed by high quality technical support in a fully managed service so you can start reaping the benefits of Postgres right away.

Because a picture tells a thousand words, we compiled an infographic detailing how EDB has improved Postgres over the years. One of our most exciting developments was introducing the MERGE command this year, which makes it easier for enterprises to migrate from expensive, legacy databases to open source (version 15 of Postgres).

We strive to help enterprises dedicated to innovation take full advantage of what their PostgreSQL and open source strategy can be, with every subsequent version. Whether it’s advising on new features, providing enterprise-grade support or shepherding businesses through major infrastructural projects, EDB has distinguished itself as the PostgreSQL leader.

The world of online trading platforms is allowing more people to take control of their financial futures and creating new opportunities for innovation among application and platform providers. In order to compete, however, these providers need to have a database that can keep pace with the demands of the industry and expectations of their users. 

If, like these executives in the survey, you want to eliminate vendor lock-in and increase scalability by moving to open source, don’t let a perceived lack of Postgres knowledge hold you back! Our fully managed Postgres in the cloud service handles database maintenance for you, so you can focus on business innovation.

Gartner's extensive “2021 Critical Capabilities for Cloud Database Management Systems for Analytical Use Cases” report is designed to help organizations evaluate the strengths and weaknesses of both native services offered by CSPs and fully cloud-based systems. 

Postgres provides several tools to simplify application development. Triggers, for example, allow one event to automatically invoke subsequent inserts, updates, or deletes to either reinforce business logic, or for auditing purposes. But are they valid for all such scenarios? Are there times when triggers would be detrimental to performance and scalability? What are our alternatives? Well, there’s only one way to find out!

In the third and final part of this series (viewable on-demand), EDB’s Performance Engineering and Architecture Team VP, Vibhor Kumar and Solutions Architecture VP, Gianni Ciolli present real-life migration success stories, demonstrating how three different EDB customers successfully migrated from Oracle to Postgres.

Microsoft recently held their annual Ignite Conference as a primarily online event, with an in-person presence in select cities around the world. We asked Microsoft Ignite attendees about their cloud usage and the benefits they expect from fully managed databases. Read on to see the results.

Each database contains a schema named public by default. This schema is also by default part of the search_path. The effect is that if you don't specify any schema in any commands, all the activities take place in this public schema.

When we surveyed our customers in 2020 and asked them what they saw as obstacles when migrating from Oracle to Postgres, cost was their smallest concern, followed by migrating the database definitions, migrating the stored procedures and moving from proprietary drivers to Postgres open source drivers. Their largest concern? Migrating the data.

MERGE is the kind of thing we heard about for a long time before it was really implemented into PostgreSQL. According to Postgres wiki, the first time a contributor asked about this feature is as old as November 2005! We thought for a while we would see it in Postgres 14, but it was finally pushed back to Postgres 15.

In Part 1, we examined how Postgres behaves on older hardware with various allocations of Shared Buffers. This time we repeat those benchmarks on more contemporary hardware equipped with modern SSD storage. The difference this makes is dramatic and has far reaching implications. Join us as we discuss the continuing role of Shared Buffers in modern server deployments!

While legacy, proprietary database providers have been an industry mainstay in the past, mission leaders in government are increasingly recognizing the constraints that these systems impose on their organizations—especially when it comes to control over their own data.

Since version 9.5, PostgreSQL offers the possibility to compress WAL records (when full-page writes are enabled) via the wal_compression parameter. Before PostgreSQL 15, when WAL compression was enabled, only one compression algorithm was available: pglz.

In order to fully harness all of Postgres' potential, however, it’s important to start thinking about the process of migration as early as possible. Ensuring a successful move from Oracle to Postgres starts long before your data starts leaving the Oracle environment.

Postgres 15 is out, with 183 new features and changes. Many of these features are major, but we always try to highlight one feature that is simple and useful. For Postgres 15, we have chosen additions to the copy command for text output and verification of copy headers.

A move to the cloud helps with agility because we can seperate the work to innovate, that is write new code, new queries and new business procedures, from the work to run and maintain the infrastructure.

The exclusive backup mode was deprecated since PostgreSQL 9.6 when non-exclusive backups were introduced. PostgreSQL 15 finally removes that long-deprecated feature and, to avoid any confusion, renames the pg_start_backup() and pg_stop_backup() functions to pg_backup_start() and pg_backup_stop().

Streaming replication is a core utility of PostgreSQL introduced in version 9.0.  Streaming replication allows a standby server to stay more up-to-date than is possible with file-based log shipping.