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

Re: Command Triggers

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
Cc: Andres Freund <andres(at)anarazel(dot)de>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>, Dimitri Fontaine <dimitri(at)2ndquadrant(dot)fr>
Subject: Re: Command Triggers
Date: 2011-12-03 00:16:47
Message-ID: CA+TgmoYKjniV1QtM_tM8C80FeTR_Z=d4peM3qOTMxQ10HModPg@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-hackers
On Fri, Dec 2, 2011 at 7:09 PM, Alvaro Herrera
<alvherre(at)commandprompt(dot)com> wrote:
> Hmm, we currently even have a patch (or is it already committed?) to
> avoid locking objects before we know the user has permission on the
> object.  Getting to the point of calling the trigger would surely be
> even worse.

I committed a first round of cleanup in that area, but unfortunately
there is a lot more to be done.

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

In response to

pgsql-hackers by date

Next:From: Andres FreundDate: 2011-12-03 00:26:22
Subject: Re: Command Triggers
Previous:From: Alvaro HerreraDate: 2011-12-03 00:09:48
Subject: Re: Command Triggers

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