Re: The suppress_redundant_updates_trigger() works incorrectly

I wrote:
> Andrew Dunstan <andrew@dunslane.net> writes:
>> OK, that will be easy enough. I assume I should still put InvalidOid 
>> back again afterwards, in case someone downstream relies on it.

> Can't imagine what ...

Actually ... what *could* change in the future is that we might support
UPDATE'ing the OID to a different value.  So what the code probably
needs to do is something like
if (relation->rd_rel->relhasoids &&    !OidIsValid(HeapTupleGetOid(newtup)))    HeapTupleSetOid(newtup,
HeapTupleGetOid(oldtup));

(details stolen from heap_update)
        regards, tom lane