Postgres: fix panic on concurrent createContinuousUnit
Postgres: fix panic on concurrent createContinuousUnit

There was a missing err check, so that if the tx.Exec() call that bumped
the next-continuous time failed, it wasn't getting caught.  The most likely
cause of this is someone else doing the same query at the same time.

diffeo/go-coordinate