| Time |
Nick |
Message |
| 02:50 |
|
DaMobi_ joined #evergreen |
| 02:50 |
|
rhamby_ joined #evergreen |
| 02:50 |
|
jweston_ joined #evergreen |
| 02:50 |
|
eeevil joined #evergreen |
| 02:51 |
|
berick_ joined #evergreen |
| 02:51 |
|
tsadok_ joined #evergreen |
| 06:01 |
pinesol |
News from qatests: Failed Running perl live tests <http://testing.evergreen-ils.org/~live//archive/2022-05/2022-05-25_04:00:02/test.49.html> |
| 07:02 |
csharp_ |
at least it's not working for some reason |
| 07:02 |
csharp_ |
uh... ignore that :-/ |
| 07:15 |
|
rjackson_isl_hom joined #evergreen |
| 08:25 |
|
mantis1 joined #evergreen |
| 08:40 |
|
Dyrcona joined #evergreen |
| 09:21 |
|
mmorgan joined #evergreen |
| 10:01 |
|
RFrasur joined #evergreen |
| 10:15 |
csharp_ |
"berick_ is now known as berick" - well lah-de-dah, you can have a nick *without* an underscore at the end |
| 10:16 |
berick |
i paid good money for that |
| 10:16 |
* csharp_ |
sings "Nobody Knows the Trouble I've Seen" |
| 10:16 |
mmorgan |
csharp_: But tails are cool! |
| 10:17 |
csharp_ |
:-) |
| 10:18 |
csharp_ |
the csharp that continually tried to log in on freenode apparently beat me to it on libera |
| 10:18 |
mmorgan |
csharp_: Did you try for csharper? ;-) |
| 10:18 |
csharp_ |
oh yeah, code4lib is happening |
| 10:19 |
csharp_ |
no - but funny you ask - there's a charper in code4lib and we got mis-nicked constantly when that channel was more active |
| 10:19 |
csharp_ |
most C4L stuff moved to Slack |
| 10:19 |
berick |
it's called a nick mullet |
| 10:20 |
* csharp_ |
looks around for a mullet emoji |
| 10:20 |
mmorgan |
berick++ |
| 10:32 |
csharp_ |
https://photos.app.goo.gl/jhfeaL3dLJaVRjTr5 appropriately sloppy, but effective, I think |
| 10:32 |
berick |
haha |
| 10:32 |
berick |
that's def. going in the annual report |
| 10:33 |
mmorgan |
:-D |
| 10:36 |
eeevil |
csharp_: I spent about 8 years waiting for a 6mo lull in the use of miker, and then pounced on day 181 :) |
| 10:40 |
berick |
heh, was about to say... |
| 10:40 |
miker |
doh! |
| 10:44 |
csharp_ |
miker++ |
| 10:57 |
berick |
@dunno add https://photos.google.com/share/AF1QipPDDECW6XPTsnD1gyaqPm5K4qz6Phl6mJ34h6Xys93hMG-uZ8K0cDFsJQRR1_Gzag?pli=1&key=WVBxVVlMdTU4TEVlVFFzeHR4X2RkeW9kYktQRjFR |
| 10:57 |
pinesol |
berick: Error: You must be registered to use this command. If you are already registered, you must either identify (using the identify command) or add a hostmask matching your current hostmask (using the "hostmask add" command). |
| 10:59 |
Dyrcona |
@dunno add https://photos.app.goo.gl/jhfeaL3dLJaVRjTr5 |
| 10:59 |
pinesol |
Dyrcona: The operation succeeded. Dunno #73 added. |
| 11:00 |
Dyrcona |
@dunno get 72 |
| 11:00 |
pinesol |
Dyrcona: Dunno #72: "OK BOOMER" (added by csharp at 12:45 PM, April 29, 2022) |
| 11:01 |
Dyrcona |
My first though on seeing that "photo" was: csharp_: The Whitesnake Years. |
| 11:02 |
berick |
totally |
| 11:20 |
csharp_ |
"And I've made up my mind... I ain't wastin' no more time... Here I Go Again On My Own..." |
| 11:21 |
csharp_ |
and now everybody has that song playing in their heads - you're welcome |
| 11:25 |
mantis1 |
Going down the only road I ever known |
| 11:26 |
Dyrcona |
:) |
| 11:48 |
abneiman |
...and of course now would be the time I look at quassel, thanks for the earworm |
| 11:55 |
berick |
hey abneiman... I bless the rains down in Africa |
| 11:55 |
csharp_ |
haha |
| 12:04 |
|
jihpringle joined #evergreen |
| 12:09 |
RFrasur |
miker, I'm aware this might be a dumb question. Please forgive me. Is DYM integrated with the staff catalog as well as the OPAC? |
| 12:10 |
RFrasur |
Or eeevil |
| 12:19 |
csharp_ |
@decide miker or eeevil |
| 12:19 |
pinesol |
csharp_: go with miker |
| 12:19 |
csharp_ |
@quote random |
| 12:19 |
pinesol |
csharp_: Quote #120: "<rfrasur> And I'm not against a little food poisoning now and then, so long as it's moderate." (added by Dyrcona at 02:55 PM, June 30, 2015) |
| 12:19 |
csharp_ |
pinesol: good choice |
| 12:19 |
pinesol |
csharp_: git diff origin/hamster Fleshing children complete |
| 12:20 |
csharp_ |
pinesol: bad timing - try again |
| 12:20 |
pinesol |
csharp_: Dyrcona probably has a script for that. |
| 12:21 |
csharp_ |
what I actually looked like when Whitesnake was popular: https://photos.app.goo.gl/RdUf9ukgFGi9uKLD9 |
| 12:22 |
csharp_ |
man, I can just hear those early puberty squeaks in my voice looking at that |
| 12:23 |
csharp_ |
https://www.youtube.com/watch?v=mBec9vGdjEU |
| 12:29 |
mmorgan |
RFrasur: Had to look, but I DO see DYM suggestions in the staff client, both angular and traditional catalogs. |
| 12:33 |
RFrasur |
Thank you :-) |
| 13:13 |
csharp_ |
before I go on a wild goose chase, is there any specific reindexing or something that should happen with a PG 9.6 -> 10 upgrade? |
| 13:14 |
csharp_ |
seeing a query that a patron claims used to work okay now taking 5 minutes |
| 13:39 |
|
rjackson_isl_hom joined #evergreen |
| 13:49 |
* miker |
read's up |
| 13:50 |
miker |
RFrasur: yes, it is (thanks, mmorgan!) |
| 13:51 |
RFrasur |
lol, thank you mmorgan++ miker++ |
| 13:52 |
miker |
csharp_: I'd definitely recommend a vac-analyze. if you have the stomach/time for it, broad REINDEXing would not hurt. if you're adventurous and go to PG 12, there's REINDEX CONCURRENTLY, too! |
| 13:53 |
|
jihpringle joined #evergreen |
| 13:57 |
miker |
csharp_: and, there's pg_repack (with debian/ubuntu packages postgresql-10-repack etc) that can help with online batch index rebuilds (and other stuff) |
| 13:58 |
miker |
for versions before PG 12 |
| 14:08 |
Dyrcona |
My advice for Pg upgrades is dump before, restore after. |
| 14:08 |
Dyrcona |
It's required, IIRC, to dump and restore going from 10 to 11, or at some point between 10 and 14. |
| 14:12 |
miker |
Dyrcona: I haven't found it to be required, though at (I think, from memory) 13 you need to reindex due to unicode handling changes (slim risk, but better safe than sorry). pg_upgrade will tell you what needs to be done, though. (and there's definitely a "reindex if you upgrade your OS past a certain libc version" issue, for the room, but I'm pretty sure you're aware of that one) |
| 14:13 |
Dyrcona |
miker: I recall the release notes saying somewhere that you should dump and restore. |
| 14:15 |
Dyrcona |
Yeahp, it's Pg 14: https://www.postgresql.org/docs/current/release-14.html#id-1.11.6.8.4 |
| 14:29 |
miker |
yes, but pg_upgrade will still work, so a dump/restore isn't necessary. dump/restore is just one of 3 options. (and a perfectly valid one, which also gives you a small(ish) backup, which is a benefit) |
| 14:42 |
Dyrcona |
I'm puzzled by the required in the Pg 14 relase notes, then |
| 14:45 |
Dyrcona |
That said I have not upgraded from Pg 13 to Pg 14. I typically restore dumps from production on the test databases. I have pg upgraded from 9.6 to 10, and I seem to recall running either reindex and/or anlayze full. |
| 14:55 |
csharp_ |
I did a vac analyze right after upgrading and we have one on a cron - I haven't reindexed anything |
| 14:58 |
Dyrcona |
csharp_: We do a weekly vacuum analyze. We upgraded to Pg 10 last October. Let me check my notes/scripts.... |
| 14:59 |
csharp_ |
thanks! |
| 15:01 |
csharp_ |
miker: thanks for the pg_repack referral - looks interesting |
| 15:03 |
Dyrcona |
Doesn't look like we did anything special. We rand the ananlyze_cluster script that pg upgrade outputs to /tmp. |
| 15:04 |
Dyrcona |
Specifically this: sudo -u postgres /tmp/analyze_new_cluster.sh |
| 15:09 |
csharp_ |
heh - I was looking for available pg_* commands and read pgrep as "pg rep" |
| 15:10 |
csharp_ |
"huh, I've never heard of that one!" |
| 15:10 |
Dyrcona |
I use pgrep all the time when checking services: pgrep -af pcrud |
| 15:10 |
Dyrcona |
:) |
| 15:11 |
Dyrcona |
I wonder what pg_rep would do. |
| 15:12 |
csharp_ |
probably summons a sales guy for support services? |
| 15:13 |
csharp_ |
s/guy/rep/ |
| 15:15 |
Dyrcona |
Heh. |
| 15:16 |
Dyrcona |
pg_josh? |
| 15:17 |
csharp_ |
definitely |
| 15:39 |
gmcharlt |
berick: if you've got a moment, I'd appreciate if you could check whether I'm on target with respect to bug 1975742 |
| 15:40 |
pinesol |
Launchpad bug 1975742 in Evergreen "Angular Holdings Editor - sort out where holdings tempalates are saved" [Undecided,New] https://launchpad.net/bugs/1975742 |
| 15:42 |
berick |
gmcharlt: looking |
| 15:43 |
Dyrcona |
mmorgan: Is NOBLE still using the ttopac for the patron catalog? |
| 15:43 |
mmorgan |
Dyrcona: Yes, we are still using the tpac. |
| 15:44 |
Dyrcona |
mmogran: Thanks! We've had a question why some options show up on your search and not on ours. |
| 15:45 |
berick |
gmcharlt: agreed it should save to the server setting instead, though I thought the saved template data had the same format as angjs |
| 15:45 |
mmorgan |
Dyrcona: Which options? |
| 15:46 |
berick |
been a little while though, so i could remember wrong |
| 15:51 |
gmcharlt |
berick: I checked and found I was mistaken; the format didn't change |
| 15:51 |
* berick |
nods |
| 15:58 |
|
jihpringle joined #evergreen |
| 16:04 |
Dyrcona |
mmorgan: We had the same customization to add a Publisher search query type in TTOPAC, but it didn't make the transition to Bootstrap OPAC here because no one noticed it was missing in testing. |
| 16:06 |
* mmorgan |
nods |
| 16:07 |
Dyrcona |
We decided to start over from scratch with Bootstrap customization. |
| 16:20 |
abneiman |
berick++ # belatedly - but thanks to my chorus-nerd background I secretly love that song |
| 16:28 |
|
jihpringle joined #evergreen |
| 17:02 |
|
mmorgan left #evergreen |
| 17:50 |
|
jihpringle joined #evergreen |
| 18:01 |
pinesol |
News from qatests: Failed Running perl live tests <http://testing.evergreen-ils.org/~live//archive/2022-05/2022-05-25_16:00:02/test.49.html> |
| 18:26 |
|
bgillap joined #evergreen |
