News:

And we're back!

Main Menu

General issues

Started by Baron von Schtinkenbutt, July 09, 2013, 06:48:44 PM

Previous topic - Next topic

Josquius

We beat the database software. Mission accomplished.
██████
██████
██████

mongers

Quote from: Josquius on June 28, 2025, 02:05:34 PMWe beat the database software. Mission accomplished.

But, but,, , now I won't be able to post the traditional Fitness 202* in 5 months time.  :cry:
"We have it in our power to begin the world over again"

DGuller

How the hell could a thread ID hit the max number anyway?  That's a LOT of threads.

mongers

Quote from: DGuller on June 29, 2025, 04:37:16 PMHow the hell could a thread ID hit the max number anyway?  That's a LOT of threads.

I blame Timmay.  :whistle:
"We have it in our power to begin the world over again"

Crazy_Ivan80

Quote from: DGuller on June 29, 2025, 04:37:16 PMHow the hell could a thread ID hit the max number anyway?  That's a LOT of threads.

Time to order new guids?  :P

(Yes, we actually convinced a former colleague that would be necessary. One of the reasons he's former)

Baron von Schtinkenbutt

Quote from: DGuller on June 29, 2025, 04:37:16 PMHow the hell could a thread ID hit the max number anyway?  That's a LOT of threads.

I'm still debugging the problem, but it's very strange.  We have far fewer threads than an a MySQL unisigned mediumint can handle.  Like, three orders of magnitude fewer.  I have no idea how the autoincrement sequence hit max value, or exactly what I can do to adjust it without breaking things.

Maladict

It looks like topic numbers jump from 167xx to 16777xxx

edit: sometime around October 2023

Josquius

#607
Looks fixed.
Maladict's observation is the source?

edit- oh no, it isn't. I'm a liar.
██████
██████
██████

Baron von Schtinkenbutt

Thanks Maladict.  I just took a quick look, and yeah for some reason the autoincrement sequence suddenly jumped ahead by over 16.6MM.  There are a few dozen older topic IDs that are out-of-sequence as well.  I think I can write a small program to edit the out-of-range indexes and reset the sequence to the new point.

Baron von Schtinkenbutt

Well, it's not going to be so simple.  The database schema doesn't have a proper foreign key setup, so I need to manually identify every table that references topic IDs and edit those columns as well. :rolleyes:

grumbler

Quote from: Baron von Schtinkenbutt on July 01, 2025, 12:28:08 PMWell, it's not going to be so simple.  The database schema doesn't have a proper foreign key setup, so I need to manually identify every table that references topic IDs and edit those columns as well. :rolleyes:

We* don't always show it, but we are grateful for the time and effort and money you have put into keeping this forum alive.


*even if only "the royal we."
The future is all around us, waiting, in moments of transition, to be born in moments of revelation. No one knows the shape of that future or where it will take us. We know only that it is always born in pain.   -G'Kar

Bayraktar!

Jacob

Agreed. Much obliged  :hug:

HVC

Meh I think you're just alright.



:P kidding, I too greatly appreciate it.
Being lazy is bad; unless you still get what you want, then it's called "patience".
Hubris must be punished. Severely.