From: | Dmitry Vasilyev <d(dot)vasilyev(at)postgrespro(dot)ru> |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Postgres service stops when I kill client backend on Windows |
Date: | 2015-10-09 09:52:21 |
Message-ID: | 1444384341.1256.9.camel@postgrespro.ru |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
I’ve started PostgreSQL server on Windows and then I kill client
backend’s process by taskkill the service was stopped:
postgres=# select pg_backend_pid();
pg_backend_pid
----------------
1976
postgres=# \! taskkill /pid 1976 /f
SUCCESS: The process with PID 1976 has been terminated.
postgres=# select 1;
server closed the connection unexpectedly
This probably means the server terminated abnormally
before or while processing the request.
The connection to the server was lost. Attempting reset: Failed.
!>
If I kill backend’s process on Linux then service not failing. So
what’s the problem? Why PostgreSQL is so strange on Windows?
------
Dmitry Vasilyev
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Company
From | Date | Subject | |
---|---|---|---|
Next Message | Etsuro Fujita | 2015-10-09 10:05:51 | Re: Foreign join pushdown vs EvalPlanQual |
Previous Message | Etsuro Fujita | 2015-10-09 09:41:18 | Re: Hooking at standard_join_search (Was: Re: Foreign join pushdown vs EvalPlanQual) |