Stephen Frost <sfrost(at)snowman(dot)net> writes:
> Subject pretty much says it all. I've put up with this error in the
> past when it has caused me trouble but it's now starting to hit our
> clients on occation which is just unacceptable.
Have you tracked down the exact scenario making it happen?
> If this is correct then the solution seems to be either add versioning
> to the SysCache data,
You have provided no evidence that that would fix anything at all.
To my mind a "concurrently updated" failure is more likely to mean
insufficient locking around update operations.
regards, tom lane