From: | Vijaykumar Jain <vijaykumarjain(dot)github(at)gmail(dot)com> |
---|---|
To: | WR <wolle321(at)freenet(dot)de> |
Cc: | pgsql-general <pgsql-general(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Obsolete or dead serverconnections after reboot |
Date: | 2021-07-21 12:57:15 |
Message-ID: | CAM+6J96cyN1L_gGMNtA6r9kF-_-X6Ef-=td7zev8GFRWLhpPkg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
> Is there a way to avoid this (without restarting the service after every
> reboot). Is this a bug or a normal behavior?
>
I have less knowledge of windows.
https://www.enterprisedb.com/blog/postgresql-shutdown
Do you see shutdown/termination messages in the db logs or windows event
logs when the machine is rebooted?
You get the same pid and query, does it also has the same age( time since
it started),
I mean is the stats table updated with new data for stale connections or
they remain static.
Do you see the same issue when the machine is power cycled.
Maybe windows might be preserving the memory state on disk and reading it
back on reboot (like sleep) unless there are instructions to shutdown the
db server on reboot. Idk.
What are the state of the connections in pg_stat_activity abd process
explorer before and after reboot. The sockets exists and active, or are
residual in pg stats only.
From | Date | Subject | |
---|---|---|---|
Next Message | Vijaykumar Jain | 2021-07-21 13:14:52 | Re: Obsolete or dead serverconnections after reboot |
Previous Message | WR | 2021-07-21 10:49:06 | Obsolete or dead serverconnections after reboot |