"Josh Berkus" <[EMAIL PROTECTED]> writes:
> I can't help but feel that, because functions wrap everything in a
> transaction, some sort of tinkering with the xlog settings/performance
> is called for ...
I kinda doubt it. More likely sources of trouble involve the optimizer
picking bad plans because it can't see the exact values being used in
queries. Can you show us the details of the function?
regards, tom lane
---------------------------(end of broadcast)---------------------------
TIP 4: Don't 'kill -9' the postmaster
