"(We will migrate to whatever the latest stable version in the 12.x series is)." sounds like you couldn't be bothered to check, do you mean "at that point"?
2020-02-04 03525, 2020
reosarevok
real-only time sounds like the safest kind, but I guess you wanted read-only?
2020-02-04 03531, 2020
reosarevok
And "but that we will have some amount" I would probably drop that "that" there but I guess it works both ways
2020-02-04 03535, 2020
reosarevok
Otherwise it seems fine :)
2020-02-04 03538, 2020
c1e0 has quit
2020-02-04 03504, 2020
CatQuest
reo
2020-02-04 03540, 2020
Pac23
gsoc ideas up ?
2020-02-04 03551, 2020
yvanzo
working on it!
2020-02-04 03552, 2020
sumedh joined the channel
2020-02-04 03553, 2020
Pac23
cool,
2020-02-04 03524, 2020
Pac23
yvanzo++
2020-02-04 03555, 2020
yvanzo
updating beta.mb.o
2020-02-04 03512, 2020
Pac23
karma bot broken ? how do i do ++ here ?
2020-02-04 03527, 2020
yvanzo
Pac23: there will be something about sir :)
2020-02-04 03522, 2020
yvanzo
No karma bot here, we have BrainzBot instead.
2020-02-04 03524, 2020
Pac23
oh cool,idk if i am capable enough of doing a complex gsoc project :/ too scared of failing gsoc.
2020-02-04 03504, 2020
Pac23
so how do i call the brainzbot ? doing nick++ did not show a prompt here on my hexchat window.
2020-02-04 03551, 2020
ruaok
reosarevok: > "at that point"?
2020-02-04 03510, 2020
ruaok
because we won't know which version in the 12.x series will have been released.
2020-02-04 03514, 2020
Mr_Monkey
!m Pac23
2020-02-04 03514, 2020
BrainzBot
You're doing good work, Pac23!
2020-02-04 03520, 2020
Mr_Monkey
That's how :)
2020-02-04 03535, 2020
Pac23
ah,thanks !m Mr_Monkey
2020-02-04 03555, 2020
Pac23
!m Mr_Monkey
2020-02-04 03555, 2020
BrainzBot
You're doing good work, Mr_Monkey!
2020-02-04 03559, 2020
Mr_Monkey
Only works with the "!m" at the beginning of the sentence though
2020-02-04 03500, 2020
Mr_Monkey
That :D
2020-02-04 03506, 2020
Pac23
!m yvanzo
2020-02-04 03506, 2020
BrainzBot
You're doing good work, yvanzo!
2020-02-04 03512, 2020
Pac23
i see,lol
2020-02-04 03519, 2020
ruaok
reosarevok: thanks for the tips, I made three small changes. (or not so small in the "real" case)
2020-02-04 03542, 2020
ruaok publishes it
2020-02-04 03542, 2020
Gore|woerk has quit
2020-02-04 03503, 2020
Matthew_ joined the channel
2020-02-04 03527, 2020
Matthew_ is now known as Guest76865
2020-02-04 03530, 2020
Guest76865
Hello! Thanks for the blog post about the Postgres upgrade. I just wanted to hurl a slight spanner from us replicated slave merchants in your direction... Neither AWS nor Azure currently provide a Postgres 12 managed database service...
2020-02-04 03522, 2020
ruaok
hiya!
2020-02-04 03540, 2020
ruaok
do you have an appreciation for how far that support lags behind the PG releases?
2020-02-04 03501, 2020
ruaok
we've got over 3 months....
2020-02-04 03515, 2020
ruaok
and also, note that it isn't CRITICAL that you update.
2020-02-04 03520, 2020
ruaok
it is recommended.
2020-02-04 03535, 2020
Guest76865
I'm not sure. Not a _huge_ amount. I can do some research and ask about AWS about their roadmap for that. I've no contacts at Microsoft.
2020-02-04 03557, 2020
ruaok
what if we refrained for (AWS|Azure) 12.x support + 30 days before we use 12.x features?
2020-02-04 03533, 2020
ruaok
I have some contacts, but I have a feeling i know what the response will be. (read: not forthcoming)
2020-02-04 03522, 2020
yvanzo
updating prod mb.o
2020-02-04 03536, 2020
ruaok
thanks yvanzo.
2020-02-04 03500, 2020
Guest76865
Sure. I understand. I'm not too concerned about it in the short term and they will eventually make the version available. Let me see if I can get someone in the know to give an idea... Anyway, just wanted to give you a heads up!
2020-02-04 03509, 2020
ruaok
thanks for that, much appreciated.
2020-02-04 03525, 2020
ruaok
and like I said, if we need to hold off using PG 12.x features, we can do that.
2020-02-04 03551, 2020
ruaok
but for our own sanity, we really want to use this cadence cycle for moving to 12.x
ok, great. let's touch base closer to the time, shall we?
2020-02-04 03504, 2020
Guest76865
Sure. ruaok - while I'm here. We've been running the SIR for a while and, aside from the artist_credit ID 1 issue, it's been largely fine. However, we have noticed some of the indexing processes hanging every now and then, requiring a kill / restart. Is that something you've seen at all?
2020-02-04 03515, 2020
Etua joined the channel
2020-02-04 03554, 2020
ruaok
yvanzo: zas: any thoughts to contribute to this? ^^
2020-02-04 03556, 2020
Guest76865
Currently, we are restarting SIR before fetching replication packets and it seems to be working fine.
2020-02-04 03521, 2020
ruaok
seems less than ideal.
2020-02-04 03541, 2020
zas
more yvanzo than me, I know nothing about SIR stuff
2020-02-04 03505, 2020
Guest76865
The code is quite.... cryptic. For me at least!
2020-02-04 03512, 2020
ruaok
well, its not SIR, but more kicking-SIR. :)
2020-02-04 03501, 2020
Guest76865
It's possibly environmental - resource exhaustion (not enough provisioned) but I just wondered if you'd seen similar
2020-02-04 03543, 2020
ruaok
I think what we've seen is also caused by resource exhaustion. adding more resources seems to have greatly improved the stability of search.
2020-02-04 03549, 2020
Guest76865
OK. Thanks ruaok.
2020-02-04 03531, 2020
ruaok
np. thanks for your quick response on this.
2020-02-04 03542, 2020
Guest76865
np
2020-02-04 03552, 2020
yvanzo
I confirm the resource exhaustion, but it is still unclear how to address it, provisioning more isn't necessarily enough.
2020-02-04 03512, 2020
yvanzo
It is more an issue of tuning configuration, but that is sometimes difficult to adjust.
2020-02-04 03536, 2020
Guest76865
Yes yvanzo, it's quite possibly the number of configured processes. I suspect the part of the issue is in the loop logic as the only way to stop a process once it gets stuck is a `kill -9`
