Date: Wed, 15 Jan 2014 03:30:07 -0800 (PST)
From: gmb <gmbouwer@gmail.com>
To: pgsql-sql@postgresql.org
Message-ID: <1389785407565-5787212.post@n5.nabble.com>
In-Reply-To: 
 <CAHZ=uVCV-u25SEFSHaHWQshbRO0Lu037S4yRabN8=4kdSKo5ew@mail.gmail.com>
References: <1389775925366-5787181.post@n5.nabble.com>
 <CAHZ=uVCV-u25SEFSHaHWQshbRO0Lu037S4yRabN8=4kdSKo5ew@mail.gmail.com>
Subject: Re: debugging triggers - get original statement?
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Precedence: bulk
Sender: pgsql-sql-owner@postgresql.org

Thanks for your reply, Lucazeo.

> BUT: it is dangerous in production: you can fill your file system very 
> fast and slow down the system. 

Yes, this was my concern as well. In my current situation this may be too
risky.

>Another way is: modify the trigger and write informations you need in 
>a specific table. Not an elegant solution but... 

Exactly what I had in mind, but I hoped to be able to log the original
statement as well .
In that way I can simulate the problem-causing transactions exactly in a
more controlled env by running the scripts as in the log table.

Thanks any way.


--
View this message in context: http://postgresql.1045698.n5.nabble.com/debugging-triggers-get-original-statement-tp5787181p5787212.html
Sent from the PostgreSQL - sql mailing list archive at Nabble.com.


-- 
Sent via pgsql-sql mailing list (pgsql-sql@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-sql