Defect #3685
keep getting duplicate key error
| Status: | Closed | Start date: | 2009-07-28 | |
|---|---|---|---|---|
| Priority: | High | Due date: | ||
| Assignee: | - | % Done: | 0% | |
| Category: | Database | |||
| Target version: | - | |||
| Resolution: | Invalid | Affected version: | 0.8.4 |
Description
We keep getting this error when people try to create new issues:
ActiveRecord::StatementInvalid (PGError: ERROR: duplicate key violates unique constraint "issues_pkey" : INSERT INTO "issues" ("created_on", "start_date", "project_id", "estimated_hours",........
We think its because we have a pretty active system and they are colliding.
History
#1
Updated by Jean-Philippe Lang about 11 years ago
Please read SubmittingBugs and post your stack trace.
#2
Updated by Robert Gonzalez about 11 years ago
- Status changed from New to Resolved
Postgres got out of sync. A reboot fixed it.
#3
Updated by Jean-Philippe Lang over 10 years ago
- Status changed from Resolved to Closed
- Resolution set to Invalid
Thanks for the feedback.