# How do I fix the pgvector "could not open extension control file" error?

The PostgreSQL extension `pgvector` sometimes returns the following error when you run the command `CREATE EXTENSION pgvector;`:

```
ERROR: could not open extension control file "/usr/pgsql-16/share/extension/pgvector.control": No such file or directory
```

This is because, despite the project being named `pgvector`, the creation command requires that you use `vector` as the extension name, like so:

```sql

CREATE EXTENSION vector;
```

For more details, see the [`pgvector` documentation](https://github.com/pgvector/pgvector).

## Related Topics

[How do I fix the pg_dumpall "permission denied for table pg_authid" error?](https://docs.digitalocean.com/support/how-do-i-fix-the-pg_dumpall-permission-denied-for-table-pg_authid-error/index.html.md): Add the –no-role-passwords flag to the pg\_dumpall command.

[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.

[How do I fix the "Authentication Failed" error when connecting to PostgreSQL?](https://docs.digitalocean.com/support/how-do-i-fix-the-authentication-failed-error-when-connecting-to-postgresql/index.html.md): Verify the database cluster, username, and password.