Not false, if you need to access the rows which changed you need to use a per-row trigger in Postgres. There is work being done to support seeing all the affec

Not false, if you need to access the rows which changed you need to use a per-row trigger in Postgres. There is work being done to support seeing all the affected rows in a per-statement trigger like you can in Sql Server, but it's not committed yet. See: https://www.postgresql.org/message-id/flat/20140616195900.GC18688%40eldon.alvh.no-ip.org#20140616195900.GC18688@eldon.alvh.no-ip.org https://www.postgresql.org/message-id/flat/20140616195900.GC...