In-Reply-To: <BE1E8DAA-A829-11D9-9125-000A95B03262@pgedit.com>
References: <4255AA15.8000508@mochima.com>
	<BE1E8DAA-A829-11D9-9125-000A95B03262@pgedit.com>
Mime-Version: 1.0 (Apple Message framework v619.2)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <fef7e50cf33b53ca481ecb2554cd6403@mail.nih.gov>
Content-Transfer-Encoding: 7bit
Cc: Carlos Moreno <moreno@mochima.com>, pgsql-sql@postgresql.org
From: Sean Davis <sdavis2@mail.nih.gov>
Subject: Re: Question on triggers and plpgsql
Date: Fri, 8 Apr 2005 09:41:57 -0400
To: John DeSoi <desoi@pgedit.com>


On Apr 8, 2005, at 8:28 AM, John DeSoi wrote:

>
> On Apr 7, 2005, at 5:45 PM, Carlos Moreno wrote:
>
>> The thing seems to work -- I had to go in a shell as user
>> postgres and execute the command:
>>
>> $ createlang -d dbname plpgsql
>>
>> (I'm not sure I understand why that is necessary, or
>> what implications -- positive or negative -- it may have)
>
> As a security measure, no pl language is available by default. What 
> you did is correct. There is not much (any?) risk with pl/pgsql, so 
> you can install it in template1 so it will be available in any new 
> database you create.
>
>>
>> Am I doing the right thing?  Have I introduced some sort
>> of catastrophe waiting to happen?
>
> I did not notice any problems.
>

Just one detail, but in the form of a question. In the original 
posting, I think the trigger was doing the logging for something 
happening on a table as a before insert or update--I may be wrong on 
that detail.  I would think of doing such actions AFTER the 
update/insert.  In the world of transaction-safe operations, is there 
ANY danger in doing the logging as a BEFORE trigger rather than an 
AFTER trigger?

Thanks,
Sean