Evergreen ILS Website

IRC log for #evergreen, 2022-09-16

| Channels | #evergreen index | Today | | Search | Google Search | Plain-Text | summary | Join Webchat

All times shown according to the server's local time.

Time Nick Message
02:39 jweston joined #evergreen
02:40 miker joined #evergreen
02:40 abneiman joined #evergreen
07:42 collum joined #evergreen
07:49 BDorsey joined #evergreen
07:53 rfrasur joined #evergreen
08:20 mantis1 joined #evergreen
08:27 kworstell-isl joined #evergreen
08:35 mmorgan joined #evergreen
08:49 mmorgan1 joined #evergreen
09:00 jvwoolf joined #evergreen
09:02 Dyrcona joined #evergreen
09:20 mmorgan1 joined #evergreen
09:25 mmorgan joined #evergreen
09:27 Dyrcona Cool. depesz has asked to see my logs from the crash. We may get somewhere.
10:11 mantis1 joined #evergreen
11:23 stephengwills joined #evergreen
11:31 Dyrcona depesz says to lower our work_mem, so we'll do that when we get a chance to restart PostgreSQL. I'm also adding the amcheck extension and running a query to check btree indexes for corruption just to rule that out.
11:35 jeffdavis On the one hand, cool that he's interested. On the other hand, scary that someone on that level has reason to be interested.
11:40 Dyrcona I think I just got lucky that he was paying attention to IRC when I posted a question.
11:41 jihpringle joined #evergreen
11:41 Dyrcona The amcheck was my idea as a precaution. depesz thinks our problem is running out of memory. I think it's bad RAM. :)
11:52 BDorsey joined #evergreen
12:29 jihpringle joined #evergreen
12:34 collum joined #evergreen
12:46 collum joined #evergreen
14:40 rfrasur joined #evergreen
15:01 jvwoolf left #evergreen
17:03 stephengwills left #evergreen

| Channels | #evergreen index | Today | | Search | Google Search | Plain-Text | summary | Join Webchat