Project

General

Profile

Actions
Copy link

Defect #3685

closed

keep getting duplicate key error

Added by Robert Gonzalez over 15 years ago. Updated about 15 years ago.

Status:
Closed
Priority:
High
Assignee:
-
Category:
Database
Target version:
-
Start date:
2009-07-28
Due date:
% Done:

0%

Estimated time:
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.

Actions
Copy link
 #1

Updated by Jean-Philippe Lang over 15 years ago

Please read SubmittingBugs and post your stack trace.

Actions
Copy link
 #2

Updated by Robert Gonzalez over 15 years ago

  • Status changed from New to Resolved

Postgres got out of sync. A reboot fixed it.

Actions
Copy link
 #3

Updated by Jean-Philippe Lang about 15 years ago

  • Status changed from Resolved to Closed
  • Resolution set to Invalid

Thanks for the feedback.

Actions
Copy link

Also available in: Atom PDF