pg.ddx.io pgsql-admin@postgresql.org mailing list archive
help / color / mirror / Atom feedServer-side killing of database connection (7.3.4)
2+ messages / 2 participants
[nested] [flat]
* Server-side killing of database connection (7.3.4)
@ 2004-02-13 09:11 Rune Froysa <rune.froysa@usit.uio.no>
2004-02-15 05:34 ` Re: Server-side killing of database connection (7.3.4) Tom Lane <tgl@sss.pgh.pa.us>
0 siblings, 1 reply; 2+ messages in thread
From: Rune Froysa @ 2004-02-13 09:11 UTC (permalink / raw)
To: pgsql-admin
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
^ permalink raw reply [nested|flat] 2+ messages in thread
* Re: Server-side killing of database connection (7.3.4)
2004-02-13 09:11 Server-side killing of database connection (7.3.4) Rune Froysa <rune.froysa@usit.uio.no>
@ 2004-02-15 05:34 ` Tom Lane <tgl@sss.pgh.pa.us>
0 siblings, 0 replies; 2+ messages in thread
From: Tom Lane @ 2004-02-15 05:34 UTC (permalink / raw)
To: Rune Froysa <rune.froysa@usit.uio.no>; +Cc: pgsql-admin
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
^ permalink raw reply [nested|flat] 2+ messages in thread
end of thread, other threads:[~2004-02-15 05:34 UTC | newest]
Thread overview: 2+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2004-02-13 09:11 Server-side killing of database connection (7.3.4) Rune Froysa <rune.froysa@usit.uio.no>
2004-02-15 05:34 ` Tom Lane <tgl@sss.pgh.pa.us>
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox