#2119: upgrade-master sets auto-increment counters for id fields incorrectly in
postgresql
--------------------+-----------------------
Reporter: szager | Owner:
Type: defect | Status: new
Priority: major | Milestone: undecided
Version: 0.8.4p1 | Keywords:
--------------------+-----------------------
When upgrading master database from 0.7.12 to 0.8.4p1, and creating the
new database in postgresql, some of the tables have an 'id' field that
uses an auto-increment counter to get a value for newly-added rows;
something like this:
CREATE TABLE changes (
changeid PRIMARY KEY DEFAULT nextval('changes_changeid_seq'),
...
);
The problem is that the state of the counter is set incorrectly after the
upgrade. For example, I upgraded a database that had 775 change records.
The imported change records had the expected sequential changeid values
1-775, but the 'last_value' field of the changes_changeid_seq counter was
20, rather than the expected 775.
I have seen this in the changes.changeid field and the build.id field.
--
Ticket URL: <http://trac.buildbot.net/ticket/2119>
Buildbot <http://buildbot.net/>
Buildbot: build/test automation
------------------------------------------------------------------------------
All of the data generated in your IT infrastructure is seriously valuable.
Why? It contains a definitive record of application performance, security
threats, fraudulent activity, and more. Splunk takes this data and makes
sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-d2dcopy2
_______________________________________________
Buildbot-commits mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/buildbot-commits
