GRANT
ing ALL
permissions for public to the database is mostly redundant (as public has connect, temporary by default, so you'd only be adding CREATE
which you probably don't want to do). You probably expected a GRANT ALL
on the database to result in a recursive GRANT ALL
to contained schemas and tables. GRANT
is not recursive, so this doesn't happen; a GRANT ALL
on a database just grants CONNECT
and TEMPORARY
rights to the database, with no effect on contained schemas and tables.
The default GRANT
s are, from the docs on GRANT:
PostgreSQL grants default privileges on some types of objects to
PUBLIC. No privileges are granted to PUBLIC by default on tables,
columns, schemas or tablespaces. For other types, the default
privileges granted to PUBLIC are as follows: CONNECT and CREATE TEMP
TABLE for databases; EXECUTE privilege for functions; and USAGE
privilege for languages. The object owner can, of course, REVOKE both
default and expressly granted privileges. (For maximum security, issue
the REVOKE in the same transaction that creates the object; then there
is no window in which another user can use the object.) Also, these
initial default privilege settings can be changed using the ALTER
DEFAULT PRIVILEGES command.
So you can see you don't need to GRANT
anything on the database unless you want the user to be able to create schemas, etc. You need to:
GRANT USAGE ON SCHEMA myschema TO theuser;
for any schema other than public
. CREATE
can be granted if you want the user to be able to make tables, views, etc.
GRANT SELECT, INSERT, UPDATE, DELETE ON TABLE sometable TO theuser;
for tables. I've omitted the TRUNATE
, REFERENCES
and TRIGGER
rights as you probably don't want to grant them.
GRANT USAGE ON SEQUENCE sometable_somecolumn_seq TO theuser;
for any sequences that are used in table defaults, either explicitly or via a SERIAL
or BIGSERIAL
column.
... etc. See the manual for GRANT
linked above for full definitions of what the privileges do, which are available on which objects, etc. Take note of the wildcard ALL TABLES
and ALL SEQUENCES
options.
If this seems like too much hassle to do for each table, view, schema, sequence, etc, you can in Pg 9.1 and above use ALTER DEFAULT PRIVILEGES
to change the default GRANT
s on new objects.
To troubleshoot, I would start by looking at the output of SELECT current_user;
and SHOW search_path;
. Also, the output of \dp termin
in psql.
My suspicion here is that you are stumbling over mixed case identifiers. The error message mentions a table
Map
Notice the capital letter M
. Are you sure there is no mix-up with another table named map
(lower case)?
Are PostgreSQL column names case-sensitive?
(Or, in another schema coming earlier in the search_path
?)
Best Answer
You should log in as the table owner (the user you used to create the tables) and then grant the necessary privileges to your user:
If you want to do that for all tables, you can use:
Or maybe you created them as the superuser, but your regular user should be the real owner, then you should do: