"Dave Cramer" <davec@fastcrypt.com> writes:
> Mine manifests with the sequence being updated, and then another process
> comes along and tries to do the same operation and somehow gets the same
> sequence.
All I can say is I've been over the sequence code with a flinty eye,
and I'm darned if I can see anything wrong with it. I don't think
we are going to make much progress on this without being able to
investigate a failure with a debugger.
A self-contained example that shows a failure (even if only rarely)
would be really useful. Anything less really isn't useful.
regards, tom lane
