Specifies the Postgres Pro role that is allowed to use DuckDB execution and manage secrets. If the specified role does not exist when running CREATE EXTENSION pgpro_axe, this role is created automatically.

Default value: "" — superuser only.

Access: Requires a restart.

Disables storages for pgpro_axe.

Possible values:

By default, the local storage is disabled:

  postgres=> SHOW duckdb.disabled_filesystems;
  duckdb.disabled_filesystems
  -----------------------------
  LocalFileSystem
  (1 row)

You can specify multiple storages by separating their names with commas without spaces:

  postgres=# ALTER SYSTEM SET duckdb.disabled_filesystems TO 'LocalFileSystem,HTTPFileSystem';
  ALTER SYSTEM
  -- after server reboot --
  postgres=# SHOW duckdb.disabled_filesystems;
    duckdb.disabled_filesystems
  --------------------------------
  LocalFileSystem,HTTPFileSystem
  (1 row)

Access: Superuser only.

Specifies whether known DuckDB extensions can be automatically installed into pgpro_axe when an analytical query requires them.

Possible values:

Only extensions that DuckDB marks as auto-installable can be installed automatically. You can install extensions manually using the duckdb.install_extension stored procedure.

If this parameter is set to true, known extensions are also automatically loaded into pgpro_axe.

Default value: true.

Access: Superuser only.

Specifies whether known extensions can be automatically loaded into pgpro_axe when an analytical query requires them.

Possible values:

Only loads extensions that are already installed into pgpro_axe. You can also install extensions automatically by setting the duckdb.autoinstall_known_extensions configuration parameter to true.

Default value: true.

Access: Superuser only.

Specifies whether community extensions can be installed.

Possible values:

Default value: false.

Access: Superuser only.

Allows DuckDB execution inside Postgres Pro functions.

Possible values:

Default value: false.

Access: Superuser only.

Allows DuckDB to access external resources (e.g., HTTP, S3).

Possible values:

Default value: true.

Access: Superuser only.

The maximum memory that pgpro_axe can use to process a single analytical query, in megabytes. For example: 4096 (4 GB), 8192 (8 GB), or 1024 (1 GB). When set to zero, 80% of RAM is used. You can configure this parameter for each session.

Default value: 4096 (4 GB).

Access: Superuser only.

The maximum number of threads (CPU cores) that Postgres Pro can use to process a single query. You can configure this parameter for each session.

Default value: -1 — the value is equal to the number of CPU cores.

Access: Superuser only.

The maximum number of Postgres Pro workers used for a single Postgres Pro scan. This parameter is similar to max_parallel_workers_per_gather.

Default value: 2.

Access: All roles.

The maximum number of DuckDB threads used for a single Postgres Pro scan. This parameter controls parallelism within DuckDB when scanning Postgres Pro tables.

Default value: 2.

Access: All roles.

Converts NUMERIC types with unsupported precision/scale to DOUBLE instead of throwing an error.

Possible values:

DuckDB supports NUMERIC/DECIMAL with precision 1-38 and scale 0-38 (where scale ≤ precision). For NUMERICs outside these limits:

Default value: false.

Access: All roles.

Allows mixed transactions between DuckDB and Postgres Pro.

Possible values:

Default value: false.

Access: All roles.

Specifies whether Postgres Pro AXE uses Postgres Pro snapshots for queries.

Possible values:

If this parameter is set to false, Postgres Pro snapshots are not used, which prevents Postgres Pro AXE from holding the transaction horizon. In this case, queries that work with heap tables fail with an error. For more information, refer to Section 26.4.

Default value: true.

Access: All roles.

Specifies whether SAVEPOINT commands are allowed when DuckDB execution is used.

Possible values:

pgpro_axe does not support savepoints, so any changes made to DuckDB tables between SAVEPOINT and ROLLBACK TO SAVEPOINT commands cannot be rolled back. By default, Postgres Pro AXE outputs an error when a SAVEPOINT command is executed. If this parameter is set to true, Postgres Pro AXE ignores SAVEPOINT commands instead of outputting an error. Postgres Pro still processes SAVEPOINT and ROLLBACK TO SAVEPOINT commands for heap tables, so changes to heap tables are rolled back as expected.

Default value: false.

Access: All roles.

Specifies the directory for temporary files that pgpro_axe creates when the available RAM is insufficient for executing analytical queries. By default, temporary files are stored in the DataDir/pg_duckdb/temp directory.

Default value: DataDir/pg_duckdb/temp.

Access: Superuser only.

The maximum amount of data that can be stored in the DuckDB temporary directory. This parameter allows preventing runaway analytical queries from consuming all available disk space.

Default value: "" — no limit is enforced.

Access: Superuser only.

Specifies the directory where DuckDB stores its extensions. By default, extensions are stored under the Postgres Pro directory (DataDir/pg_duckdb/extensions). This is useful for managing the extension storage or sharing extensions across multiple Postgres Pro instances.

Default value: "DataDir/pg_duckdb/extensions".

Access: Superuser only.

Enables or disables the cache for Parquet files from S3 storages. When enabled, Parquet files are cached in RAM to reduce storage read I/O requirements. For more information, refer to Section 20.3.

Possible values:

Default value: true.

Access: Superuser only.

Allows DuckDB to load extensions with invalid or missing signatures. This is mostly useful for the development of DuckDB extensions.

Possible values:

Default value: false.

Access: Superuser only.

Logs the EXPLAIN plan of a Postgres Pro scan at the NOTICE log level. This parameter is useful for debugging query execution and understanding how DuckDB interacts with Postgres Pro tables.

Possible values:

Default value: false.

Access: All roles.