[EMAIL PROTECTED] (Tom Lane) writes:
> > But you really shouldn't need the old tuple to know this since none
> > of the columns present in the unique index are 'set' by the update?
> > I.e. the 'not changing the unique key part' is not data dependent,
> > it is guarantied by the form of the update statement.
>
> (a) that's even further upstream from the index AM, and (b) what about
> BEFORE triggers that change the tuple contents?
>
> regards, tom lane
Ok, I rest my case. I obviously don't know enough of the
postgres internals to suggest a usable solution for this
problem. Thanks for your quick answers.
_
Mats Lofkvist
[EMAIL PROTECTED]
---------------------------(end of broadcast)---------------------------
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
