Limitations

Postgres developers didn’t implement the backup routines with data deduplication in mind, therefore the results may not be ideal. However the cluster command may be used at times to enhance the deduplication ratio as it physically reorders the data according to the index information. However, notice that this command requires exclusive lock while it is running, and also may quite heavy on CPU and I/O resources.
In PITR mode, each Job should contain a single Cluster. To backup multiple clusters installed on the same client, multiple jobs are needed.
In Dump mode, PostgreSQL version 8.3 and earlier may not support automatic restore through the Bacula Enterprise PostgreSQL plugin. The pg_restore program can produce the following error: WARNING: invalid creation date in header. In this case, it is needed to restore data to a directory, and run pg_restore in a terminal.
The clean option requires PostgreSQL 9.1 or later.
The backup will include all files in the data directory and tablespaces, including the configuration files and any additional files placed in the directory by third parties, except certain temporary files managed by PostgreSQL. But only regular files and directories are copied, except that symbolic links used for tablespaces are preserved. Symbolic links pointing to certain directories known to PostgreSQL are copied as empty directories. Other symbolic links and special device files are skipped. See: https://www.postgresql.org/docs/current/protocol-replication.html for the precise details.
The restart command has limitations with plugins, as it initiates the Job from scratch rather than continuing it. Bacula determines whether a Job is restarted or continued, but using the restart command will result in a new Job.