cargo-pgx is a Cargo subcommand for managing pgx-based Postgres extensions.
You'll want to use cargo pgx during your extension development process. It automates the process of creating new Rust crate projects, auto-generating the SQL schema for your extension, installing your extension locally for testing with Postgres, and running your test suite against one or more versions of Postgres.
A video walkthrough of its abilities can be found here: https://www.twitch.tv/videos/684087991
Installing via crates.io is really easy.
$ cargo install cargo-pgxAs new versions of pgx are released, you'll want to make sure you run this command again to update it.
$ cargo pgx --help
cargo-pgx
USAGE:
cargo pgx [SUBCOMMAND]
FLAGS:
-h, --help Prints help information
-V, --version Prints version information
SUBCOMMANDS:
connect connect, via psql, to a Postgres instance
get get a property from the extension control file
help Prints this message or the help of the given subcommand(s)
init initize pgx development environment for the first time
install install the extension from the current crate to the Postgres specified by whatever "pg_config" is
currently on your $PATH
new create a new extension crate
package create an installation package directory (in ./target/[debug|release]/extname-pgXX/).
run compile/install extension to a pgx-managed Postgres instance and start psql
schema generate extension schema files
start start a pgx-managed Postgres instance
status is a pgx-managed Postgres instance running?
stop stop a pgx-managed Postgres instance
test run the test suite for this cratePGX_HOME- If set, overridespgx's default directory of~/.pgx/PGX_BUILD_FLAGS- If set duringcargo pgx run/test/install, these additional flags are passed tocargo buildwhile building the extensionPGX_BUILD_VERBOSE- Set to true to enable verbose "build.rs" output -- useful for debugging build issuesHTTPS_PROXY- If set duringcargo pgx init, it will download the Postgres sources using these proxy settings. For more details refer to the env_proxy crate documentation.
$ cargo pgx init
Discovered Postgres v13.3, v12.7, v11.12, v10.17
Downloading Postgres v12.7 from https://ftp.postgresql.org/pub/source/v12.7/postgresql-12.7.tar.bz2
Stopping Postgres v13
Downloading Postgres v11.12 from https://ftp.postgresql.org/pub/source/v11.12/postgresql-11.12.tar.bz2
Downloading Postgres v10.17 from https://ftp.postgresql.org/pub/source/v10.17/postgresql-10.17.tar.bz2
Downloading Postgres v13.3 from https://ftp.postgresql.org/pub/source/v13.3/postgresql-13.3.tar.bz2
Untarring Postgres v10.17 to /home/yourself/.pgx/10.17
Untarring Postgres v11.12 to /home/yourself/.pgx/11.12
Untarring Postgres v12.7 to /home/yourself/.pgx/12.7
Untarring Postgres v13.3 to /home/yourself/.pgx/13.3
Configuring Postgres v10.17
Configuring Postgres v11.12
Configuring Postgres v12.7
Configuring Postgres v13.3
Compiling Postgres v10.17
Compiling Postgres v13.3
Compiling Postgres v11.12
Compiling Postgres v12.7
Installing Postgres v10.17 to /home/yourself/.pgx/10.17/pgx-install
Installing Postgres v11.12 to /home/yourself/.pgx/11.12/pgx-install
Installing Postgres v12.7 to /home/yourself/.pgx/12.7/pgx-install
Installing Postgres v13.3 to /home/yourself/.pgx/13.3/pgx-install
Validating /home/yourself/.pgx/10.17/pgx-install/bin/pg_config
Validating /home/yourself/.pgx/11.12/pgx-install/bin/pg_config
Validating /home/yourself/.pgx/12.7/pgx-install/bin/pg_config
Validating /home/yourself/.pgx/13.3/pgx-install/bin/pg_configcargo pgx init is required to be run once to properly configure the pgx development environment.
As shown by the screenshot above, it downloads the latest versions of Postgres v10, v11, v12, v13, configures them, compiles them, and installs them to ~/.pgx/. Other pgx commands such as run and test will fully manage and otherwise use these Postgres installations for you.
pgx is designed to support multiple Postgres versions in such a way that during development, you'll know if you're trying to use a Postgres API that isn't common across all three versions. It's also designed to make testing your extension against these versions easy. This is why it requires you have three fully compiled and installed versions of Postgres during development.
If you want to use your operating system's package manager to install Postgres, cargo pgx init has optional arguments that allow you to specify where they're installed (see below).
What you're telling cargo pgx init is the full path to pg_config for each version.
For any version you specify, cargo pgx init will forego downloading/compiling/installing it. pgx will then use that locally-installed version just as it uses any version it downloads/compiles/installs itself.
However, if the unless the "path to pg_config" is the literal string download, the pgx will download and compile that version of Postgres for you.
When the various --pgXX options are specified, these are they only versions of Postgres that pgx will manage for you.
You'll also want to make sure you have the "postgresql-server-dev" package installed for each version you want to manage yourself.
Once complete, cargo pgx init also creates a configuration file (~/.pgx/config.toml) that describes where to find each version's pg_config tool.
If a new minor Postgres version is released in the future you can simply run cargo pgx init [args] again, and your local version will be updated, preserving all existing databases and configuration.
$ cargo pgx init --help
cargo-pgx-pgx-init
initize pgx development environment for the first time
USAGE:
cargo-pgx pgx init [OPTIONS]
FLAGS:
-h, --help Prints help information
-V, --version Prints version information
OPTIONS:
initize pgx development environment for the first time
USAGE:
cargo pgx init [OPTIONS]
FLAGS:
-h, --help Prints help information
-V, --version Prints version information
OPTIONS:
--pg10 <PG10_PG_CONFIG> if installed locally, the path to PG10's 'pg_config' tool, or 'download' to have pgx
download/compile/install it
--pg11 <PG11_PG_CONFIG> if installed locally, the path to PG11's 'pg_config' tool, or 'download' to have pgx
download/compile/install it
--pg12 <PG12_PG_CONFIG> if installed locally, the path to PG12's 'pg_config' tool, or 'download' to have pgx
download/compile/install it
--pg13 <PG13_PG_CONFIG> if installed locally, the path to PG13's 'pg_config' tool, or 'download' to have pgx
download/compile/install it
--pg14 <PG14_PG_CONFIG> if installed locally, the path to PG14's 'pg_config' tool, or 'download' to have pgx
download/compile/install it
cargo pgx new <extname> is an easy way to get started creating a new extension. It's similar to cargo new <name>, but does the additional things necessary to support building a Rust Postgres extension.
If you'd like to create a "background worker" instead, specify the --bgworker argument.
cargo pgx new does not initialize the directory as a git repo, but it does create a .gitignore file in case you decide to do so.
$ cargo pgx new --help
cargo-pgx-new 0.1.21
create a new extension crate
USAGE:
cargo pgx new [FLAGS] <NAME>
FLAGS:
-b, --bgworker create a background worker template
-h, --help Prints help information
-V, --version Prints version information
ARGS:
<NAME> the name of the extension$ cargo pgx status
Postgres v10 is stopped
Postgres v11 is stopped
Postgres v12 is stopped
Postgres v13 is stopped
$ cargo pgx start all
Starting Postgres v10 on port 28810
Starting Postgres v11 on port 28811
Starting Postgres v12 on port 28812
Starting Postgres v13 on port 28813
$ cargo pgx status
Postgres v10 is running
Postgres v11 is running
Postgres v12 is running
Postgres v13 is running
$ cargo pgx stop pg10
Stopping Postgres v10
$ cargo pgx status
Postgres v10 is stopped
Postgres v11 is running
Postgres v12 is running
Postgres v13 is runningcargo pgx has three commands for managing each Postgres installation: start, stop, and status. Additionally, cargo pgx run (see below) will automatically start its target Postgres instance if not already running.
When starting a Postgres instance, pgx starts it on port 28800 + PG_MAJOR_VERSION, so Postgres 10 runs on 28810, 11 on 28811, etc. Additionally, the first time any of these are started, it'll automaticaly initialize a PGDATA directory in ~/.pgx/data-[10 | 11 | 12]. Doing so allows pgx to manage either Postgres versions it installed or ones already on your computer, and to make sure that in the latter case, pgx managed versions don't interfere with what might already be running.
pgx doesn't tear down these instances. While they're stored in a hidden directory in your home directory, pgx considers these important and permanent database installations.
Once started, you can connect to them using psql (if you have it on your $PATH) like so: psql -p 28812. However, you probably just want the cargo pgx run command.
$ cargo pgx run pg13
Stopping Postgres v13
building extension with features `pg13`
"cargo" "build" "--features" "pg13" "--no-default-features"
Finished dev [unoptimized + debuginfo] target(s) in 0.09s
installing extension
Copying control file to `/home/yourself/.pgx/13.3/pgx-install/share/postgresql/extension/strings.control`
Copying shared library to `/home/yourself/.pgx/13.3/pgx-install/lib/postgresql/strings.so`
Finished dev [unoptimized + debuginfo] target(s) in 0.09s
Running `target/debug/sql-generator /home/yourself/.pgx/13.3/pgx-install/share/postgresql/extension/strings--1.0.sql`
Finished installing strings
Starting Postgres v13 on port 28813
Re-using existing database strings
psql (13.3)
Type "help" for help.
strings=# DROP EXTENSION strings;
DROP EXTENSION
strings=# CREATE EXTENSION strings;
CREATE EXTENSION
strings=# \df strings.*
List of functions
Schema | Name | Result data type | Argument data types | Type
---------+---------------+------------------+------------------------------------------+------
strings | append | text | input text, extra text | func
strings | return_static | text | | func
strings | split | text[] | input text, pattern text | func
strings | split_set | SETOF text | input text, pattern text | func
strings | substring | text | input text, start integer, "end" integer | func
strings | to_lowercase | text | input text | func
(6 rows)
strings=# select strings.to_lowercase('PGX');
to_lowercase
--------------
pgx
(1 row)cargo pgx run <pg10 | pg11 | pg12 | pg13> is the primary interface into compiling and interactively testing/using your extension during development.
The very first time you execute cargo pgx run pgXX, it needs to compile not only your extension, but pgx itself, along with all its dependencies. Depending on your computer, this could take a bit of time (pgx is nearly 200k lines of Rust when counting the generated bindings for Postgres). Afterwards, however (as seen in the above screenshot), it's fairly fast.
cargo pgx run compiles your extension, installs it to the specified Postgres installation as described by its pg_config tool, starts that Postgres instance using the same process as cargo pgx start pgXX, and drops you into a psql shell connected to a database, by default, named after your extension. From there, it's up to you to create your extension and use it.
This is also the stage where pgx automatically generates the SQL schema for your extension. It places individual modname.generated.sql files into ./sql/, and then combines those together by the order defined in ./sql/load-order.txt.
When you exit psql, the Postgres instance continues to run in the background.
For Postgres installations which are already on your computer, cargo pgx run will need write permissions to the directories described by pg_config --pkglibdir and pg_config --sharedir. It's up to you to decide how to make that happen. While a single Postgres installation can be started multiple times on different ports and different data directories, it does not support multiple "extension library directories".
$ cargo pgx run --help
cargo-pgx-run
compile/install extension to a pgx-managed Postgres instance and start psql
USAGE:
cargo pgx run [FLAGS] [OPTIONS] <PG_VERSION> [--] [DBNAME]
FLAGS:
-h, --help Prints help information
-r, --release compile for release mode (default is debug)
-n, --no-schema Don't regenerate the schema
-V, --version Prints version information
OPTIONS:
--features <features>... additional cargo features to activate (default is '--no-default-features')
ARGS:
<PG_VERSION> Do you want to run against Postgres 'pg10', 'pg11', 'pg12', 'pg13'?
<DBNAME> The database to connect to (and create if the first time). Defaults to a database with the same
name as the current extension name$ cargo pgx connect pg13 strings
Re-using existing database strings
psql (13.3)
Type "help" for help.
strings=# select strings.to_lowercase('PGX');
to_lowercase
--------------
pgx
(1 row)If you'd simply like to connect to a managed version of Postgres without re-compiling and installing
your extension, use cargo pgx connect <pg10 | pg11 | pg12 | pg13>.
This command will use the default database named for your extension, or you can specify another database name as the final argument.
If the specified database doesn't exist, cargo pgx connect will create it. Similarly, if
the specified version of Postgres isn't running, it'll be automatically started.
$ cargo pgx connect --help
cargo-pgx-connect
connect, via psql, to a Postgres instance
USAGE:
cargo pgx connect <PG_VERSION> [DBNAME]
FLAGS:
-h, --help Prints help information
-V, --version Prints version information
ARGS:
<PG_VERSION> Do you want to run against Postgres 'pg10', 'pg11', 'pg12', 'pg13'?
<DBNAME> The database to connect to (and create if the first time). Defaults to a database with the same
name as the current extension namecargo pgx install
building extension with features `pg12`
"cargo" "build" "--features" "pg12" "--no-default-features"
Finished dev [unoptimized + debuginfo] target(s) in 0.18s
installing extension
Copying control file to `/home/yourself/pg12/share/postgresql/extension/strings.control`
Copying shared library to `/home/yourself/pg12/lib/postgresql/strings.so`
`src/bin/sql-generator.rs` does not exist or is not what is expected.
If you encounter problems please delete it and use the generated version.
running SQL generator features `pg12`
"cargo" "run" "--bin" "sql-generator" "--features" "pg12" "--no-default-features" "--" "/home/yourself/pg12/share/postgresql/extension/strings--1.0.sql"
Finished dev [unoptimized + debuginfo] target(s) in 0.11s
Running `target/debug/sql-generator /home/yourself/pg12/share/postgresql/extension/strings--1.0.sql`
Finished installing stringsIf for some reason cargo pgx run <PG_VERSION> isn't your style, you can use cargo pgx install to install your extension
to the Postgres installation described by the pg_config tool currently on your $PATH.
You'll need write permissions to the directories described by pg_config --pkglibdir and pg_config --sharedir.
By default, cargo pgx install builds your extension in debug mode. Specifying --release changes that.
$ cargo pgx install --help
cargo-pgx-install
install the extension from the current crate to the Postgres specified by whatever "pg_config" is currently on your
$PATH
USAGE:
cargo pgx install [FLAGS] [OPTIONS]
FLAGS:
-h, --help Prints help information
-r, --release compile for release mode (default is debug)
-n, --no-schema Don't regenerate the schema
-V, --version Prints version information
OPTIONS:
--features <features>... additional cargo features to activate (default is '--no-default-features')
-c, --pg_config <pg_config> the `pg_config` path (default is first in $PATH)$ cargo pgx test pg13
"cargo" "test" "--all" "--features" " pg13 pg_test" "--no-default-features"
Finished test [unoptimized + debuginfo] target(s) in 0.11s
Running unittests (target/debug/deps/spi-ce9e68c581d521ac)
running 2 tests
building extension with features `pg13 pg_test`
"cargo" "build" "--features" "pg13 pg_test" "--no-default-features"
Finished dev [unoptimized + debuginfo] target(s) in 0.09s
installing extension
Copying control file to `/home/yourself/.pgx/13.3/pgx-install/share/postgresql/extension/spi.control`
Copying shared library to `/home/yourself/.pgx/13.3/pgx-install/lib/postgresql/spi.so`
`src/bin/sql-generator.rs` does not exist or is not what is expected.
If you encounter problems please delete it and use the generated version.
running SQL generator features `pg13 pg_test`
"cargo" "run" "--bin" "sql-generator" "--features" "pg13 pg_test" "--no-default-features" "--" "/home/yourself/.pgx/13.3/pgx-install/share/postgresql/extension/spi--1.0.sql"
Finished dev [unoptimized + debuginfo] target(s) in 0.09s
Running `target/debug/sql-generator /home/yourself/.pgx/13.3/pgx-install/share/postgresql/extension/spi--1.0.sql`
Aug 03 10:26:39.108 INFO Writing SQL. path=/home/yourself/.pgx/13.3/pgx-install/share/postgresql/extension/spi--1.0.sql
Finished installing spi
test tests::pg_test_spi_query_by_id_direct ... ok
test tests::pg_test_spi_query_by_id_via_spi ... ok
test result: ok. 2 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.56s
Stopping Postgres
Running unittests (target/debug/deps/sql_generator-0bc6e7d903af4637)
running 0 tests
test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.00s
Doc-tests spi
running 0 tests
test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.00scargo pgx test [pg10 | pg11 | pg12 | pg13] runs your #[test] and #[pg_test] annotated functions using cargo's test system.
During the testing process, pgx starts a tempory instance of Postgres with its PGDATA directory in ./target/pgx-test-data-PGVER/. This Postgres instance is stopped as soon as the test framework has finished.
The output is standard "cargo test" output along with some Postgres log output. In the case of test failures, the failure report will include any Postgres log messages generated by that particular test.
Rust #[test] functions behave normally, while #[pg_test] functions are run inside the Postgres instance and have full access to all of Postgres internals. All tests are run in parallel, regardless of their type.
Additionally, a #[pg_test] function runs in a transaction that is aborted when the test is finished. As such, any changes it might
make to the database are not preserved.
$ cargo pgx test --help
cargo-pgx-test
run the test suite for this crate
USAGE:
cargo pgx test [FLAGS] [OPTIONS] [--] [ARGS]
FLAGS:
-h, --help Prints help information
-r, --release compile for release mode (default is debug)
-n, --no-schema Don't regenerate the schema
-V, --version Prints version information
--workspace Test all packages in the workspace
OPTIONS:
--features <features>... additional cargo features to activate (default is '--no-default-features')
ARGS:
<PG_VERSION> Do you want to test for Postgres 'pg10', 'pg11', 'pg12', 'pg13', or 'all' (default)?
<TESTNAME> If specified, only run tests containing this string in their names$ cargo pgx package
building extension with features `pg12`
"cargo" "build" "--release" "--features" "pg12" "--no-default-features"
Finished release [optimized] target(s) in 0.07s
installing extension
Copying control file to `target/release/spi-pg12/usr/share/postgresql/12/extension/spi.control`
Copying shared library to `target/release/spi-pg12/usr/lib/postgresql/12/lib/spi.so`
Building SQL generator with features `pg12`
"cargo" "build" "--bin" "sql-generator" "--release" "--features" "pg12" "--no-default-features"
Finished release [optimized] target(s) in 0.07s
Discovering SQL entities
Discovered 8 SQL entities: 0 schemas (0 unique), 6 functions, 0 types, 0 enums, 2 sqls, 0 ords, 0 hashes
running SQL generator with features `pg12`
"cargo" "run" "--bin" "sql-generator" "--release" "--features" "pg12" "--no-default-features" "--" "--sql" "/home/yourself/pgx/pgx-examples/spi/target/release/spi-pg12/usr/share/postgresql/12/extension/spi--1.0.sql"
Finished release [optimized] target(s) in 0.07s
Running `target/release/sql-generator --sql /home/yourself/pgx/pgx-examples/spi/target/release/spi-pg12/usr/share/postgresql/12/extension/spi--1.0.sql`
Finished installing spicargo pgx package [--debug] builds your extension, in --release mode, to a directory structure in
./target/[debug | release]/extension_name-PGVER using the Postgres installation path information from the pg_config
tool on your $PATH.
The intent is that you'd then change into that directory and build a tarball or a .deb or .rpm package.
The directory structure cargo pgx package creates starts at the root of the filesystem, as a package-manager installed
version of Postgres is likely to split pg_config --pkglibdir and pg_config --sharedir into different base paths.
(In the example screenshot above, cargo pgx package was used to build a directory structure using my manually installed
version of Postgres 12.)
This command could be useful from Dockerfiles, for example, to automate building installation packages for various Linux distobutions or MacOS Postgres installations.
$ cargo pgx package --help
cargo-pgx-package
create an installation package directory (in ./target/[debug|release]/extname-pgXX/) for the Postgres installation
specified by whatever "pg_config" is currently on your $PATH
USAGE:
cargo-pgx pgx package [FLAGS]
FLAGS:
-d, --debug compile for debug mode (default is release)
-h, --help Prints help information
-V, --version Prints version information
OPTIONS:
--features <features>... additional cargo features to activate (default is '--no-default-features')
-c, --pg_config <pg_config> the `pg_config` path (default is first in $PATH)If you just want to look at the full extension schema that pgx will generate, use
cargo pgx schema /dir/to/write/it/.
$ cargo pgx schema --help
cargo-pgx-schema 0.1.22
generate extension schema files
USAGE:
cargo pgx schema [FLAGS] [OPTIONS] [--] [PG_VERSION]
FLAGS:
-f, --force-default Force the generation of default required files
-h, --help Prints help information
-m, --manual Skip checking for required files
-r, --release Compile for release mode (default is debug)
-V, --version Prints version information
-v, --verbose Enable debug logging (-vv for trace)
OPTIONS:
-d, --dot <dot> A path to output a produced GraphViz DOT file [default: extension.dot]
--features <features>... additional cargo features to activate (default is none)
-o, --out <out> A path to output a produced SQL file (default is `sql/$EXTNAME-$VERSION.sql`)
-c, --pg_config <pg_config> the `pg_config` path (default is first in $PATH)
ARGS:
<PG_VERSION> Do you want to run against Postgres 'pg10', 'pg11', 'pg12', 'pg13'?
REQUIREMENTS
The SQL generation process requires configuring a few settings in the crate. Normally 'cargo pgx schema --force-
default'
can set these automatically.
They are documented in the README.md of cargo-pgx: https://github.com/zombodb/pgx/tree/master/cargo-pgx#Manual-SQL-GenerationThis section is for users with custom
.cargo/configsettings or advanced requirements.If you are not using
cargo pgx initto generate your extension, or you're upgrading your extension frompgx0.1.21 or earlier, you can usually havecargo-pgxprovision it's base requirements withcargo pgx schema --force-default.
SQL generation requires some linker flags, as well as a binary.
The flags are typically set by a linker script:
#! /usr/bin/env bash
# Auto-generated by pgx. You may edit this, or delete it to have a new one created.
if [[ $CARGO_BIN_NAME == "sql-generator" ]]; then
UNAME=$(uname)
if [[ $UNAME == "Darwin" ]]; then
TEMP=$(mktemp pgx-XXX)
echo "*_pgx_internals_*" > ${TEMP}
gcc -exported_symbols_list ${TEMP} $@
rm -rf ${TEMP}
else
TEMP=$(mktemp pgx-XXX)
echo "{ __pgx_internals_*; };" > ${TEMP}
gcc -Wl,-dynamic-list=${TEMP} $@
rm -rf ${TEMP}
fi
else
gcc -Wl,-undefined,dynamic_lookup $@
fiWhich would be configured in .cargo/config for supported targets:
[target.aarch64-unknown-linux-gnu]
linker = "./.cargo/linker-script.sh"Then, a src/bin/sql-generator.rs binary would exist with the following:
pgx::pg_binary_magic!(extension_name);If cargo pgx schema does not detect these, it will create them automatically with defaults.
To skip writing defaults, use -m, to overwrite exiting files with these defaults, use -f.
Finally, lib.crate-type should be set in Cargo.toml:
[lib]
crate-type = ["cdylib", "rlib"]cargo pgx schema --force-default does not update your Cargo.toml, this must be manually set.