| Time |
Nick |
Message |
| 07:32 |
|
collum joined #evergreen |
| 08:04 |
|
BDorsey joined #evergreen |
| 08:14 |
|
jonadab joined #evergreen |
| 08:38 |
|
mmorgan joined #evergreen |
| 08:48 |
|
redavis joined #evergreen |
| 08:53 |
|
Dyrcona joined #evergreen |
| 09:02 |
|
dguarrac joined #evergreen |
| 09:14 |
|
mantis1 joined #evergreen |
| 09:16 |
Dyrcona |
I've noticed that with psql 16, \df+ <function> no longer shows the function definition. |
| 09:22 |
Dyrcona |
I had to use \ef <function> to open it in a test editor, which gives you the SQL used to create the function. |
| 09:24 |
Dyrcona |
Interesting... psql 10 gives an error when doing \df+ on a pg 15 database. I wonder if \df+ from psql 16 works on a Pg 16 database. It probably does. |
| 09:25 |
* Dyrcona |
loads a dump into pg 16 to see what happens. |
| 09:26 |
Dyrcona |
Heh... "Talk Soup" by Weird Al just started playing.... :) |
| 09:26 |
mantis1 |
talksoup++ |
| 09:27 |
Dyrcona |
"Listen to me! Listen to me! Listen to me!" :P |
| 09:30 |
* Dyrcona |
updates a script for pg 16 on the test db server. |
| 09:32 |
Dyrcona |
Whee! Just copy, paste, and edit 3 lines. |
| 09:35 |
JBoyer |
Dyrcona, so long as you specify enough params to uniq-ify it, \sf should show you the function source |
| 09:35 |
JBoyer |
(similar to \df+ I mean) |
| 09:35 |
Dyrcona |
JBoyer: OK. I was going to check with psql 16 on a pg 16 database because I think its an issue client server mismatch and not a change in features. |
| 09:36 |
JBoyer |
Oh, I see what you mean. Yeah, the queries backing that feature may have changed / broken / been removed in psql 16. |
| 09:36 |
Dyrcona |
Now that I have used it, I think I prefer \ef, at least when I'm running psql locally and talking to a remote server. |
| 09:37 |
Dyrcona |
I also plan to finally get around to adding Pg 16 support for Evergreen, so this will be a good first test. |
| 09:43 |
Dyrcona |
I suppose it is a good sign that pg_restore has not produced any output to the screen. |
| 09:43 |
|
smayo joined #evergreen |
| 09:51 |
|
BDorsey_ joined #evergreen |
| 09:51 |
|
BDorsey_ joined #evergreen |
| 10:19 |
|
sleary joined #evergreen |
| 10:21 |
|
sandbergja joined #evergreen |
| 10:47 |
Dyrcona |
pg_restore is still chugging away. Looks like Pg 16 might be easy. -- I should check the release notes. |
| 10:49 |
csharp_ |
@praise pg_restore |
| 10:49 |
* pinesol |
pg_restore is the hardest working person in #evergreen. |
| 10:49 |
csharp_ |
pinesol: uh.. NOT a person, pinesol |
| 10:49 |
pinesol |
csharp_: excuse me while I start planning my escape to a non-extradition nation |
| 10:51 |
berick |
@band add Quantum Goblet |
| 10:51 |
pinesol |
berick: Band 'Quantum Goblet' added to list |
| 10:51 |
berick |
the stuff that pops into my head at 2am |
| 10:53 |
Dyrcona |
Well. I think pg_restore finished. |
| 10:54 |
Dyrcona |
Yeah, the error message that I just go comes from an attempt to vacuum analyze a non-existent database. |
| 10:54 |
Dyrcona |
s/go/got/ |
| 10:56 |
Dyrcona |
Maybe I should add an option to the script to set the database name to restore into. |
| 10:58 |
Dyrcona |
And, here comes "Gigflapping" again..... "Pinging with no reply..." |
| 11:03 |
|
briank joined #evergreen |
| 11:03 |
|
brian_k joined #evergreen |
| 11:09 |
|
jvwoolf joined #evergreen |
| 12:05 |
|
jihpringle joined #evergreen |
| 12:28 |
|
jvwoolf joined #evergreen |
| 12:55 |
|
sleary joined #evergreen |
| 13:28 |
|
smayo joined #evergreen |
| 13:38 |
csharp_ |
Dyrcona: I tested out all but one of the LP scripts you shared and with a couple of Python 3-ish changes, they appear to work |
| 13:39 |
csharp_ |
the release.py one is untested since it appears to make changes and I wanted to get my head around it first |
| 13:39 |
csharp_ |
smayo may do some work on things too - we're still in research mode to make sense of the release process |
| 13:47 |
|
jvwoolf joined #evergreen |
| 13:58 |
|
dguarrac_ joined #evergreen |
| 14:11 |
|
mdriscoll joined #evergreen |
| 14:20 |
|
mdriscoll joined #evergreen |
| 14:25 |
mdriscoll |
I want to copy some patrons from a production system to a test system and I need their password to work. I have the password hash but not sure how to do the insert so the password works and isn't set to literally 'd41d8cd98f00b...' Any ideas? |
| 14:31 |
|
mdriscoll joined #evergreen |
| 14:34 |
jeff |
mdriscoll: that looks like the start of the md5 hash of an empty string. you'll probably want to take a look at the actor.passwd table. |
| 14:36 |
jeff |
mdriscoll: if you copy a user's row from actor.usr and actor.passwd (and actor.usr_address, actor.card, etc), then the copied user on the test system should end up with the same password as on the source system. |
| 14:39 |
mdriscoll |
jeff: thanks. I think actor.passwd is the part I was missing. |
| 14:41 |
jeff |
mdriscoll: depending on how empty your test system db is, you may need to worry about conflicts, renumbering ids, etc. Even if you don't, consider that if you manually insert ID values, you'll want to either bump sequences or know that eventually you'll run into an error when some future insert gets that manually-inserted value from its default sequence. |
| 14:42 |
jeff |
(depending on what kind of a test system this is, and how long it will be around, and other things, you may not care) |
| 14:48 |
mdriscoll |
jeff: I'm altering a script I use for loading patrons where I usually set the password and let the database trigger crypt the plain text. I let the database create the new ids but duly noted about bumping sequences. |
| 15:01 |
|
mmorgan1 joined #evergreen |
| 15:10 |
|
smayo joined #evergreen |
| 15:20 |
|
jihpringle joined #evergreen |
| 15:25 |
|
Rogan joined #evergreen |
| 15:28 |
|
mantis1 left #evergreen |
| 15:31 |
|
jihpringle joined #evergreen |
| 16:01 |
|
kmlussier joined #evergreen |
| 16:25 |
Dyrcona |
csharp_++ |
| 16:26 |
* Dyrcona |
has been dealing with plumbing this afternoon. |
| 17:01 |
|
jihpringle joined #evergreen |
| 17:06 |
|
mmorgan1 left #evergreen |
| 17:33 |
sandbergja |
abneiman, Bmagic, dluch, jihpringle, and any other DIG folks that I have neglected to spam: if you have the time and inclination to try out my branch for bug 1930099 by building the docs on a Windows computer, I'd be very appreciative. |
| 17:33 |
pinesol |
Launchpad bug 1930099 in Evergreen "generate_docs.pl should be able to run on Windows" [Medium,Confirmed] https://launchpad.net/bugs/1930099 |
| 17:33 |
Bmagic |
sandbergja: I saw that bug! I'll take a look as soon as I can |
| 17:34 |
sandbergja |
Bmagic++ |
| 17:36 |
|
briank joined #evergreen |
| 18:14 |
|
kmlussier left #evergreen |
| 18:42 |
|
sandbergja joined #evergreen |
| 18:54 |
|
briank joined #evergreen |
| 19:18 |
|
briank joined #evergreen |
| 20:33 |
|
briank joined #evergreen |
| 21:08 |
|
briank joined #evergreen |
| 21:41 |
|
briank joined #evergreen |
| 22:15 |
|
briank joined #evergreen |
| 22:56 |
|
briank joined #evergreen |
| 23:39 |
|
briank joined #evergreen |
