| Time |
Nick |
Message |
| 07:54 |
|
Rogan joined #evergreen |
| 08:06 |
|
BDorsey joined #evergreen |
| 08:24 |
|
collum joined #evergreen |
| 08:37 |
|
mmorgan joined #evergreen |
| 08:44 |
|
terranm joined #evergreen |
| 08:44 |
|
Stompro joined #evergreen |
| 08:46 |
|
Dyrcona joined #evergreen |
| 08:51 |
|
dguarrac joined #evergreen |
| 08:54 |
Dyrcona |
Stompro++ # It only took 1 hour and 14 minutes to export "all" of our bibs with items Sunday morning. |
| 08:56 |
Stompro |
Nice, that seems pretty reasonable. How many bibs and items is that? |
| 09:00 |
|
sleary joined #evergreen |
| 09:00 |
|
smayo joined #evergreen |
| 09:02 |
|
mmorgan1 joined #evergreen |
| 09:10 |
Dyrcona |
Stompro: It is 1,736,893 bibs. I can't really count the items because the main file is MARC binary. |
| 09:11 |
Dyrcona |
BTW: I think the Perl MARC::Record is too permissive. I'm going to do some research on it and probably open a ticket in CPAN's RT. |
| 09:12 |
Dyrcona |
We have a record with and empty 008 as an example. Evergreen deals with it just fine, but other systems mangle it. |
| 09:24 |
Dyrcona |
The simple things seem to be a problem for me this morning, like opening files in Perl.... I know what the problem is... No music is playing! |
| 09:25 |
|
mantis1 joined #evergreen |
| 09:32 |
|
NIngalls joined #evergreen |
| 09:57 |
pinesol |
News from commits: LP#2009891: release notes <https://git.evergreen-ils.org/?p=Evergreen.git;a=commitdiff;h=1fff08e73ca64d22bc6ddaa2e6d76af028be516b> |
| 09:57 |
pinesol |
News from commits: LP#2009891: add carousel default name to open-ils.actor.carousel.retrieve_by_org <https://git.evergreen-ils.org/?p=Evergreen.git;a=commitdiff;h=0b2561df57fbed32351e07d883370358bc3a9314> |
| 09:57 |
pinesol |
News from commits: LP#2009891: add item author to open-ils.actor.carousel.get_contents <https://git.evergreen-ils.org/?p=Evergreen.git;a=commitdiff;h=79080a199753a2240767d5ff8036af2fa18445a4> |
| 10:01 |
|
sleary joined #evergreen |
| 10:20 |
terranm |
Bmagic: Do you have reports running on your test server? |
| 10:22 |
|
smayo joined #evergreen |
| 10:51 |
|
smorrison joined #evergreen |
| 10:55 |
|
briank joined #evergreen |
| 11:18 |
|
sandbergja joined #evergreen |
| 11:43 |
csharp_ |
pretty sure current DB build scripts are failing on PG 11 - I haven't confirmed that - 11 goes out of support this month I think |
| 11:44 |
csharp_ |
"The PostgreSQL community will stop releasing updates for the 11.X release series in November 2023. Users are encouraged to update to a newer release branch soon." - yep |
| 12:01 |
|
Christineb joined #evergreen |
| 12:14 |
Dyrcona |
csharp_: I would say we should drop 10 and 11 (add 16), but not enough people have gone beyond 10 in production for me to be comfortable with just doing it. |
| 12:15 |
* Dyrcona |
has not had time to look into Pg 16, yet. |
| 12:18 |
jeffdavis |
we've been on PG14 in production for >6 months, it's just fine |
| 12:19 |
berick |
jeffdavis++ |
| 12:19 |
Dyrcona |
jeffdavis++ |
| 12:19 |
Dyrcona |
I've been testing production data with Pg 15, but not full time. |
| 12:19 |
Dyrcona |
I still run Pg 10 most of the time. |
| 12:20 |
jeffdavis |
we had to do a bit of cleanup prior to our Postgres upgrade because our EG install is so old, but nothing too arduous and we don't have any ongoing issues related to PG versions |
| 12:21 |
Dyrcona |
I can upgrade from Pg 10 to Pg 15 simply by applying the Evergreen db upgrades and doing a pg_dump and pg_restore. We have applied most of the necessary updates already. |
| 12:22 |
Dyrcona |
Hm. Maybe I'll swap Pg 10 and Pg 15 on my test system and just use Pg 10 to do the needed updates.... |
| 12:23 |
Dyrcona |
Yeah, I'll set that up this afternoon. |
| 12:24 |
Dyrcona |
Someone should open a Lp about Pg 10 and 11, and possibly Pg 16. |
| 12:34 |
Dyrcona |
jeffdavis: Have you seen the bug about disabling JIT in Pg? Lp 2042158 |
| 12:34 |
pinesol |
Launchpad bug 2042158 in Evergreen "Postgres 12+ needs to have JIT disabled" [Undecided,New] https://launchpad.net/bugs/2042158 |
| 12:35 |
jeffdavis |
I had not! Thanks, will mark as confirmed |
| 13:16 |
|
jihpringle joined #evergreen |
| 13:42 |
Dyrcona |
That pg_restore seems suspiciously fast. |
| 13:55 |
|
redavis joined #evergreen |
| 14:00 |
terranm |
Weekly 3.12 code review if anyone wants to join - https://www.google.com/url?q=https://princeton.zoom.us/my/sandbergja |
| 14:13 |
|
ejk_ joined #evergreen |
| 15:21 |
jeff |
terranm++ for sharing the link here |
| 15:36 |
Dyrcona |
So, I'm thinking of implement a third MARC exporter for Evergreen. This one would be written in Java using MARC4J to catch things that Aspen won't like. It's not so much meant to be for every day use. |
| 15:54 |
Dyrcona |
Looking through the code I wrote the MVLC migration to Evergreen from Horizon has given me some ideas. I had a SAX parser in there to check the MARCXML before trying to load a record. It would delete "empty" subfields and control fields. I could just yank the MARCXML from the database and check for busted elements as a start. |
| 16:07 |
csharp_ |
jeffdavis++ # PG 14 |
| 16:59 |
|
mantis1 left #evergreen |
| 17:10 |
|
mmorgan1 left #evergreen |
| 20:39 |
|
degraafk joined #evergreen |
| 21:06 |
|
sandbergja joined #evergreen |
