PostgreSQL Experts

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.

The purpose of this blog is to illustrate how to save pgAdmin 4 configurations to an external database server. In addition, we covered examples that demonstrate how to use PostgreSQL server as an external database.

This blog explains the purpose of the various configuration files used by pgAdmin, when they should be modified, and for what reason.

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.

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.

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.

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.

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().

One of the guiding Postgres design principles is heavy reliance on features provided by the environment (particularly operating system) and file systems are a prime example of this. Unlike other databases Postgres never supported raw devices that would require implementing a “custom” file system.

The PostgreSQL project roadmap is quite simple: there is a new major version each year around October/November and minor versions each quarter (unless there is a critical bug to fix). Now, Postgres 15 has arrived!

With 40 Postgres contributors, EDB has contributed extensively to the Postgres community over the years, including working on certain extensions.

The DBMS landscape is experiencing seismic changes right beneath our feet, innovators and market leaders across industries are taking notice. As of 2021, open source database licenses outpace commercial database licenses and this trend shows no signs of slowing.

EDB thanks everyone who has contributed to this great new release in any way! EDB is committed to helping the Community improve Postgres with each release, as it has done for the last 16 versions. For Postgres 15, EDB has made significant contributions.

A PostGIS cluster is essentially a PostgreSQL cluster with a primary and an arbitrary number of standby instances where the running operand image contains all the required PostGIS related extensions.