Thanks for your answer! I would like to kill only a postgres session not postmaster. The table pg_session indicates the pid of the wrong session but kill -INT <pid> didn't stop this session.
pg_ctl works fine when i want to stop postmaster with the argument '-m immediate stop' ----Message d'origine---- >Date: Wed, 27 Oct 2004 10:11:16 +0100 >De: Richard Huxton <[EMAIL PROTECTED]> >A: [EMAIL PROTECTED] >Copie à: [EMAIL PROTECTED] >Sujet: Re: [GENERAL] > >[EMAIL PROTECTED] wrote: >> Hello ! >> >> To kill a session i used KILL -INT <PID>. >> >> This command wasn't successfull. The processus is still here when a >> 'ps ax' or a 'select * from pg_stat_activity' >> >> Is there an other way to kill this process only because a web server >> 24/7 use postgres and cannot stop postgresql now. > > From the manuals: >To terminate the postmaster normally, the signals SIGTERM, SIGINT, or >SIGQUIT can be used. The first will wait for all clients to terminate >before quitting, the second will forcefully disconnect all clients, and >the third will quit immediately without proper shutdown, resulting in a >recovery run during restart. > >The utility command pg_ctl can be used to start and shut down the >postmaster safely and comfortably. > >Does pg_ctl do anything for you? > >-- > Richard Huxton > Archonet Ltd > >---------------------------(end of broadcast)--------------------------- >TIP 6: Have you searched our list archives? > > http://archives.postgresql.org > > ---------------------------(end of broadcast)--------------------------- TIP 7: don't forget to increase your free space map settings
