## Chapter 36. Extending SQL

In the sections that follow, we will discuss how you can extend the Postgres Pro SQL query language by adding:

- functions (starting in Section 36.3)

- aggregates (starting in Section 36.10)

- data types (starting in Section 36.11)

- operators (starting in Section 36.12)

- operator classes for indexes (starting in Section 36.14)

- packages of related objects (starting in Section 36.15)

## 36.1. How Extensibility Works

Postgres Pro is extensible because its operation is catalog-driven. If you are familiar with standard relational database systems, you know that they store information about databases, tables, columns, etc., in what are commonly known as system catalogs. (Some systems call this the data dictionary.) The catalogs appear to the user as tables like any other, but the DBMS stores its internal bookkeeping in them. One key difference between Postgres Pro and standard relational database systems is that Postgres Pro stores much more information in its catalogs: not only information about tables and columns, but also information about data types, functions, access methods, and so on. These tables can be modified by the user, and since Postgres Pro bases its operation on these tables, this means that Postgres Pro can be extended by users. By comparison, conventional database systems can only be extended by changing hardcoded procedures in the source code or by loading modules specially written by the DBMS vendor.

The Postgres Pro server can moreover incorporate user-written code into itself through dynamic loading. That is, the user can specify an object code file (e.g., a shared library) that implements a new type or function, and Postgres Pro will load it as required. Code written in SQL is even more trivial to add to the server. This ability to modify its operation “on the fly” makes Postgres Pro uniquely suited for rapid prototyping of new applications and storage structures.