Created timestamp index on events shouldn't be unique

[peterbroadhurst]

Saw the below error in a long-run test, where an attempt to insert an event resulted in no rows being added in PSQL with ON CONFLICT DO NOTHING RETURNING seq. I found there's an index that is set to UNIQUE on the created timestamp, and while a clash there is unlikely it's definitely possible.

{"log":"[2022-03-27T20:45:44.100Z]  WARN node_0: SQL! transaction rollback dbtx=WLXd2cMS httpreq=GJpFajph req=w6nJtbSg\n","stream":"stderr","time":"2022-03-27T20:45:44.102693254Z"}
{"log":"[2022-03-27T20:45:44.102Z]  INFO node_0: \u003c-- POST /api/v1/namespaces/default/contracts/invoke [500] (19.62ms): FF10116: Database insert failed: FF10375: Failed to retrieve sequence for insert row 1 (could mean duplicate insert) httpreq=GJpFajph req=w6nJtbSg\n","stream":"stderr","time":"2022-03-27T20:45:44.10280407Z"}

[codecov-commenter]

Codecov Report

Merging #634 (bbc43f9) into main (53ecb34) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##              main      #634   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files          311       311           
  Lines        18842     18842           
=========================================
  Hits         18842     18842           

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 53ecb34...bbc43f9. Read the comment docs.