Conversation

When executing an UPSERT in #PostgreSQL it seems "new" and "old" in my trigger hold the same value. Expected behaviour?

Replying to

INSERT or UPDATE trigger?

Replying to

can put up a gist if needed...

Replying to

Do.

Replying to

see here ht.ly/T8a6S - Quite likely my mistake, but can`t spot the error... :P

Replying to

This is an AFTER trigger, you see. Those are generally used to modify other table. Only BEFORE triggers "intercept" UPDATEs.

Replying to

Also, since it's AFTER trigger, "RETURN NEW" could be replaced with "RETURN NULL" without consequence -- return value ignored.