Control: tag -1 moreinfo
I'm looking through old bug reports for the bacula package.
You reported wrong/missing access privileges after restoring an old
catalog backup and then manually upgrading it by running the upgrade
You noted that some tables have empty access privileges, while most had
specific privileges for bacula.
On current installations, the column "Access privileges" in the \dp
output of psql is empty, yet everything works, including running the
upgrade scripts as the bacula user. Did you actually have problems after
your restore+upgrade and before further changing the access privileges?