Search Postgresql Archives

Re: postgres process got stuck in "notify interrupt waiting" status

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Aleksey Tsalolikhin <atsaloli.tech@xxxxxxxxx> wrote:
 
> Why will it kill all your other sessions too?  Isn't there a
> separate backend process for each session?
 
When stopped that abruptly, the process has no chance to clean up
its pending state in shared memory.  A fresh copy of shared memory
is needed, so it is necessary to effectively do an immediate restart
on the whole PostgreSQL instance.
 
-Kevin


-- 
Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]
  Powered by Linux