Re: The suppress_redundant_updates_trigger() works incorrectly

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: KaiGai Kohei <kaigai(at)ak(dot)jp(dot)nec(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: The suppress_redundant_updates_trigger() works incorrectly
Date: 2008-11-05 18:39:01
Message-ID: 4911E845.4070300@dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tom Lane wrote:
> I wrote:
>
>> This method is utterly, utterly unacceptable; you're probably trashing
>> the contents of a disk buffer there.
>>
>
> ... however, it seems reasonable to assume that the *new* tuple is just
> local storage. Why don't you just poke the old tuple's OID into the new
> one before comparing?
>
>
>

OK, that will be easy enough. I assume I should still put InvalidOid
back again afterwards, in case someone downstream relies on it.

cheers

andrew

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2008-11-05 18:41:44 Re: The suppress_redundant_updates_trigger() works incorrectly
Previous Message Andrew Dunstan 2008-11-05 18:31:31 Re: The suppress_redundant_updates_trigger() works incorrectly