| From: | Sergey Shinderuk <s(dot)shinderuk(at)postgrespro(dot)ru> |
|---|---|
| To: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Cc: | Alexander Lakhin <exclusion(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Lars Kanis <lars(at)greiz-reinsdorf(dot)de>, Thomas Munro <thomas(dot)munro(at)gmail(dot)com> |
| Subject: | Re: Windows: Wrong error message at connection termination |
| Date: | 2022-01-14 23:15:25 |
| Message-ID: | eb2c816f-ea28-796b-95b1-0dd54df54434@postgrespro.ru |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 14.01.2022 13:01, Sergey Shinderuk wrote:
> Unexpectedly, this changes the error message:
>
> postgres=# set idle_session_timeout = '1s';
> SET
> postgres=# select 1;
> could not receive data from server: Software caused connection
> abort (0x00002745/10053)
For the record, after more poking I realized that it depends on timing.
By injecting delays I can get any of the following from libpq:
* could not receive data from server: Software caused connection abort
* server closed the connection unexpectedly
* no connection to the server
> Should we handle ECONNABORTED similarly to ECONNRESET in pqsecure_raw_read?
So this doesn't make sense anymore.
Sorry for the noise.
--
Sergey Shinderuk https://postgrespro.com/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2022-01-14 23:34:11 | Re: Adding CI to our tree |
| Previous Message | Tom Lane | 2022-01-14 22:51:52 | Re: Why is src/test/modules/committs/t/002_standby.pl flaky? |