From: | Guillaume LELARGE <guillaume(dot)lelarge(at)gmail(dot)com> |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Subject: | Re: Something I don't understand with the use of schemas |
Date: | 2005-12-12 19:46:59 |
Message-ID: | 200512122047.00218.guillaume.lelarge@gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Le Samedi 10 Décembre 2005 17:43, vous avez écrit :
> Guillaume LELARGE <guillaume(dot)lelarge(at)gmail(dot)com> writes:
> > Apparently, I can rename all schemas, even system schemas !
> > metier=# alter schema pg_catalog rename to foobar;
> > ALTER SCHEMA
>
> If you are superuser, you can do anything you want, up to and including
> breaking the system irretrievably. Compare "rm -rf /" on Unix. We
> won't be putting training wheels on superuser status for the same
> reasons that no one finds it a good idea to restrict root's abilities.
>
Seems pretty fair.
I've made more tests on schemas. I'm able to drop information_schema and
public schemas but I can't drop pg_catalog and pg_toast. It makes me think
that only pg_* are system schemas and that public and information_schema are
public schemas. Am I right on this one ?
--
Guillaume.
<!-- http://abs.traduc.org/
http://lfs.traduc.org/
http://traduc.postgresqlfr.org/ -->
From | Date | Subject | |
---|---|---|---|
Next Message | Jim C. Nasby | 2005-12-12 20:05:03 | Re: Something I don't understand with the use of schemas |
Previous Message | Mike G. | 2005-12-12 19:30:54 | PgInstaller error on upgrade |