Re: The suppress_redundant_updates_trigger() works incorrectly

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Andrew Dunstan <andrew(at)dunslane(dot)net>, 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:12:48
Message-ID: 478.1225908768@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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?

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Martijn van Oosterhout 2008-11-05 18:16:12 Re: [WIP] In-place upgrade
Previous Message Tom Lane 2008-11-05 18:10:35 Re: The suppress_redundant_updates_trigger() works incorrectly