Re: DROP OWNED BY

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
Cc: Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: DROP OWNED BY
Date: 2005-08-13 14:09:35
Message-ID: 6525.1123942175@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> writes:
> I'm working on the promised DROP OWNED patch, and just noticed that it
> needs modifications to the Grant/Revoke machinery that are too invasive
> to consider for 8.1; the problem is that ExecuteGrantStmt takes textual
> names for objects and grantees, and what I have from pg_shdepend are
> Oids.

So refactor the GrantStmt code into a layer that translates to OIDs and
another layer that does the work. The other way doesn't sound good to
me; it is prone to race conditions against someone doing a RENAME.

> Is anyone opposed to this idea? Further, is anyone opposed to the
> addition as a whole? I'm already a month and a half late with this
> part of the shdep patch, so if people think it's better to ship this
> release without it, so be it. (Of course I don't like that.)

I think we're rapidly approaching the point where we have to say "sorry,
that is too late for this release". DROP OWNED is really a new feature,
not an essential component of the ROLES patch, and we've already
stretched the no-new-features-after-freeze rule to the breaking point.
I'll take the full blame for that --- I should probably not have forced
in the ROLES patch so close to feature freeze when it was obviously not
finished --- but at some point we've got to say no.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2005-08-13 14:33:55 Re: psql SET/RESET/SHOW tab completion
Previous Message Martijn van Oosterhout 2005-08-13 14:00:00 SPI: ERROR: no snapshot has been set