Hello, I just finished a test database upgrade of our 2.10 system to 3.0.0-beta1 and it went pretty smooth. It did get stuck on the 2.12.4->3.0.0-beta1 script when adding the new copy visibility scheme, but once I added the trigger drops and re-adds mentioned by Chris Sharp in IRC, that part only took a few minutes on my slow test VM.
http://git.evergreen-ils.org/?p=evergreen/pines.git;a=blobdiff;f=Open-ILS/src/sql/Pg/version-upgrade/2.12.5-3.0-beta1-upgrade-db.sql;h=3a4f54fecc0b4c37b627da2963fe1e50e259aa02;hp=0da18594c992f7050b0ea907600e318af117d6da;hb=99d5c1164f7180117760d48245db54a5a7bc0296;hpb=dfc8e3892d76af32162e1069c2c620139449ce2f http://git.evergreen-ils.org/?p=evergreen/pines.git;a=commitdiff;h=826d5ba27d47123982a9fc06b44847cca125c24e;hp=3f5e6b3d36be3cd149ea45b8c87ba1c2e98c17ad After the upgrade I started a reingest using the pingest.pl tool, since I skipped all the skippable reingests during the upgrade, and I received two instances of the following error. I'm wondering if this is anything to worry about? Or is this just a timing issue, maybe two threads of pingest.pl were both trying to create the same browse creator entry? I used small batches of 250 records, so maybe that is it? DBD::Pg::st execute failed: ERROR: duplicate key value violates unique constraint "browse_entry_sort_value_value_key" DETAIL: Key (sort_value, value)=(glasrud clarence a creator, Glasrud, Clarence A. creator) already exists. CONTEXT: SQL statement "INSERT INTO metabib.browse_entry ( value, sort_value ) VALUES ( value_prepped, ind_data.sort_value )" PL/pgSQL function metabib.reingest_metabib_field_entries(bigint,boolean,boolean,boolean,boolean,integer[]) line 86 at SQL statement at ./pingest.pl line 272. metabib.reingest_metabib_field_entries failed for record 8544 at ./pingest.pl line 275. DBD::Pg::st execute failed: ERROR: duplicate key value violates unique constraint "browse_entry_sort_value_value_key" DETAIL: Key (sort_value, value)=(montgomery l m lucy maud creator, Montgomery, L. M. (Lucy Maud). creator) already exists. CONTEXT: SQL statement "INSERT INTO metabib.browse_entry ( value, sort_value ) VALUES ( value_prepped, ind_data.sort_value )" PL/pgSQL function metabib.reingest_metabib_field_entries(bigint,boolean,boolean,boolean,boolean,integer[]) line 86 at SQL statement at ./pingest.pl line 272. metabib.reingest_metabib_field_entries failed for record 241130 at ./pingest.pl line 275. I re-ran the pingest just for the records mentioned and that did take care of adding the correct entries to metabib.browse_entry_def_map. Does each batch in pingest.pl run in its own transaction? Would this error mean that all the changes for that batch of 250 records were rolled back? Thanks Lake Agassiz Regional Library - Moorhead MN larl.org Josh Stompro | Office 218.233.3757 EXT-139 LARL IT Director | Cell 218.790.2110
