select pg_cancel_backend(procpid) solved half of my problem...at least it terminated the query for that user... but it is still holding a user connection in IDLE state....If I have too many of those, Postgres may run of out of user connections....
I already knew how to kill a connection if the connection is from the local host. But I have many remote connections coming from different machines... hard to kill with unix command "kill"... One time, I was testing to kill a particular connection on a testing machine, the entrie Postgres was brought down....
I need to find a safer, cleaner way to disconnect a user from Postgres when needed.
Thanks a lot,
Scott Marlowe <scott.marlowe@gmail.com> wrote:
On 10/15/07, Jessica Richard wrote:
> Thanks a lot!
>
> "select pg_cancel_backend(procpid) " can end the current query for that
> user, but then this connection becomes IDLE, still connected.
>
> Is there a command for me to totally disconnect a user by procpid? Some
> times, I need to kick out a particular Postgres user completely.
From the command line on the server you can issue a kill to do
that. From within pgsql you'd need to write a function in an
untrusted language to pull it off.
---------------------------(end of broadcast)---------------------------
TIP 2: Don't 'kill -9' the postmaster
Don't let your dream ride pass you by.
Make it a reality with Yahoo! Autos.