# How do I fix the pg\_dumpall "permission denied for table pg\_authid" error? The `pg_dumpall: error: query failed: ERROR: permission denied for table pg_authid` error typically occurs when you do not have the necessary privileges to access the `pg_authid` table, which stores information about database user roles and their authentication. The `doadmin` user lacks permission to access the `pg_authid` table; however, it does have access to all other necessary system tables and information required for the dump. To fix this issue, include the `--no-role-passwords` flag in the `pg_dumpall` command. For example: ```shell pg_dumpall -h -U -p 25060 -Fc --no-role-passwords > ``` Specifying the `--no-role-passwords` flag excludes role passwords from the dump. This allows the process to proceed without `pg_authid` table permission errors and without comprising the security of role passwords. To learn about the `pg_dumpall` command flags, see our [guide on exporting a PostgreSQL database](https://docs.digitalocean.com/products/databases/postgresql/how-to/import-databases/index.html.md#export-an-existing-database). ## Related Topics [How do I fix a "permission denied for schema public" error in PostgreSQL?](https://docs.digitalocean.com/support/how-do-i-fix-a-permission-denied-for-schema-public-error-in-postgresql/index.html.md): Update the user’s privileges to `CREATE`, `USAGE`, or `ALL` on the public schema. [How do I fix the pgvector "could not open extension control file" error?](https://docs.digitalocean.com/support/how-do-i-fix-the-pgvector-could-not-open-extension-control-file-error/index.html.md): Use the command CREATE EXTENSION vector; instead of pgvector. [How do I fix the pg_dump "aborting because of server version mismatch" error?](https://docs.digitalocean.com/support/how-do-i-fix-the-pg_dump-aborting-because-of-server-version-mismatch-error/index.html.md): Resolve the pg\_dump server version mismatch by upgrading pg\_dump, matching it to the server version, or using a third-party backup tool.