er,
because the restricted python environment isn't yet working.
So... Is there an easy way to call a script from a trigger?
Thanks
Alan Graham
--
Alan Graham <[EMAIL PROTECTED]>
---(end of broadcast)---
TIP 9: the planner will ignore y
ython script LISTENing for a NOTIFY?
Thanks for your help
Alan Graham
On Thu, 2003-12-04 at 23:43, Peter Childs wrote:
> On Thu, 4 Dec 2003, Alan Graham wrote:
>
> > I'm doing a low cost, low performance roll your own replication project,
> > between various offices around
a CASCADE into the drop
function so it would drop the trigger as well,, and removed the drop
trigger statement.
Any thoughts as to how I can debug this further are greatly
appreciated. I'm not sure what to try next.
Thanks
Alan Graham
On Sat, 2003-12-06 at 02:51, Peter Eisentraut wrote:
> On
re?
Any suggestions as to debug options, extra logging, etc, I can try?
I thought it might be a permissions issue, but all users have full
access. The replicator user can make the changes by submitting an SQL
update. pgreplicator has a 'rejected sql' log file, but that's empty.
