pgxman

https://docs.pgxman.com
Admin
pgxman is a package manager for Postgres extensions that simplifies discovery, installation, and...
Tokens:9,947
Snippets:177
Trust Score:6.1
Update:5 months ago
Show doc for...
Tokens:
Raw
### Example Build Script Configuration

Source: https://docs.pgxman.com/spec/buildkit

Specifies the build commands for an extension. Ensure DESTDIR is correctly set for installation.

```yaml
build: |
  make
  DESTDIR=${DESTDIR} make install
```

--------------------------------

### Example pgxman.yaml for Docker testing

Source: https://docs.pgxman.com/building_an_extension

A sample `pgxman.yaml` file used within a Docker container to specify the extension package to install. Adjust the `path` and `postgres.version` as needed.

```yaml
apiVersion: v1
extensions:
- path: "./out/debian/bookworm/postgresql-15-pgxman-yourpackage_1.2.3_arm64.deb"
postgres:
  version: 15
```

--------------------------------

### Install from Local Debian Package

Source: https://docs.pgxman.com/cli/pgxman_install

Installs an extension from a local Debian package file. Provide the full path to the `.deb` file as the argument.

```bash
pgxman install /PATH_TO/postgresql-15-pgxman-pgvector_0.5.0_arm64.deb
```

--------------------------------

### Install Multiple Extensions

Source: https://docs.pgxman.com/cli/pgxman_install

Installs multiple extensions with specific versions for a designated PostgreSQL version. List each extension and its version separated by spaces.

```bash
pgxman install pgvector=0.5.0 postgis=3.3.3 --pg 15
```

--------------------------------

### Complete Buildkit Configuration Example

Source: https://docs.pgxman.com/spec/buildkit

This example demonstrates all available fields in a pgxman buildkit configuration file. It includes metadata, build steps, dependencies, and overrides for different builders and PostgreSQL versions.

```yaml
# API version of the buildkit specification. Only v1 is supported.
apiVersion: v1
# Name of the extension.
name: my-extension
# Version of the extension. Must be in semantic versioning v2 format.
version: "0.4.4"
# URL of the extension's homepage.
homepage: https://github.com/org/repo
# URL of the extension's repository.
repository: https://github.com/org/repo
# URL of the extension's source code. Only `tar.gz` files are supported.
source: https://github.com/org/repo/archive/refs/tags/v0.4.4.tar.gz
# Description of the extension.
description: Extension description
# License of the extension. Must be a valid SPDX license identifier.
license: PostgreSQL
# Keywords relevant to the extension.
keywords:
  - keyword1
  - keyword2
# Supported architectures.
arch:
  - amd64
  - arm64
# Maintainers of the buildkit.
maintainers:
  - name: Owen Ou
    email: o@hydra.so
# Supported PostgreSQL versions.
pgVersions:
  - "13"
  - "14"
  - "15"
  - "16"
# Build scripts for the extension.
build:
  # Steps to be executed before the main build process.
  pre:
    - name: Install dependencies
      run: |
        # Do something
  # Steps to be executed for the main build process.
  main:
    - name: Build pgvector
      run: |
        # Do something
  # Steps to be executed after the main build process.
  post:
    - name: Cleanup
      run: |
        # Do something
# Build dependencies of the extension.
buildDependencies:
  - dep1
  - dep2
  - pgxman/extension
# Run dependencies of the extension.
runDependencies:
  - dep3
  - dep4
  - pgxman/extension
# Overrides the default builders to be used.
builders:
  # Overrides the debian:bookworm builder.
  debian:bookworm:
    # Overrides the global build dependencies for this builder.
    buildDependencies:
      - dep1
      - dpe2
    # Overrides the global run dependencies for this builder.
    runDependencies:
      - dep3
      - dep4
    # Extra APT repositories to add.
    aptRepositories:
      - id: repo1
        types:
          - deb
          - deb-src
        uris:
          - http://repo1.com
        suites:
          - suite1
        components:
          - comp1
        signedKey:
          - uri: http://repo1.com/key
            format: gpg
  # Overrides the ubuntu:jammy builder.
  ubuntu:jammy:
    # Overrides the global build dependencies for this builder.
    buildDependencies:
      - dep1
      - dpe2
    # Overrides the global run dependencies for this builder.
    runDependencies:
      - dep3
      - dep4
    # Extra APT repositories to add.
    aptRepositories:
      - id: repo1
        types:
          - deb
          - deb-src
        uris:
          - http://repo1.com
        suites:
          - suite1
        components:
          - comp1
        signedKey:
          - uri: http://repo1.com/key
            format: gpg
overrides:
  pgVersions:
    # overrides fields for pg 13
    "13":
      version: "1.2.3"
      homepage: https://github.com/org/repo2
      repository: https://github.com/org/repo2
      source: https://github.com/org/repo/archive/refs/tags/v1.2.3.tar.gz
    # overrides fields for pg 14
    "14":
      version: "2.3.4"
      homepage: https://github.com/org/repo3
      repository: https://github.com/org/repo3
      source: https://github.com/org/repo/archive/refs/tags/v2.3.4.tar.gz

```

