On Tue, Aug 7, 2012 at 2:39 PM, Craig James <cjames@xxxxxxxxxxxxxx> wrote:
Obviously this is a very expensive trigger, but one that we can drop
in a very specific circumstance. But we NEVER want to drop it for
everyone. It seems like a very reasonable use-case to me.
Sounds like you should try doing the work inside the trigger conditionally and see if that improves performance enough, since you aren't likely to get anything that better suits your needs without patching postgres.
