Thread: Server-side killing of database connection (7.3.4)

I need to kill a connected database user.  I'm able to find the pid
associated with the troublesome user.  However, if I try killing the
process with any of INT, TERM or QUIT, all connected database users
get the message:

   WARNING:  Message from PostgreSQL backend:
           The Postmaster has informed me that some other backend
           died abnormally and possibly corrupted shared memory.
           I have rolled back the current transaction and am
           going to terminate your database system connection and exit.
           Please reconnect to the database system and repeat your query.

Is it possible to kill a connected user without shuting down the
database?  I.e. something like "alter system kill session" in oracle.

Regards,
Rune Frøysa

I know this isn't strictly a postgresql question, but I'm sure it applies to
others out there using psql.  If I am working in psql from SSH and switch to
another window, it seems that there is a very short window of time before
the window freezes and doesn't allow any more input.  Does anyone know how
to change the setting that controls how much time the window can remain
without input before it shuts down?

Thanks,
Jeremy

Rune Froysa <rune.froysa@usit.uio.no> writes:
> I need to kill a connected database user.  I'm able to find the pid
> associated with the troublesome user.  However, if I try killing the
> process with any of INT, TERM or QUIT, all connected database users
> get the message:

>    WARNING:  Message from PostgreSQL backend:
>            The Postmaster has informed me that some other backend
>            died abnormally and possibly corrupted shared memory.
>            I have rolled back the current transaction and am
>            going to terminate your database system connection and exit.
>            Please reconnect to the database system and repeat your query.

Better take another look at how you're doing that kill.  It is not
sending the signal number you think it is.

            regards, tom lane

"Jeremy Smith" <jer@highboard.com> writes:
> I know this isn't strictly a postgresql question, but I'm sure it applies to
> others out there using psql.  If I am working in psql from SSH and switch to
> another window, it seems that there is a very short window of time before
> the window freezes and doesn't allow any more input.

Never heard of such a problem before.  What's your environment, and
would you give a more complete description of the problem?

            regards, tom lane

Do you use  PuTTy as the ssh client? If yes then here you are ,it
is the connection problem .i have it all the time and did not found
what to do with.Actually that is not only putty problem ,but for
example linux ssh client at least does not just freeze - it says
something like 'connection timeout'.Just as a proof that this
is an ssh problem and not postgres - i have 2 servers with the
same config but on diff networks - one neither have a freeze while
the other all the time.
Evgeny
On Sun, 15 Feb 2004 11:56:16 -0500, Tom Lane <tgl@sss.pgh.pa.us> wrote:

> "Jeremy Smith" <jer@highboard.com> writes:
>> I know this isn't strictly a postgresql question, but I'm sure it
>> applies to
>> others out there using psql.  If I am working in psql from SSH and
>> switch to
>> another window, it seems that there is a very short window of time
>> before
>> the window freezes and doesn't allow any more input.
>
> Never heard of such a problem before.  What's your environment, and
> would you give a more complete description of the problem?
>
>             regards, tom lane
>
> ---------------------------(end of broadcast)---------------------------
> TIP 1: subscribe and unsubscribe commands go to majordomo@postgresql.org