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

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 (view raw or flat)
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

pgsql-hackers by date

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

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