On Feb 17, 2007, at 12:12 PM, John D. Burger wrote:
A better approach is to write a plpgsql function that assembles and
EXECUTEs the required GRANT commands.
Okay, thanks - guess it's time to learn some real plpgsql control
structures.
You can find some help here:
http://pgedit.com/tip/
Tom Lane wrote:
How dangerous is it to UPDATE pg_class
directly, perhaps copying the relacl column for a table that I've
done by hand with GRANT.
You can do it, and it will seem to work. However, unless you also
make
entries in pg_shdepend, bad things will happen if you later drop
any of
"John D. Burger" <[EMAIL PROTECTED]> writes:
> How dangerous is it to UPDATE pg_class
> directly, perhaps copying the relacl column for a table that I've
> done by hand with GRANT.
You can do it, and it will seem to work. However, unless you also make
entries in pg_shdepend, bad things will h
Alvaro Herrera wrote:
If I am reading the (7.4) docs correctly, privileges can be granted
only with respect to tables that exist at the time the GRANT command
is given
Yes.
In fact, I have to individually grant access to each table, and any
associated sequences, yes? How dangerous is it
John D. Burger wrote:
> If I am reading the (7.4) docs correctly, privileges can be granted
> only with respect to tables that exist at the time the GRANT command
> is given - there is no
>
> GRANT ALL ON * TO PUBLIC
>
> or some such that would result in subsequently created tables having
If I am reading the (7.4) docs correctly, privileges can be granted
only with respect to tables that exist at the time the GRANT command
is given - there is no
GRANT ALL ON * TO PUBLIC
or some such that would result in subsequently created tables having
public privileges.
Is this so?
