"Gokulakannan Somsundaram" <[EMAIL PROTECTED]> writes:
> I propose to change this row-by-row approach, when it is a full table
> update. I plan to send a extra flag(which will be set for Full table
> Deletes/Updates). this would make the access method directly acquire the
> exclusive lock and update the existing record.
This sounds like a recipe for utter destruction of what little
modularity and layering we've got left. And I rather doubt it will buy
anything interesting performance-wise.
To cite just one concrete objection: surely the tuple-fetch code has got
no business firing triggers.
regards, tom lane
---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match
