> -Original Message-
> From: Tom Lane [mailto:t...@sss.pgh.pa.us]
> Sent: Donnerstag, 4. Juni 2015 15:56
> To: Marc Mamin
> Cc: pgsql-general@postgresql.org
> Subject: Re: [GENERAL] Row visibility issue with consecutive triggers,
> one being DEFERRED
>
> Marc
Marc Mamin writes:
> The test below is running fine
> but if you add the trigger push_foo_tr (uncomment)
> then the exception is raised.
Doesn't that trigger result in infinite recursion?
> CREATE OR REPLACE FUNCTION push_foo_trf () returns trigger AS $$
> BEGIN
> UPDATE foo SET (id,v) = (N
Hello,
The test below is running fine
but if you add the trigger push_foo_tr (uncomment)
then the exception is raised.
It seems that this additional trigger to be called at the first place
changes the deferrable status of the second one.
Is this an expected behaviour ?
regards,
Marc Mamin
