Register a PostgreSQL provider

Register PostgreSQL storage and compute with Redis Feature Form.

Register a postgres provider when Redis Feature Form should discover PostgreSQL tables, run structured query language (SQL) transformations, or materialize training sets and feature-view data in PostgreSQL.

The provider fills the offline-store and compute roles. It doesn't provide online serving. A serving feature view also needs a supported online-store provider.

Distinguish data from Feature Form state

A PostgreSQL data provider holds or computes customer feature data. It is separate from a PostgreSQL state backend that stores Feature Form's control-plane state. Use separate databases, credentials, and schemas for these purposes unless your deployment has another isolation policy.

Before you begin

Make sure you have:

• A Feature Form workspace.
• A PostgreSQL hostname and database reachable from the Feature Form server.
• A PostgreSQL username and password.
• A secret provider for the password reference.
• Permission to read the required source tables and create managed outputs.

The Python example uses this workspace-scoped provider client:

import featureform as ff

client = ff.Client.from_env()
providers = client.providers("<workspace-id>")

Register PostgreSQL

from featureform.types import EnvSecretRef, PostgresConfig, ProviderType, SSLMode

providers.register(
    name="<postgres-provider-name>",
    provider_type=ProviderType.POSTGRES,
    config=PostgresConfig(
        host="<postgres-host>",
        port=5432,
        database="<database-name>",
        username="<username>",
        password_secret=EnvSecretRef(name="PG_PASSWORD"),
        ssl_mode=SSLMode.REQUIRE,
    ),
)

ff provider register <postgres-provider-name> \
  --workspace <workspace-id> \
  --type postgres \
  --pg-host <postgres-host> \
  --pg-port 5432 \
  --pg-database <database-name> \
  --pg-username <username> \
  --pg-password-secret env:PG_PASSWORD \
  --pg-ssl-mode require

The environment reference is resolved by the Feature Form server. Replace it with a reference to another registered secret backend when appropriate.

The current public provider supports password authentication. Don't assume that internal or database-specific identity authentication methods are available through ff.

Choose connection security

The Python ssl_mode field and the --pg-ssl-mode CLI option accept:

• disable
• allow
• prefer (default)
• require
• verify-ca
• verify-full

The public registration contract doesn't accept explicit client-certificate or root-certificate fields. Configure the required trust material in the Feature Form deployment environment.

Grant workload permissions

The registration health check connects to PostgreSQL and queries its version. It proves connectivity and authentication, but it doesn't prove that later workloads can read or write their tables.

Feature Form-managed transformation tables use the ff_transforms schema through the documented gRPC registration path. The server creates the schema when required. This path doesn't expose a custom managed-schema value.

Understand supported workloads

Verify registration

ff provider get <postgres-provider-name> --workspace <workspace-id>
ff provider list --workspace <workspace-id>

In Python, use providers.get("<postgres-provider-name>") or providers.list().

Update safely

Before a forced update or deletion, review datasets, transformations, training sets, feature views, and other references to the provider. The usage check doesn't detect every indirect reference.

Troubleshoot registration