AlexDyukov
AlexDyukov
auth_query and nothing more. Does system worker keep connections without any frees? at start: ``` 1 2022-06-20T11:13:22Z info [none none] (stats) clients 0 1 2022-06-20T11:13:22Z info [none none] (stats) worker[0]:...
Not true in general You can rewrite response writer after next call (see [my example](https://github.com/alexdyukov/compresshandler/blob/master/fasthttp.go#L75)), but streams or early flush() breaks this logic and atm i dont know how to...
Thanks, @reshke . It works. But current master still throws segfault. Is there any instruction for core dump my container? P.S. You can reproduce it with toward configs: `PGPASSWORD=secret pgbench...
@reshke now it doesnt segfault, but pool_size on auth querys in some cases throws failed to make auth_query errors in logs like in screenshot. When i disable it with pool_size...
@reshke Nope, the feature has a different description: https://github.com/yandex/odyssey/blob/master/documentation/configuration.md#pool_size-integer `Clients are put in a wait queue, when all servers are busy.` and: ``` pool_timeout integer Server pool wait timeout. Time...
Still leaks: ``` found unexpected goroutines: [Goroutine 83 in state chan receive, with github.com/testcontainers/testcontainers-go.(*Reaper).connect.func1 on top of the stack: github.com/testcontainers/testcontainers-go.(*Reaper).connect.func1() /home/user/gopath/pkg/mod/github.com/testcontainers/[email protected]/reaper.go:539 +0xee created by github.com/testcontainers/testcontainers-go.(*Reaper).connect in goroutine 33 /home/user/gopath/pkg/mod/github.com/testcontainers/[email protected]/reaper.go:534 +0x1af...
@mdelapenya I dont know how to test main branch. I do benchmark on tagged 0.38.0: ``` $ grep 'testcontainer\|goleak' go.* && go version && cat example_test.go && go test -timeout...