| Time |
Nick |
Message |
| 01:44 |
|
b_bonner joined #evergreen |
| 01:44 |
|
mtcarlson_away joined #evergreen |
| 02:07 |
|
b_bonner joined #evergreen |
| 02:07 |
|
mtcarlson_away joined #evergreen |
| 03:09 |
|
mtcarlson_away joined #evergreen |
| 03:25 |
|
tfaile_ joined #evergreen |
| 03:25 |
|
mtate joined #evergreen |
| 09:39 |
|
RBecker joined #evergreen |
| 09:58 |
csharp |
hmm - getting an error I haven't seen before in the 2.4.3-2.5.0 db upgrade script: ERROR: could not find trigger 1981765 |
| 09:58 |
csharp |
google search is only yielding one other person ever who posted about this 10 years ago: http://www.postgresql.org/message-id/3392633009.20031219144130@uptsoft.com |
| 10:00 |
csharp |
I thought it might be related to 0827 since the error was originally happening at the "SET CONSTRAINTS ALL IMMEDIATE;" statement, but when I commented that out, it happened at "COMMIT;" |
| 10:05 |
* csharp |
decides to run VACUUM ANALYZE before running the script again |
| 11:07 |
|
RBecker joined #evergreen |
| 11:20 |
csharp |
nope - vacuum didn't help :-/ |
| 13:42 |
bshum |
Hmm, unrelated but the original 0827 doesn't have that in it. It's only in the upgrade script itself. So we probably never stumbled over that particular issue. |
| 13:43 |
bshum |
csharp: My vague googling is coming up with slony threads that include references to that error you mention about "could not find trigger" |
| 13:43 |
bshum |
Since we don't use slony, but you do, maybe that is related. |
| 13:43 |
|
stevenyvr2 joined #evergreen |
| 13:44 |
|
stevenyvr2 left #evergreen |
| 13:45 |
bshum |
Either way, I haven't run a version upgrade script in so long that I probably should stop now and let other folks think through it. |
| 13:45 |
bshum |
Good luck csharp, sorry I can't be more helpful right now. |
| 14:01 |
bshum |
Unrelated, it may be that we need both the --create-database and --create-schema flags for eg_db_config to create a remote database. The README only notes --create-database |
| 14:04 |
bshum |
And fwiw csharp, a clean 2.4.3 database with concerto running the 2.4.3-2.5.0 script went through just fine. Not that it's a good test, cause real production data is always better. But it doesn't seem to be an immediately broken script :( |
| 14:16 |
csharp |
bshum: thanks - I have another test db and I'm going to run the same script on it to see if it's a data corruption issue or something |
| 14:22 |
bshum |
@later tell dbs Curious if you think this article I was just reading about dojo.require and Firefox rendering makes sense. Maybe it could help with our autosuggest brokenness with Firefox lately? http://stackoverflow.com/questions/1943082/dojo-require-prevents-firefox-from-rendering-the-page |
| 14:22 |
pinesol_green |
bshum: The operation succeeded. |
| 14:24 |
bshum |
csharp: Cool deal, curious to see what happens :) |
| 14:27 |
bshum |
Eh, probably not it dbs, maybe nevermind |
| 14:36 |
bshum |
Hmm, so I turned on autosuggest on our test database. And then if I search in Chrome for something, it'll suggest it to me. |
| 14:36 |
bshum |
Interestingly, if I then search for the same term in Firefox, it suggests it to me. |
| 14:37 |
bshum |
It's probably cache or something |
| 14:45 |
bshum |
Oh well, off to shovel some snow and then get ready for the first Christmas party of this week. |
| 16:11 |
ldwhalen |
is anyone around who understands how pgTap tests are supposed to be used? |
| 16:14 |
jeff |
have you looked at the existing docs and the notes that dbs put in the Encode.pm bug? |
| 16:15 |
ldwhalen |
no, I looked at 1194246 |
| 16:17 |
jeff |
bug 1242999 |
| 16:17 |
pinesol_green |
Launchpad bug 1242999 in Evergreen "Encode.pm 2.54 breaks database functions (naco_normalize, maintain_control_numbers, others)" (affected: 1, heat: 10) [High,Confirmed] https://launchpad.net/bugs/1242999 |
| 16:17 |
jeff |
almost the last comment has a brief outline |
| 16:17 |
ldwhalen |
thanks! |
| 16:17 |
jeff |
beyond that i don't have direct experience yet, but ask away! |
| 16:18 |
jeff |
(and soneone else with more direct experience may answer) |
| 16:19 |
ldwhalen |
I am modifying query_parser_fts, and I am not sure what type of tests I might run. I will look into this bug. |
| 16:28 |
ldwhalen |
From what I can see the pgTAP tests are testing the effects of data within the database. This modification is |
| 16:29 |
ldwhalen |
to a function. There are tests that could be run against it. But, I am not sure what the scope should be. |
| 16:29 |
ldwhalen |
It has 12 input parameters, so a complete test would be massive. |
| 16:30 |
ldwhalen |
I am going to add it to a workingg branch and put a pull request on the lp bug because that has been requested |
| 16:30 |
ldwhalen |
and these changes have been running live on Sitka for months. If a test is needed, I will write one. |
| 17:01 |
csharp |
interesting... if I 'grep block_check 2.4.3-2.5.0-upgrade-db.sql | cut -d"'" -f2' and apply those updates one at a time, I get no errors |
| 17:02 |
csharp |
so it must be something about the script + my data |
| 17:02 |
csharp |
or the script itself |
| 17:02 |
csharp |
or a hardware problem/limitation |
| 17:02 |
* csharp |
hates not knowing for sure |
| 17:32 |
|
dcook joined #evergreen |
| 19:54 |
|
dac joined #evergreen |
| 22:26 |
csharp |
same 'could not find trigger' error when running 2.4.3-2.5.0 upgrade script on another PINES prod data set - I'll file a bug tomorrow in case it's not just something about us. |
| 22:32 |
jeff |
csharp++ |
| 23:47 |
|
dcook joined #evergreen |
