From: | Bill Studenmund <wrstuden(at)netbsd(dot)org> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Hiroshi Inoue <Inoue(at)tpf(dot)co(dot)jp>, Peter Eisentraut <peter_e(at)gmx(dot)net>, PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: RFD: schemas and different kinds of Postgres objects |
Date: | 2002-01-31 16:31:03 |
Message-ID: | Pine.NEB.4.33.0201310828190.29090-100000@vespasia.home-net.internetconnect.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Wed, 30 Jan 2002, Tom Lane wrote:
> Hiroshi Inoue <Inoue(at)tpf(dot)co(dot)jp> writes:
> > For example, doesn't 'DROP table a_table' drop the
> > a_table table in a schema in the *path* if there's
> > no a_table table in the current schema ?
>
> Sure. And that's exactly what it should do, IMHO.
> Otherwise the notion that you can ignore your private
> schema (at the front of the path) if you're not using
> it falls down. Also, we wouldn't be able to implement
> temp tables via a backend-local schema at the front of
> the path.
Well, I disagree on this one. :-) I'd vote drop should need a specific
schema if it's not the current one. But I won't push the point. :-)
> Any security concerns here should be addressed by putting
> ACLs on the schemas you don't want altered; not by contorting
> the notion of a search path to work for some operations and
> not others.
I'm not so concerned about security as being sure of operator intent. ACLs
address security (and should be used), but they don't address making sure
you delete exactly what you wanted.
Take care,
Bill
From | Date | Subject | |
---|---|---|---|
Next Message | Oleg Bartunov | 2002-01-31 16:33:28 | Re: postgresql under Windows is slow |
Previous Message | Bill Studenmund | 2002-01-31 16:28:10 | Re: RFD: schemas and different kinds of Postgres objects |