On Tue, May 19, 2015 at 1:20 PM, Peter Geoghegan <p...@heroku.com> wrote: > On Tue, May 19, 2015 at 1:07 PM, Robins Tharakan <thara...@gmail.com> wrote: >> My use-case is to create an extra row for all UPDATEd rows (only), which is >> implemented in MSSQL by enveloping the MERGE with an INSERT (MERGE ... >> OUTPUT $action) WHERE $action = 'UPDATE'. > > That could make sense. You can achieve something similar with per-row > triggers, perhaps.
BTW, be prepared to deal with the updated row (*any* row version) not being visible to your MVCC snapshot with that pattern in Postgres (at READ COMMITTED level). It probably won't matter, but it could. -- Peter Geoghegan -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
