That EXECUTE FUNCTION syntax will break any attempt to create a new Evergreen 3.10.4, 3.11.2, or 3.12.0 database on Postgres 10 or any attempt to upgrade to one of those versions on Postgres 10. I've got local commits that correct the syntax for all affected branches, and once I push those I'll rebuild the 3.10.4, 3.11.2, and 3.12.0 tarballs unless someone else wants to grab one or some.
To be clear, anyone running Pg11 or later will not run into this issue because Postgres 11+ supports both syntaxes. As for your specific error, it's possible that with the 800.fkeys.sql file being broken (but the create-db script(s) not checking for errors... something else to fix sometime) the db you were left with was largely complete, but not complete enough to work properly. Jason -- Jason Boyer Senior System Administrator Equinox Open Library Initiative [email protected] +1 (877) Open-ILS (673-6457) https://equinoxOLI.org/ > On Dec 14, 2023, at 3:12 PM, Blake Graham-Henderson > <[email protected]> wrote: > > All, > > I've been spinning up more installations of Evergreen with various variables > changed. I've successfully installed the 3.11.2 tarball on a new machine, and > the concerto set does work now. So, I'm not sure what my problem was the > first go around. I should have done this routine before I blabbed about it. > In addition to the tarball success, I built another machine from git > rel_3_11, and that worked as well. > > Jason Boyer: > > I suppose you've ran through the installation from git rel_3_11 and > encountered an issue with EXECUTE PROCEDURE? But only for upgrading existing > DB's? > > I'm looking at > https://git.evergreen-ils.org/?p=working/Evergreen.git;a=commit;h=ff542fb56b4a9f4d6db688453fb15fafc1af186d > -Blake- > Conducting Magic > Will consume any data format > MOBIUS > > On 12/14/2023 1:49 PM, Jason Boyer wrote: >> So here's what happened: When I added the new trigger for LP 2023314 I used >> the Pg11+ FOR EACH ROW EXECUTE FUNCTION syntax rather than the pg <= 10 FOR >> EACH ROW EXECUTE PROCEDURE so creating a db on pg10 will fail for all >> releases from yesterday, 3.10.4, 3.11.2, and 3.12.0, and main. >> >> ALL POINT RELEASE UPGRADES WILL ALSO FAIL ON PG 10. >> >> Until the last point release of the last branch that supports Postgres 10 we >> need to continue to use the EXECUTE PROCEDURE syntax. As Postgres is slow to >> *remove* syntax support this will likely continue to work for a very long >> time. (Both syntaxes are still supported in pg 15 and current.) >> >> Since we have the branches for the point releases I'll correct them and >> rebuild the tarballs because we support pg10 even in main, so this needs to >> work everywhere. >> >> Jason >> >> -- >> Jason Boyer >> Senior System Administrator >> Equinox Open Library Initiative >> [email protected] <mailto:[email protected]> >> +1 (877) Open-ILS (673-6457) >> https://equinoxOLI.org/ <https://equinoxoli.org/> >> >>> On Dec 14, 2023, at 12:56 PM, Jason Boyer <[email protected]> >>> <mailto:[email protected]> wrote: >>> >>> Ah, what combination was broken wasn't entirely clear. I'll check on >>> rel_3_10 and pg 10 because I believe it's supported there so it needs to >>> work. >>> >>> Jason >>> >>> -- >>> Jason Boyer >>> Senior System Administrator >>> Equinox Open Library Initiative >>> [email protected] <mailto:[email protected]> >>> +1 (877) Open-ILS (673-6457) >>> https://equinoxOLI.org/ <https://equinoxoli.org/> >>> >>>> On Dec 14, 2023, at 12:42 PM, Blake Graham-Henderson >>>> <[email protected]> <mailto:[email protected]> wrote: >>>> >>>> Jason, >>>> >>>> Thanks for taking a look! A couple of clarifications: >>>> >>>> - It's rel_3_11 >>>> - My test machine used PG 10: >>>> >>>> make -f Open-ILS/src/extras/Makefile.install >>>> postgres-server-ubuntu-focal-10 >>>> >>>> Could be something going on in my environment. If you've tested it and >>>> it's working for you then I'm sure I've got something amiss over here. >>>> -Blake- >>>> Conducting Magic >>>> Will consume any data format >>>> MOBIUS >>>> >>>> On 12/14/2023 11:32 AM, Jason Boyer wrote: >>>>> Galen and I have done a little research on this and it looks like the >>>>> rel_3_10 branch can't be used to setup a new database on Postgres 15. >>>>> Just going back to pg 14 a new db + concerto works just fine. Since no >>>>> one is expected to install a fresh 3.10 system on pg15 this is fine. >>>>> >>>>> Jason >>>>> >>>>> -- >>>>> Jason Boyer >>>>> Senior System Administrator >>>>> Equinox Open Library Initiative >>>>> [email protected] <mailto:[email protected]> >>>>> +1 (877) Open-ILS (673-6457) >>>>> https://equinoxOLI.org/ <https://equinoxoli.org/> >>>>> >>>>>> On Dec 14, 2023, at 9:37 AM, Blake Graham-Henderson via Evergreen-dev >>>>>> <[email protected]> >>>>>> <mailto:[email protected]> wrote: >>>>>> >>>>>> Jason, >>>>>> >>>>>> I created the tarball, tested it, and uploaded it to the site. I also >>>>>> updated the downloads page. Maybe that was a bit hasty. I'll revert that >>>>>> if needs be. One thing that was concerning was the installation of the >>>>>> concerto set threw this error: >>>>>> >>>>>> psql:assets_concerto.sql:58: ERROR: update or delete on table >>>>>> "record_entry" violates foreign key constraint >>>>>> "browse_entry_def_map_source_fkey" on table "browse_entry_def_map" >>>>>> >>>>>> -Blake- >>>>>> Conducting Magic >>>>>> Will consume any data format >>>>>> MOBIUS >>>>>> 573-234-4513 >>>>>> 877-312-3517 >>>>>> >>>>>> On 12/14/2023 7:15 AM, Jason Stephenson via Evergreen-dev wrote: >>>>>>> Hi, all. >>>>>>> >>>>>>> I'm going to release 3.10.4 sometime today or tomorrow. I've got >>>>>>> personal stuff to do, and I'm working on a summary of the release >>>>>>> discussion. It's a lot of information to digest and summarize. >>>>>>> >>>>>>> Blake, are you ready to release 3.11.2? >>>>>>> >>>>>>> I'm not hanging out in IRC today, but I might pop in tomorrow. I have >>>>>>> less going on then. >>>>>>> >>>>>>> Jason Stephenson >>>>>>> _______________________________________________ >>>>>>> Evergreen-dev mailing list >>>>>>> [email protected] >>>>>>> <mailto:[email protected]> >>>>>>> http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-dev >>>>>> >>>>>> _______________________________________________ >>>>>> Evergreen-dev mailing list >>>>>> [email protected] >>>>>> <mailto:[email protected]> >>>>>> http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-dev >>>>> >>>> >>> >> >
_______________________________________________ Evergreen-dev mailing list [email protected] http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-dev
