Known issues and limitations#

These known issues and limitations are in the current release of EDB Postgres Distributed for Kubernetes.

Postgres major version upgrades#

This version of EDB Postgres Distributed for Kubernetes doesn’t support major version upgrades of Postgres.

Data migration#

This version of EDB Postgres Distributed for Kubernetes doesn’t support declarative import of data from other Postgres databases. To migrate schemas and data, you can use traditional Postgres migration tools such as EDBLoader or Migration Toolkit / Replication Server . You can also use pg_dump ... on the source database and pipe the command’s output to your target database with psql -c .

Connectivity with PgBouncer#

EDB Postgres Distributed for Kubernetes doesn’t support using PgBouncer to pool client connection requests. This limitation applies to both the open-source and EDB versions of PgBouncer.

Backup operations#

To configure an EDB Postgres Distributed for Kubernetes environment, you must apply a PGDGroup YAML object to each Kubernetes cluster. Applying this object creates all necessary services for implementing a distributed architecture.

If you added a spec.backup section to this PGDGroup object with the goal of setting up a backup configuration, the backup will fail unless you also set the spec.backup.cron.schedule value.

Error output example:

The PGDGroup "region-a" is invalid: spec.backup.cron.schedule: Invalid value: "": Empty spec string

Workaround#

To work around this issue, add a spec.backup.cron.schedule section with a schedule that meets your requirements, for example:

spec:
  instances: 3
  proxyInstances: 2
  pgd:
    parentGroup:
      create: true
      name: world
  backup:
    configuration:
      barmanObjectStore:
        ...
    cron:
      suspend: false
      immediate: true
      schedule: "0 */5 * * * *"