On Wed, Jan 7, 2015 at 12:01 PM, Stephen Frost <sfrost@snowman.net> wrote:
> Other databases have this capability and have triggers and at least one
> ends up firing both INSERT and UPDATE triggers, with many complaints
> from users about how that ends up making the performance suck. Perhaps
> we could use that as a fallback but support the explicit single trigger
> option too.. Just some thoughts, apologies if it's already been
> convered in depth previously.
I would like to expose whether or not statement-level triggers are
being called in the context of an INSERT ... ON CONFLICT UPDATE, FWIW.
--
Peter Geoghegan
