| From: | PG Bug reporting form <noreply(at)postgresql(dot)org> |
|---|---|
| To: | pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Cc: | sayanoruspai(at)gmail(dot)com |
| Subject: | BUG #17981: HY000 server closed the connection unexpectedly |
| Date: | 2023-06-19 11:52:16 |
| Message-ID: | 17981-984fdc9ec7e66b42@postgresql.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
The following bug has been logged on the website:
Bug reference: 17981
Logged by: Sayan Oruspay
Email address: sayanoruspai(at)gmail(dot)com
PostgreSQL version: 12.1
Operating system: Windows 10
Description:
I am writing an application that connects to the local database through
psqlodbc version 13.02. And when I manually stop my database service, I get
sqlstate HY000 and message 'server closed the connection unexpectedly ...'.
Should not it be something like 08S01? Also SQLGetConnectAttr(GetHandle(),
SQL_ATTR_CONNECTION_DEAD, &dead, SQL_IS_INTEGER, nullptr); does not produce
right answer and dead is returned equal to SQL_CD_FALSE.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | PG Bug reporting form | 2023-06-19 12:07:42 | BUG #17982: Inconsistent results of SELECT with CTE caused by subquery comparison |
| Previous Message | Richard Guo | 2023-06-19 10:21:43 | Re: BUG #17978: Unexpected error: "wrong varnullingrels (b) (expected (b 5)) for Var 6/2" triggered by JOIN |