--------------------------------

### Install pgxman via curl script

Source: https://docs.pgxman.com/installing_pgxman

Use this command to download and execute the pgxman installer script. It works on both MacOS and Linux.

```sh
curl -sfL https://install.pgx.sh | sh -
```

--------------------------------

### Install a Specific Version of an Extension

Source: https://docs.pgxman.com/installing_extensions

Specify the desired version of an extension using the '=version' syntax. This ensures you install a particular release.

```bash
pgxman install pgvector=0.5.0
```

--------------------------------

### Batch Install Extensions using pgxman.yaml

Source: https://docs.pgxman.com/installing_extensions

Define multiple extensions and PostgreSQL versions in a pgxman.yaml file for batch installation or upgrades. This simplifies managing several extensions at once.

```yaml
apiVersion: v1
extensions:
  - name: "pgvector"
    version: "0.5.0"
  - name: "pg_ivm"
    version: "1.5.1"
pgVersions:
  - "15"
```

```bash
pgxman pack install -f pgxman.yaml
```

--------------------------------

### Install Extension into Container

Source: https://docs.pgxman.com/container

Use this command to install an extension into a pgxman container. Specify the desired PostgreSQL version using the --pg flag. Installation is persistent and rebuilds the container image.

```sh
pgxman c install extension --pg version
```

--------------------------------

### Install Extension with Sudo

Source: https://docs.pgxman.com/cli/pgxman_install

Installs a specific version of an extension for a specified PostgreSQL version using `sudo` for elevated privileges. This is useful when installing extensions in system-wide PostgreSQL installations.

```bash
pgxman install pgvector=0.5.0 --pg 15 --sudo
```

--------------------------------

### Install Postgres 16 on Linux

Source: https://docs.pgxman.com/installing_postgres

After adding the PGDG repository, use this command to install PostgreSQL version 16. Adjust the version number to install a different supported version.

```sh
sudo apt install postgresql-16
```

--------------------------------

### Install Extensions with Automatic Confirmation

Source: https://docs.pgxman.com/cli/pgxman_pack_install

Installs PostgreSQL extensions while suppressing interactive prompts for automatic installation or upgrades. Use this for non-interactive environments or scripting.

```bash
pgxman pack install -y
```

--------------------------------

### Install Extensions from Current Directory Pack File

Source: https://docs.pgxman.com/cli/pgxman_pack_install

Installs PostgreSQL extensions using the 'pgxman.yaml' file located in the current directory. This is the default behavior when no file is explicitly specified.

```bash
pgxman pack install
```

--------------------------------

### Initialize a buildkit file with pgxman

Source: https://docs.pgxman.com/building_an_extension

Run this command to start the interactive process of creating a new extension manifest file (`extension.yaml`).

```sh
pgxman init
```

--------------------------------

### Search using a regular expression

Source: https://docs.pgxman.com/cli/pgxman_search

Employ regular expressions to perform more advanced searches. This example finds all extensions whose names start with 'pg_'.

```bash
pgxman search ^pg_
```

--------------------------------

### Install Latest pgvector for PostgreSQL 15

Source: https://docs.pgxman.com/cli/pgxman_container_install

This command installs the latest pgvector extension specifically for PostgreSQL version 15. Ensure PostgreSQL 15 is supported by your pgxman setup.

```bash
pgxman container install pgvector --pg 15
```

--------------------------------

### Install pgxman via Homebrew on MacOS

Source: https://docs.pgxman.com/installing_pgxman

For MacOS users, install pgxman using the provided Homebrew tap. This command adds the pgxman repository and installs the package.

```sh
brew install pgxman/tap/pgxman
```

--------------------------------

### Install Extensions from STDIN Pack File

Source: https://docs.pgxman.com/cli/pgxman_pack_install

Installs PostgreSQL extensions by reading the pack file content from standard input (STDIN). This allows for dynamic generation or piping of pack file definitions.

```bash
cat <<EOF | pgxman pack install -f -
    apiVersion: v1
    extensions:
      - name: "pgvector"
        version: "0.5.0"
      - path: "/local/path/to/extension"
    postgres:
      version: "14"
  EOF
```

--------------------------------

### Install Extension with Sudo Privileges

Source: https://docs.pgxman.com/installing_extensions

Append the '--sudo' flag to install extensions using administrator privileges if required by your system's package manager.

```bash
pgxman install pgvector=0.5.0@15 --sudo
```

--------------------------------

### Install Multiple Extensions for PostgreSQL 15

Source: https://docs.pgxman.com/cli/pgxman_container_install

Install multiple PostgreSQL extensions, such as pgvector and postgis, with their specified versions for PostgreSQL 15 in a single command.

```bash
pgxman container install pgvector=0.5.0 postgis=3.3.3 --pg 15
```

--------------------------------

### Install Local Debian Package in a Container

Source: https://docs.pgxman.com/cli/pgxman_container_install

Install a PostgreSQL extension from a local Debian package file within a container. Replace '/PATH_TO/' with the actual path to your .deb file.

```bash
pgxman container install /PATH_TO/postgresql-15-pgxman-pgvector_0.5.0_arm64.deb
```

--------------------------------

### Dockerfile for testing extensions with Docker

Source: https://docs.pgxman.com/building_an_extension

This Dockerfile sets up a PostgreSQL environment and installs your built extension. Ensure your extension artifacts are in the `out/` directory and `pgxman.yaml` is configured correctly.

```Dockerfile
FROM postgres:15-bookworm

RUN apt-get update && \
  apt-get install -y curl && \
  curl -sfL https://install.pgx.sh | sh - 

COPY out/ /pgxman/out/
COPY pgxman.yaml /pgxman/pgxman.yaml

WORKDIR /pgxman
RUN pgxman install --debug -f pgxman.yaml
```

--------------------------------

### Example pgxman Pack Configuration

Source: https://docs.pgxman.com/spec/pack

This is an example of a pgxman pack YAML file. It declares the 'pgvector' and 'pg_ivm' extensions with specified versions and targets PostgreSQL version 15. It also shows how to include a local extension path.

```yaml
apiVersion: v1
extensions:
  - name: "pgvector"
    version: "0.5.0"
  - name: "pg_ivm"
    version: "1.5.1"
  - path: "/local/path/to/extension"
postgres:
  version: "15"
```

--------------------------------

### Start a pgxman Container

Source: https://docs.pgxman.com/container

Restart a previously stopped pgxman container using the docker start command. Replace NAME with the container's name.

```sh
docker start pgxman_runner_15
```

--------------------------------

### Install Extensions from a Specified Pack File Location

Source: https://docs.pgxman.com/cli/pgxman_pack_install

Installs PostgreSQL extensions using a pack file located at a specific path. This is useful when your pack file is not in the current directory.

```bash
pgxman pack install -f /PATH_TO/pgxman.yaml
```

--------------------------------

### Enable a Postgres extension

Source: https://docs.pgxman.com/quickstart

After connecting to Postgres, list available extensions and then create the desired extension, for example, 'vector'.

```sql
postgres=# select * from pg_available_extensions;
... 
postgres=# create extension vector;
CREATE EXTENSION
```

--------------------------------

### Install Latest Extension

Source: https://docs.pgxman.com/cli/pgxman_install

Installs the latest version of a specified extension for the detected or latest supported PostgreSQL version. The PostgreSQL version is automatically detected from `pg_config` if available.

```bash
pgxman install pgvector
```

--------------------------------

### Install Latest pgvector in a Container

Source: https://docs.pgxman.com/cli/pgxman_container_install

Use this command to install the latest version of the pgvector extension in a new container. No specific PostgreSQL version is required, so the default will be used.

```bash
pgxman container install pgvector
```

--------------------------------

### Install Extension for Specific PostgreSQL Version

Source: https://docs.pgxman.com/cli/pgxman_install

Installs the latest version of a specified extension for a particular PostgreSQL version. Use the `--pg` flag to specify the target PostgreSQL version.

```bash
pgxman install pgvector --pg 15
```

--------------------------------

### Install Specific Extension Version for PostgreSQL

Source: https://docs.pgxman.com/cli/pgxman_install

Installs a specific version of an extension for a specified PostgreSQL version. Append the version number to the extension name using `=` and use the `--pg` flag for the PostgreSQL version.

```bash
pgxman install pgvector=0.5.0 --pg 15
```

--------------------------------

### List Available PostgreSQL Extensions

Source: https://docs.pgxman.com/using_extensions

To find the exact name of an installed extension, query the pg_available_extensions view. This helps in correctly using the CREATE EXTENSION command.

```sql
SELECT * FROM pg_available_extensions;
```

--------------------------------

### Upgrade Latest pgvector for Installed PostgreSQL

Source: https://docs.pgxman.com/cli/pgxman_upgrade

Use this command to upgrade the latest version of the pgvector extension for your currently installed PostgreSQL. The PostgreSQL version is automatically detected.

```bash
pgxman upgrade pgvector
```

--------------------------------

### Search for a Postgres extension

Source: https://docs.pgxman.com/quickstart

Use the search command to find available extensions. For example, search for the 'vector' extension.

```bash
pgxman search vector
```

--------------------------------

### Add PGDG apt repository

Source: https://docs.pgxman.com/installing_postgres

Run these commands to add the Postgres Global Developer Group (PGDG) apt repository to your system. This is a prerequisite for installing Postgres via apt.

```sh
sudo apt install -y postgresql-common gnupg2
sudo /usr/share/postgresql-common/pgdg/apt.postgresql.org.sh
```

--------------------------------

### Install Specific pgvector Version for PostgreSQL 15

Source: https://docs.pgxman.com/cli/pgxman_container_install

Install a precise version (0.5.0) of the pgvector extension for PostgreSQL 15. This is useful for ensuring compatibility or using specific features of an older version.

```bash
pgxman container install pgvector=0.5.0 --pg 15
```

--------------------------------

### Search for a specific extension

Source: https://docs.pgxman.com/cli/pgxman_search

Use this command to find a particular extension by its name. For example, to search for 'pgvector'.

```bash
pgxman search pgvector
```

--------------------------------

### Restart PostgreSQL Service (Linux)

Source: https://docs.pgxman.com/using_extensions

On Linux systems, PostgreSQL must be restarted to recognize newly installed extensions. This command initiates the restart process.

```sh
sudo service postgresql restart
```

--------------------------------

### Upgrade Specific pgvector Version for PostgreSQL 15 with Sudo

Source: https://docs.pgxman.com/cli/pgxman_upgrade

This command upgrades a specific version of pgvector for PostgreSQL 15 and uses `sudo` for elevated privileges. This is useful when installing extensions in system-wide directories.

```bash
pgxman upgrade pgvector=0.5.0 --pg 15 --sudo
```

--------------------------------

### pgxman init Help Flags

Source: https://docs.pgxman.com/cli/pgxman_init

Standard help flag for the init command.

```bash
  -h, --help   help for init
```

--------------------------------

### pgxman init Command

Source: https://docs.pgxman.com/cli/pgxman_init

Use this command to create a new buildkit YAML file for your PostgreSQL extension. The file specifies the build and packaging process.

```bash
pgxman init [flags]
```

--------------------------------

### Connect to Postgres

Source: https://docs.pgxman.com/quickstart

Connect to your Postgres database. The command varies for MacOS and Linux.

```bash
# mac - connect to the container pgxman creates
$ psql postgres://postgres:pgxman@127.0.0.1/postgres

# linux - restart postgres so it picks up newly installed extensions, then connect
$ sudo service postgresql restart
$ sudo -u postgres psql
```

--------------------------------

### pgxman CLI Options

Source: https://docs.pgxman.com/cli/pgxman

Lists the available command-line options for the pgxman tool. Use --debug for verbose logging or specify a custom registry URL.

```bash
      --debug             enable debug logging
  -h, --help              help for pgxman
      --registry string   registry URL (default "https://registry.pgxman.com/v1")
```

--------------------------------

### Build the extension locally using pgxman

Source: https://docs.pgxman.com/building_an_extension

Use this command to build your PostgreSQL extension based on the `extension.yaml` file. The output packages will be placed in the `out` directory.

```sh
pgxman build -f extension.yaml
```

--------------------------------

### Create PostgreSQL Extension

Source: https://docs.pgxman.com/using_extensions

After connecting to your desired PostgreSQL database, use this command to load an extension. The extension name might differ from the pgxman package name.

```sql
CREATE EXTENSION extension_name;
```

--------------------------------

### pgxman build Command Usage

Source: https://docs.pgxman.com/cli/pgxman_build

Basic usage of the pgxman build command. Specify the path to the extension manifest file using the -f flag.

```bash
pgxman build [flags]
```

--------------------------------

### Upgrade from Local Debian Package

Source: https://docs.pgxman.com/cli/pgxman_upgrade

Upgrade an extension using a local Debian package file. Provide the full path to the .deb file.

```bash
pgxman upgrade /PATH_TO/postgresql-15-pgxman-pgvector_0.5.0_arm64.deb
```

--------------------------------

### pgxman build Options

Source: https://docs.pgxman.com/cli/pgxman_build

Available options for the pgxman build command, including cache configuration, parallel build settings, and manifest file path.

```bash
      --cache-from stringArray   External cache sources. The value is passed to docker buildx build --cache-from.
      --cache-to stringArray     Cache export destinations. The value is passed to docker buildx build --cache-to.
  -f, --file string              Path to the extension manifest file (default "extension.yaml")
  -h, --help                     help for build
      --no-cache                 Do not use cache when building the image. The value is passed to docker buildx build --no-cache.
      --parallel int             Number of parrallel builds to run (default 2)
  -s, --set stringToString       Override values in the extension.yaml file in the format of --set KEY=VALUE, e.g. --set version=1.0.0 --set arch=[amd64,arm64] --set pgVersions=[10,11,12] (default [])
```

--------------------------------

### Upgrade Local Debian Package in Container

Source: https://docs.pgxman.com/cli/pgxman_container_upgrade

Upgrade a PostgreSQL extension by providing the path to a local Debian package file within a container.

```bash
pgxman container upgrade /PATH_TO/postgresql-15-pgxman-pgvector_0.5.0_arm64.deb
```

--------------------------------

### Connect to PostgreSQL Container using psql

Source: https://docs.pgxman.com/container

Connect to a running PostgreSQL container using the psql client. The connection string includes the username, password, host, port, and database name, all set to 'pgxman' by default. The port is determined by the PostgreSQL version.

```sh
psql postgres://pgxman:pgxman@127.0.0.1:15432/pgxman
```

--------------------------------

### Upgrade Multiple Extensions for PostgreSQL 15

Source: https://docs.pgxman.com/cli/pgxman_upgrade

Upgrade multiple extensions, such as pgvector and postgis, to specific versions for PostgreSQL 15. List each extension with its version separated by spaces.

```bash
pgxman upgrade pgvector=0.5.0 postgis=3.3.3 --pg 15
```

--------------------------------

### pgxman init Inherited Flags

Source: https://docs.pgxman.com/cli/pgxman_init

Flags inherited from parent commands, including debug logging and registry URL configuration.

```bash
      --debug             enable debug logging
      --registry string   registry URL (default "https://registry.pgxman.com/v1")
```

--------------------------------

### pgxman doctor Help Flag

Source: https://docs.pgxman.com/cli/pgxman_doctor

Displays help information for the doctor command.

```bash
  -h, --help   help for doctor
```

--------------------------------

### View Running pgxman Containers

Source: https://docs.pgxman.com/container

List all running Docker containers and filter for those related to pgxman. This helps in identifying the names of running containers.

```sh
docker ps | grep pgxman
```

--------------------------------

### Configure BuildKit Overrides for PostgreSQL Versions

Source: https://docs.pgxman.com/spec/buildkit

Use this configuration to tailor BuildKit settings for specific PostgreSQL versions. Define custom `version` and `source` for each targeted PostgreSQL version.

```yaml
pgVersions:
  - "13"
  - "14"
  - "15"
overrides:
  pgVersions:
    "13":
      version: "1.2.3"
      source: https://github.com/org/repo/archive/refs/tags/v1.2.3.tar.gz
    "14":
      version: "2.3.4"
      source: https://github.com/org/repo/archive/refs/tags/v2.3.4.tar.gz
```

--------------------------------

### Upgrade Multiple Extensions for PostgreSQL

Source: https://docs.pgxman.com/cli/pgxman_container_upgrade

Upgrade multiple PostgreSQL extensions with specific versions (e.g., pgvector 0.5.0 and postgis 3.3.3) for a given PostgreSQL version (e.g., 15) in a container.

```bash
pgxman container upgrade pgvector=0.5.0 postgis=3.3.3 --pg 15
```

--------------------------------

### View Docker Volumes for pgxman

Source: https://docs.pgxman.com/container

List all Docker volumes and filter for those associated with pgxman. This is useful for identifying where container data is stored.

```sh
docker volume ls | grep pgxman
```

--------------------------------

### Connect to PostgreSQL Container from within Docker

Source: https://docs.pgxman.com/container

Access the psql client directly from within the running PostgreSQL container. This is useful for executing commands in the container's environment.

```sh
docker exec -it pgxman_runner_15 psql -U pgxman
```

--------------------------------

### pgxman doctor Command Synopsis

Source: https://docs.pgxman.com/cli/pgxman_doctor

Use this command to check your system for potential problems. It will exit with a non-zero status if any issues are detected.

```bash
pgxman doctor [flags]
```

--------------------------------

### Tear Down Multiple PostgreSQL Containers

Source: https://docs.pgxman.com/cli/pgxman_container_teardown

Execute this command to remove multiple PostgreSQL playground containers simultaneously. All specified containers and their data will be purged.

```bash
pgxman container teardown pgxman_runner_15 pgxman_runner_16
```

--------------------------------

### Remove pgxman configuration directory

Source: https://docs.pgxman.com/uninstalling_pgxman

Use this command to remove the pgxman configuration directory from your system. This action is irreversible.

```shell
rm -r ~/.config/pgxman
```

--------------------------------

### Upgrade Latest pgvector in Container

Source: https://docs.pgxman.com/cli/pgxman_container_upgrade

Use this command to upgrade the latest available version of the pgvector extension within a container.

```bash
pgxman container upgrade pgvector
```

--------------------------------

### Tear Down PostgreSQL Container

Source: https://docs.pgxman.com/cli/pgxman_container_teardown

Use this command to remove a specific PostgreSQL playground container. This action will also purge all associated data.

```bash
pgxman container teardown pgxman_runner_15
```

--------------------------------

### Upgrade Latest pgvector for PostgreSQL 15

Source: https://docs.pgxman.com/cli/pgxman_upgrade

This command upgrades the latest pgvector extension for a specific PostgreSQL version, in this case, PostgreSQL 15. The `--pg` flag specifies the target PostgreSQL version.

```bash
pgxman upgrade pgvector --pg 15
```

--------------------------------

### Upgrade Specific pgvector Version for PostgreSQL 15

Source: https://docs.pgxman.com/cli/pgxman_upgrade

Upgrade a specific version of pgvector (e.g., 0.5.0) for PostgreSQL 15. Specify the version using the NAME=VERSION format.

```bash
pgxman upgrade pgvector=0.5.0 --pg 15
```

--------------------------------

### Upgrade pgvector for Specific PostgreSQL Version

Source: https://docs.pgxman.com/cli/pgxman_container_upgrade

Upgrade the latest pgvector extension for a specific PostgreSQL version (e.g., 15) in a container.

```bash
pgxman container upgrade pgvector --pg 15
```

--------------------------------

### Stop a pgxman Container

Source: https://docs.pgxman.com/container

Stop a specific pgxman container using the docker stop command. Replace NAME with the actual container name (e.g., pgxman_runner_15).

```sh
docker stop pgxman_runner_15
```

--------------------------------

### Upgrade Specific pgvector Version for PostgreSQL

Source: https://docs.pgxman.com/cli/pgxman_container_upgrade

Upgrade a precise version of pgvector (e.g., 0.5.0) for a specific PostgreSQL version (e.g., 15) within a container.

```bash
pgxman container upgrade pgvector=0.5.0 --pg 15
```

--------------------------------

### Teardown pgxman Container

Source: https://docs.pgxman.com/container

Completely remove a pgxman container, including its image, volume, and configuration. This action will delete all stored data within the container's database.

```sh
pgxman c teardown pgxman_runner_15
```
Tokens:
Raw