> Tomasz Ostrowski wrote:
>
>> The database would get an error on the connection socket only after it tries to read or write to it next time. But
itdoes not try to do this - it's busy counting those quarks until statement_timeout is reached.
>>
>
I found relevant patch from postgrespro on commitfest: https://commitfest.postgresql.org/21/1882/
--
Dmitry Vasiliev