Extensions are modules commonly used to install additional features on a database server. Despite the extensive list of built-in extensions, PostgreSQL provides some ways for the user to write custom extensions although this topic will not be covered in this manual. Basically, extensions are a set of other objects like functions, types, operators, and many others. When the user needs to install a certain extension all the objects owned by it are installed as part of the database.
In pgModeler, an extension object is used just to tell the server that the named extension must be installed at the specified schema. To work correctly, the extension modules or libraries must exist in the database server. Following, the extension attributes are detailed.
||Specifies the schema where the objects installed by the extension will be placed.|
||The current version of the extension to be installed.|
||This attribute must be specified when, and only when, you are attempting to install an extension that replaces an "old style" module that is just a collection of objects not packaged into an extension.|
||Indicates that the extension installs a data type. It is assumed that the data type has the same name as the extension itself. Once created, the extension type will be available in the data type configuration widget. Unfortunately, there is a limitation in the usage of this attribute: if the extension installs more than one data type, pgModeler will create only the data type named by the extension. To create the additional types you can mock these objects by creating simple user-defined types and disabling their SQL codes. Details about mocking objects can be seen in the chapter dedicated to modeling tips and tricks.|
PostgreSQL built-in extensions