Mix of explicit event definition IDs and CURRVAL results in unhappiness
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Evergreen |
Fix Released
|
Critical
|
Thomas Berezansky |
Bug Description
* Evergreen master
* PostgreSQL 9.1
I noticed when creating the database schema today that my PostgreSQL log contained the following:
ERROR: insert or update on table "event_params" violates foreign key constraint "event_
DETAIL: Key (event_def)=(100) is not present in table "event_definition".
STATEMENT: INSERT INTO action_
VALUES (currval(
This is because at line 7213 we use SETVAL to set the sequence value to 100.
But that breaks later, down on line 9212, when we use an explicit ID to create the event definition, but fall back to using CURRVAL on the sequence.
Changed in evergreen: | |
milestone: | none → 2.2.0beta1 |
tags: | added: bitesize |
Changed in evergreen: | |
assignee: | nobody → Thomas Berezansky (tsbere) |
Changed in evergreen: | |
milestone: | 2.2.0beta1 → 2.2.0beta2 |
Changed in evergreen: | |
status: | Fix Committed → Fix Released |
Marked as "Critical" because it should be a release blocker.