Database Reference
In-Depth Information
You will now find that you have a utility installed named
pgxn-utils
. This utility
makes it super simple to create an extension project.
pgxn-utils skeleton myextension
create myextension
create myextension/myextension.control
create myextension/META.json
create myextension/Makefile
create myextension/README.md
create myextension/doc/myextension.md
create myextension/sql/myextension.sql
create myextension/sql/
uninstall_myextension.sql
create myextension/test/expected/base.out
create myextension/test/sql/base.sql
Wow! All of the files that we have mentioned so far just got created in a single step.
Several files also got created to support the old contrib style of deployment. The next
few sections will show which ones are important to you for extension development.
This package management system has one notable restriction. In contrast to Post-
greSQL, which allows version numbers to be any alphanumeric text, this package
management requires version numbers to follow the rules of semantic versioning.
This version format includes major version, minor version, and release number in the
format
major.minor.release
. This is to assist the package manager in installing
your package on multiple operating system platforms. Just go with it, you'll thank us
later.
Providing the metadata about the extension
There are three files used to provide data about the extension. The PostgreSQL Ex-
tension Network uses one of them on the website,
META.json
, for search criteria
and description text for the extension.
META.json
will be located in
myextension/
META.json
.
Here is an example:
