Re: [v9.2] sepgsql's DROP Permission checks

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Kohei KaiGai <kaigai(at)kaigai(dot)gr(dot)jp>
Cc: PgHacker <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [v9.2] sepgsql's DROP Permission checks
Date: 2012-01-18 02:53:02
Message-ID: CA+TgmobdOvxh3kAfE74VPUVnVO_ZAWG_aZ_=geZ7gufwPOhmMQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Jan 17, 2012 at 10:55 AM, Kohei KaiGai <kaigai(at)kaigai(dot)gr(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2012-01-18 03:08:35 Re: [v9.2] Fix Leaky View Problem
Previous Message Alvaro Herrera 2012-01-18 02:46:36 Re: automating CF submissions (was xlog location arithmetic)