Re: [v9.2] sepgsql's DROP Permission checks - Mailing list pgsql-hackers

From Robert Haas
Subject Re: [v9.2] sepgsql's DROP Permission checks
Date
Msg-id CA+TgmobdOvxh3kAfE74VPUVnVO_ZAWG_aZ_=geZ7gufwPOhmMQ@mail.gmail.com
Whole thread Raw
In response to Re: [v9.2] sepgsql's DROP Permission checks  (Kohei KaiGai <kaigai@kaigai.gr.jp>)
Responses Re: [v9.2] sepgsql's DROP Permission checks  (Kohei KaiGai <kaigai@kaigai.gr.jp>)
List pgsql-hackers
On Tue, Jan 17, 2012 at 10:55 AM, Kohei KaiGai <kaigai@kaigai.gr.jp> wrote:
> Do I modify the patch to place object-access-hook on deleteOneObject
> (probably, it is the best position to track actual deletion)?
> One problem is case of deletion of columns by ALTER TABLE.
> It just marks "attisdropped" flag; without removing catalog entry.
> Do we ought to put this hook on ATExecDropColumn exceptionally?

+1.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company


pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: automating CF submissions (was xlog location arithmetic)
Next
From: Robert Haas
Date:
Subject: Re: [v9.2] LEAKPROOF attribute of FUNCTION (Re: [v9.2] Fix Leaky View Problem)