> >Certainly, I've
> >tried "grant select on database mydatabase to user myuser"; it doesn't
> >work, because "select" is not a database-level privilege.
> Sorry, you're right on that one. I misread it. However, it shouldn't
> be too hard to write a script, either in a procedural language or higher
> level, to pull the existing table names from pg_class and invokes the
> GRANT command for you "trusted" user on each.
That could be done, but my big worry is all the non-table components of
a database such as views and functions -- I'd hate to accidentally be
creating incomplete dumps simply because I forgot to programmatically
assign permissions on my operator classes (or whatever).
So I'd still like to see a "read" or "readonly" permission at the database
level, but until then, it seems the best bet is to use an overprivileged
trusted account for my backups. The security risks can be managed, and
they are worth it to make sure I've got a complete and cohesive dump.
