| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | David Ford <david(at)blue-labs(dot)org> |
| Cc: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: PostGres Doubt |
| Date: | 2002-06-18 14:39:02 |
| Message-ID: | 26192.1024411142@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
David Ford <david(at)blue-labs(dot)org> writes:
> heakin=> \z
> Access privileges for database "heakin"
> Table | Access privileges
> -------------------+-------------------
> interviewers |
> heakin=> grant select,insert,update on interviewers to heakin;
> GRANT
> heakin=> \z
> Access privileges for database "heakin"
> Table | Access privileges
> -------------------+--------------------
> interviewers | {=,heakin=arwdRxt}
I take it heakin is the owner of the table in question. As such,
he implicitly has all privileges --- the initial null privilege list
is a shorthand for what you see explicitly in the second case.
The GRANT man page in current development sources has an example about
this; see the Notes section of
http://developer.postgresql.org/docs/postgres/sql-grant.html
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2002-06-18 14:45:12 | Re: FATAL 2: InitRelink(logfile 0 seg 173) failed: No such file or directory |
| Previous Message | Tom Lane | 2002-06-18 14:34:04 | Re: [HACKERS] PERFORM effects FOUND patch (Was: I must be |