Re: BUG #8152: strange behavior regarding after triggers and inheritance

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

El 13/05/13 17:06, Tom Lane escribi=F3:
> hcurti@exa.unicen.edu.ar writes:
>> PostgreSQL version: 8.4.17
>=20
>> After statments triggers on child tables are sometimes executed and
>> sometimes are not. As I far as I could see, when the after trigger is
>> defined in only one of the tables it may not get executed, wether when=
 it is
>> defined in every inherited table it does, but
>> which one is undetermined.
>=20
> This test case appears to work the way you're expecting in 9.0 and
> later.  I didn't immediately find a mention of such a change in the
> commit logs; perhaps it got fixed as a side-effect of the changes that
> moved trigger processing into ModifyTable plan nodes.  Anyway, I doubt
> we'd consider changing trigger behavior in 8.4.x at this late date.
> You should update to a newer release series if this is a problem for yo=
u.
>=20
>             regards, tom lane

Thank you Tom,

   The update to 9.x is already planned, and the workaround I mentioned
in the post works for me.

   regards,

        Hugo

- --=20
mailto:hcurti@exa.unicen.edu.ar
http://www.exa.unicen.edu.ar/~hcurti
Firma digital GPG/PGP: http://www.exa.unicen.edu.ar/~hcurti/firma_hcurti.=
asc

Puede hacer una donaci=F3n indirecta (gratis) de un plato de comida
para un ni=F1o de la Argentina ahora mismo ingresando a
http://www.porloschicos.com/servlet/PorLosChicos?comando=3Ddonar
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAlGRZLEACgkQy9s+D7eSFvn2uwCeL3v4sQpkLgvN3xmHIVYN/2Ic
NEcAoOrR+NXMzfarmgKxjDSun2docaC5
=3D6buB
-----END PGP SIGNATURE-----