| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
| Cc: | Bill Cunningham <billc(at)ballydev(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, pgsql-interfaces <pgsql-interfaces(at)postgresql(dot)org> |
| Subject: | Re: [HACKERS] Schemas: status report, call for developers |
| Date: | 2002-06-08 16:03:07 |
| Message-ID: | 14093.1023552187@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-interfaces |
Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> If I remove public create access to public, can the super user or db
> owner still create tables?
Superusers can always do whatever they want.
The DB owner (assume he's not a superuser) has no special privileges
w.r.t. the public schema at the moment. We could perhaps put in a
kluge to change this, but it would definitely be a kluge --- I don't
see any clean way to make the behavior different.
One possible approach would be for a superuser to change the ownership
of public to be the DB owner.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2002-06-08 16:05:37 | Re: Roadmap for a Win32 port |
| Previous Message | Bruce Momjian | 2002-06-08 15:57:07 | Re: Roadmap for a Win32 port |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Franco | 2002-06-08 18:37:29 | error reporting |
| Previous Message | Bruce Momjian | 2002-06-08 15:12:02 | Re: [HACKERS] Schemas: status report, call for developers |