On Thu, Feb 25, 2021 at 5:36 PM dbatoCloud Solution
<[hidden email]> wrote:
> Someone help on the killing the user session. I tried to use it but still unable to kill it and no blocking session.
> Is there any other way to kill session?
If you're still using Aurora, you'll need to check its documentation
or ask its support as the behavior of those functions may be different
than community postgres.
Otherwise, you'll need to provide more information. Can you show the
related rows in pg_stat_activity, the result when you tried to use
those functions and related postgres logs if any.
On Thu, 25 Feb 2021, 3:06 pm dbatoCloud Solution, <[hidden email]> wrote:
Someone help on the killing the user session. I tried to use it but still unable to kill it and no blocking session.
Is there any other way to kill session?
Interested to see what is happening based on the output of pg_stat_activity. Is that some session that is connecting to a foreign server using some FDW ?
Also, never attempt to kill a process using kill -9 as it may crash your PostgreSQL cluster with the following message.
WARNING: terminating connection because of crash of another server process
DETAIL: The postmaster has commanded this server process to roll back the
current transaction and exit, because another server process exited
abnormally and possibly corrupted shared memory.
HINT: In a moment you should be able to reconnect to the database and
repeat your command.
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: Succeeded.