Set merge_profile id sequence explicitly

Bug #1426133 reported by Remington Steed on 2015-02-26
This bug affects 1 person
Affects Status Importance Assigned to Milestone

Bug Description

Many database tables need to explicitly set the id sequence (often to 100) to provide room for stock data with static ids. The stock database contains 2 profiles but doesn't yet set the sequence for merge_profile. This is causing the pgTAP test for bug 957466 to fail, since the test tries to create a new profile, which defaults to id=1 which is already taken by a stock profile.

We need to set merge_profile_id_seq to 100 in the stock database, and include an upgrade script that bumps the id of any custom profiles to above 100 (and then sets the sequence to the next id).

Remington Steed (rjs7) wrote :

Here is a branch that sets the sequence value in the stock database and includes an upgrade script.;a=shortlog;h=refs/heads/user/rsteed/lp1426133_set_merge_profile_sequence

tags: added: pullrequest schema
Ben Shum (bshum) wrote :

Pushed to master and backported to rel_2_7 and rel_2_6 since the reference pgtap test was applied to previous branches as well.

Thanks Remington!

Changed in evergreen:
milestone: none → 2.8-beta
status: New → Fix Committed
Changed in evergreen:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers