One of the well-known properties of PostgreSQL is that it is a lean and modular database. At a time when DevOps, virtualization and container platforms are becoming increasingly important topics, this is a decisive factor when choosing software platforms. To ensure this in the long term, PostgreSQL can be supplemented with additional functions via additional software modules or a built-in extension interface. However, this approach is controversially discussed, especially in IT decision-making circles, and unfortunately leads to decisions against using PostgreSQL as an alternative database system.
This article is the start of a 5-part series. It promotes an understanding of the philosophy and concept of extensibility in PostgreSQL. The other austria telegram screening parts of the series will go into more detail about recommendations for extensions and tools. This is intended to provide incentives and inspiration and thus contribute to better decision-making.
aspects of extensibility
Basically, PostgreSQL can do a lot of what is expected of a modern relational database management system without any extensions installed. This applies to both the community versions and the commercial variants. There is a conscious decision not to overload it with features and tools.
The advantage is already apparent in the first steps. A fresh PostgreSQL installation with a standard database is much more space-efficient than with other databases, such as Oracle or MySQL (see Table 1).