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: "" — superusers 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)

To specify multiple storages, separate 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 extensions can be automatically installed when a DuckDB query depends on them.

Possible values:

By default, only superusers can execute duckdb.install_extension and duckdb.autoload_extension. This prevents other users from installing extensions that can have security implications or interfere with database operation.

Users can only use extensions that DuckDB marked as auto-installable. To restrict the use of these extensions to a specific list of allowed extensions, set duckdb.autoinstall_known_extensions to false.

Default value: true.

Access: Superuser-only.

Specifies whether known extensions can be automatically loaded when a DuckDB query depends on them.

Default value: true.

Access: Superuser-only

Specifies whether community extensions can be installed.

Default value: false.

Access: Superuser-only.

Allows DuckDB execution inside Postgres Pro functions.

Default value: false.

Access: Superuser-only.

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

Default value: true.

Access: Superuser-only.