| Time |
Nick |
Message |
| 08:13 |
|
collum joined #evergreen |
| 10:35 |
csharp_ |
upgraded PINES DB to PG 17 on Saturday - happy so far |
| 10:35 |
csharp_ |
things feel speedier - no errors that I've seen yet |
| 10:37 |
|
Christineb joined #evergreen |
| 10:37 |
csharp_ |
I had to drop the public.xml_is_well_formed function (which I feel certain we've talked about here) and I had to revoke privileges for one of the pg system tables that went away between versions |
| 10:38 |
csharp_ |
(for some non-superuser accounts we've created for ro access) |
| 10:40 |
jmurray-isl |
Yep...I had to drop the public.xml_is_well_formed function when upgrading from Pg 14 to 16. |
| 10:41 |
csharp_ |
feeling relieved - been meaning to find a window to do this for months - just forced one so it's not postponed to January or after our February 3.16 upgrade |
| 11:27 |
|
mmorgan joined #evergreen |
| 11:41 |
Bmagic |
csharp_++ # smooth |
| 12:02 |
|
jihpringle joined #evergreen |
| 13:22 |
|
collum joined #evergreen |
| 15:25 |
goood |
csharp_: is xml_is_well_formed a case of PG catching up with us? ... I'm not seeing the creation, so it must have been before we started using the evergreen schema to hold our custom "public" functions |
| 15:55 |
csharp_ |
goood: I think that's right |
| 16:09 |
|
jonadab joined #evergreen |
| 17:03 |
|
mmorgan left #evergreen |
| 18:55 |
|
jihpringle joined #evergreen |
| 23:55 |
|
csharp_ joined #evergreen |
