We are still in a pickle with trying to resolve our trigger issues
without affecting slony triggers.

The point is, we need to be able to disable triggers, check constraints,
and foreign-key constraints without affecting slony triggers in certain
situations.

This is all running on 7.4.19, thus, it's our understanding that using
tgenabled is not going to be a solution.

Making our triggers smarter doesn't get us all the way there.

Suggestions?

--
Until later, Geoffrey

Those who would give up essential Liberty, to purchase a little
temporary Safety, deserve neither Liberty nor Safety.
- Benjamin Franklin

---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match

On Feb 25, 2008, at 2:33 PM, Geoffrey wrote:

> We are still in a pickle with trying to resolve our trigger issues
> without affecting slony triggers.
>
> The point is, we need to be able to disable triggers, check
> constraints, and foreign-key constraints without affecting slony
> triggers in certain situations.
>
> This is all running on 7.4.19, thus, it's our understanding that
> using tgenabled is not going to be a solution.
>
> Making our triggers smarter doesn't get us all the way there.
>
> Suggestions?

This may've been suggested to you earlier, but can you drop them and
re-add them when you're done?

Erik Jones

DBA | Emma®
erik@myemma.com
800.595.4401 or 615.292.5888
615.292.0777 (fax)

Emma helps organizations everywhere communicate & market in style.
Visit us online at http://www.myemma.com




---------------------------(end of broadcast)---------------------------
TIP 3: Have you checked our extensive FAQ?

http://www.postgresql.org/docs/faq