User Has no Permission for Table

Evan Hicks

The Problem

If you come across the error user <user> has no permission for table <table> when trying to run queries using a certain table, you are missing the correct permissions in the Postgres database. A common reason for this is creating a table using the postgres default user, then trying to access said table using a different user. The creator of a table has to explicitly grant other users permission to query that table.

The Solution

If these permissions are the problem, you can change the ownership of a table using a SQL query (note you’ll need to run this query as the owner of the table or a superuser).

ALTER TABLE `my_table` OWNER TO `new_owner`;

However, the more common solution is to use the GRANT keyword to give other users the permission you want on the table. The following query will grant SELECT access to another user.

GRANT SELECT ON `my_table` to `bob`;

This will allow the bob user to run SELECT queries on my_table. You can read about the full specification for GRANT here: []

Further Reading

If you’re looking to get a deeper understanding of how database application monitoring works, take a look at the following articles:

Loved by over 4 million developers and more than 90,000 organizations worldwide, Sentry provides code-level observability to many of the world’s best-known companies like Disney, Peloton, Cloudflare, Eventbrite, Slack, Supercell, and Rockstar Games. Each month we process billions of exceptions from the most popular products on the internet.

Share on Twitter
Bookmark this page
Ask a questionJoin the discussion

Related Answers

A better experience for your users. An easier life for your developers.

© 2024 • Sentry is a registered Trademark
of Functional Software, Inc.