I have a db structure that looks somewhat like this:

client (id, ... other fields)
client_stats (client_id references client(id), ...other fields)

I have also configured the client_stats to be auto-deleted when the client gets deleted.

A client will have many (tens of thousands) of such client stats.
The issue I am facing is that when I delete the client, i run into a

fatal error: thread exhaustion

which takes down my server. here the error details:

`runtime: program exceeds 10000-thread limit
fatal error: thread exhaustion

runtime stack:
runtime.throw({0x212ac67?, 0x598d1ff970?})
C:/Users/Administrator/go/pkg/mod/golang.org/toolchain@v0.0.1-go1.24.1.windows-amd64/src/runtime/panic.go:1101 +0x4d fp=0x598d1ff970 sp=0x598d1ff940 pc=0xe636ad
runtime.checkmcount()
C:/Users/Administrator/go/pkg/mod/golang.org/toolchain@v0.0.1-go1.24.1.windows-amd64/src/runtime/proc.go:921 +0x8e fp=0x598d1ff998 sp=0x598d1ff970 pc=0xe3436e
runtime.mReserveID()
C:/Users/Administrator/go/pkg/mod/golang.org/toolchain@v0.0.1-go1.24.1.windows-amd64/src/runtime/proc.go:937 +0x2f fp=0x598d1ff9c0 sp=0x598d1ff998 pc=0xe343af
runtime.startm(0xc000072a08?, 0x0, 0x0)
C:/Users/Administrator/go/pkg/mod/golang.org/toolchain@v0.0.1-go1.24.1.windows-amd64/src/runtime/proc.go:2987 +0x112 fp=0x598d1ffa10 sp=0x598d1ff9c0 pc=0xe37fd2
runtime.handoffp(0x7ffaffffffff?)
C:/Users/Administrator/go/pkg/mod/golang.org/toolchain@v0.0.1-go1.24.1.windows-amd64/src/runtime/proc.go:3036 +0x365 fp=0x598d1ffa38 sp=0x598d1ffa10 pc=0xe38505
runtime.retake(0x13e2567c972d4)
C:/Users/Administrator/go/pkg/mod/golang.org/toolchain@v0.0.1-go1.24.1.windows-amd64/src/runtime/proc.go:6310 +0x255 fp=0x598d1ffa98 sp=0x598d1ffa38 pc=0xe3fe55
runtime.sysmon()
C:/Users/Administrator/go/pkg/mod/golang.org/toolchain@v0.0.1-go1.24.1.windows-amd64/src/runtime/proc.go:6214 +0x39a fp=0x598d1ffb18 sp=0x598d1ffa98 pc=0xe3fa1a
runtime.mstart1()
C:/Users/Administrator/go/pkg/mod/golang.org/toolchain@v0.0.1-go1.24.1.windows-amd64/src/runtime/proc.go:1855 +0x9d fp=0x598d1ffb40 sp=0x598d1ffb18 pc=0xe3665d
runtime.mstart0()
C:/Users/Administrator/go/pkg/mod/golang.org/toolchain@v0.0.1-go1.24.1.windows-amd64/src/runtime/proc.go:1808 +0x6a fp=0x598d1ffb68 sp=0x598d1ffb40 pc=0xe365aa
runtime.mstart()
C:/Users/Administrator/go/pkg/mod/golang.org/toolchain@v0.0.1-go1.24.1.windows-amd64/src/runtime/asm_amd64.s:395 +0x5 fp=0x598d1ffb70 sp=0x598d1ffb68 pc=0xe69745

goroutine 1 gp=0xc0000021c0 m=nil [chan receive, 1 minutes]:
runtime.gopark(0x23e23600108?, 0x301000000000070?, 0xf8?, 0x98?, 0x23e23600108?)
C:/Users/Administrator/go/pkg/mod/golang.org/toolchain@v0.0.1-go1.24.1.windows-amd64/src/runtime/proc.go:435 +0xce fp=0xc000879d60 sp=0xc000879d40 pc=0xe637ce
runtime.chanrecv(0xc0000c91f0, 0x0, 0x1)
C:/Users/Administrator/go/pkg/mod/golang.org/toolchain@v0.0.1-go1.24.1.windows-amd64/src/runtime/chan.go:664 +0x445 fp=0xc000879dd8 sp=0xc000879d60 pc=0xe01de5
runtime.chanrecv1(0xc0000bea88?, 0x1?)
C:/Users/Administrator/go/pkg/mod/golang.org/toolchain@v0.0.1-go1.24.1.windows-amd64/src/runtime/chan.go:506 +0x12 fp=0xc000879e00 sp=0xc000879dd8 pc=0xe01972
github.com/pocketbase/pocketbase.(*PocketBase).Execute(0xc0001bf8b0)
C:/Users/Administrator/go/pkg/mod/github.com/pocketbase/pocketbase@v0.25.9/pocketbase.go:204 +0xf3 fp=0xc000879e58 sp=0xc000879e00 pc=0x1da5953
github.com/pocketbase/pocketbase.(*PocketBase).Start(0xc0001bf8b0)
C:/Users/Administrator/go/pkg/mod/github.com/pocketbase/pocketbase@v0.25.9/pocketbase.go:170 +0x88 fp=0xc000879e90 sp=0xc000879e58 pc=0x1da5828
main.main()
C:/funtech/server/ninjaserver-go/gameserver/gameserver.go:261 +0x872 fp=0xc000879f50 sp=0xc000879e90 pc=0x1db9932
runtime.main()
C:/Users/Administrator/go/pkg/mod/golang.org/toolchain@v0.0.1-go1.24.1.windows-amd64/src/runtime/proc.go:283 +0x27d fp=0xc000879fe0 sp=0xc000879f50 pc=0xe331bd
runtime.goexit({})
C:/Users/Administrator/go/pkg/mod/golang.org/toolchain@v0.0.1-go1.24.1.windows-amd64/src/runtime/asm_amd64.s:1700 +0x1 fp=0xc000879fe8 sp=0xc000879fe0 pc=0xe6b801

... and so on
`

Running this with
Pocketbase v0.25.9
go 1.24.1
Windows Server 2022

(!!) I could NOT replicate this on WSL2