Henrique Carvalho
Henrique Carvalho
I meant a timer for when a client does not respond. But I get what you're saying. I noticed that this fails for some connections that enter the `pgagroal_connection_get_pid`. How...
> [@decarv](https://github.com/decarv) We can def not have a "pgagroal -> client" timer in the performance pipeline... Is it sort of `disconnect_client` you are thinking of ? See https://github.com/agroal/pgagroal/blob/master/doc/CONFIGURATION.md "Danger zone"...
I could fix it, but maybe you can point me to the right direction here. What should be happening?
Have to build and test this... @Userfrom1995 have you had the opportunity?
Hi, Reporting my findings. First, `pgagroal_write_discard_all` the reply->kind that I'm reading has value 'e', not 'E'. This passes 0 to the caller and the kill_connection is never reached in `pgagroal_return_connection`....
> `'e'` ? There is no such message - https://www.postgresql.org/docs/devel/protocol-message-formats.html I will investigate this better. > Second, when failure happens, the last message is sent by pgagroal to the server,...
You can cancel pgbench run before the client sends a Q to the server or after. If you cancel it before, the recovery is fine. If it is after, connections...
I believe this can be closed. @fluca1978, can you confirm?
No, cancelling the pgbench run should leave no connections hanging as before. Here works fine… On Mon, 19 May 2025 at 12:39 Luca Ferrari ***@***.***> wrote: > *fluca1978* left a...