Skip site navigation (1) Skip section navigation (2)

Re: ALTER TABLE OWNER: change indexes

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Yury Bokhoncovich <byg(at)center-f1(dot)ru>
Cc: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>,PostgreSQL-patches <pgsql-patches(at)postgresql(dot)org>,Peter Eisentraut <peter_e(at)gmx(dot)net>,Neil Conway <nconway(at)klamath(dot)dyndns(dot)org>
Subject: Re: ALTER TABLE OWNER: change indexes
Date: 2002-03-12 05:40:49
Message-ID: 28130.1015911649@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-patches
Yury Bokhoncovich <byg(at)center-f1(dot)ru> writes:
> 2) I (admin) have a few tables as owner and wanna give another user
> (programmer) ability to create/drop any necessary indices. At the same
> time I do not wanna give him (her) a chance to drop/alter the table
> itself.

But keep in mind that CREATE UNIQUE INDEX does alter the table, in
the sense that subsequent operations may fail where they'd not have
done before.  Conversely, dropping a unique index may allow logically
invalid data to be inserted.  Also, dropping an index may cause important
operations to take vastly longer than they're expected to.  So giving
away the right to manipulate indexes is at the very least an opening
to denial-of-service problems.

In any case, what you are really suggesting here is that we offer a
grantable "right to create/drop indexes" on a *table*.  Dangerous or
not, it could be useful.  But it has nothing that I can see to do with
a notion of ownership of the indexes themselves; there's still no visible
reason to consider the indexes to have ownership independent of the
table they're on.

			regards, tom lane

In response to

Responses

pgsql-patches by date

Next:From: Paul EggertDate: 2002-03-12 05:59:30
Subject: Re: support for POSIX 1003.1-2001 hosts
Previous:From: Yury BokhoncovichDate: 2002-03-12 04:51:14
Subject: Re: ALTER TABLE OWNER: change indexes

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group