From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Rune Froysa <rune(dot)froysa(at)usit(dot)uio(dot)no> |
Cc: | pgsql-admin(at)postgresql(dot)org |
Subject: | Re: Server-side killing of database connection (7.3.4) |
Date: | 2004-02-15 05:34:39 |
Message-ID: | 5631.1076823279@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Rune Froysa <rune(dot)froysa(at)usit(dot)uio(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2004-02-15 05:46:06 | Re: Urgent!!!! Setting permissions on Views |
Previous Message | Tom Lane | 2004-02-15 05:26:59 | Re: forcing SSL |