After part 1 of the series of articles presented the basic philosophy and concept of PostgreSQL extensions, this part provides examples of general extensions and tools from the administration area. Only open source examples are shown. Links to the sources can be found at the end of the article.
Tool pgBasenv
The development of tools and extensions can arise for various reasons. As a rule, the open source concept known from PostgreSQL is continued here. This leads to companies making tools available to the community in order to be able to give something back and to promote the development of these tools. One example is the pgBasenv tool [1] . The tool, which already exists in a similar form for Oracle databases, is intended to austria telegram screening simplify the handling of several parallel PostgreSQL software versions and database clusters. During installation, all configurations are recognized, clearly displayed and made selectable so that it is easy to switch between environments. At the same time, all important environment variables are set accordingly when switching. Technically speaking, pgBasenv is a collection of Bash scripts.
Changing and operating the tool, which is written exclusively in Bash, is done using set alias commands. The pgup command gives you an overview of the installed software versions (Installation homes ) of PostgreSQL and the corresponding database clusters ( Cluster data directories ) created. It was important that the most important details are visible. For example, when listing the Installation homes, the Options column also notes whether SSL encryption is activated, how large the data files are (e.g. 2 GB) or which block size (e.g. 8 KB) has been defined.
The information about the cluster data directories includes the respective status, size and last start time of the database cluster.
An example output is shown in Listing 1. This is how it is displayed when the corresponding operating system user logs in or when pgup is called .