Steve Wampler <swampler@noao.edu> writes:
> It appears as though the timestamp resolution is now low
> enough that it cannot keep up with the speed at which
> items can be inserted.
Your example looks like what's being called is current_timestamp(3),
or else something on the client side is rounding it off to 3 digits.
The bare function will give whatever resolution the operating system
supplies, down to microseconds at best (the limit of the POSIX API for
this).
Even so, though, I think it would be quite foolish to design an
application around the assumption that the timestamps of successive
insertions will be distinguishable. Put in a serial column.
regards, tom lane
