From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
Cc: | Howard Cole <howardnews(at)selestial(dot)com>, "'PgSql General'" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Killing a session in windows |
Date: | 2007-12-17 13:45:30 |
Message-ID: | 200712171345.lBHDjU425483@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Alvaro Herrera wrote:
> Bruce Momjian wrote:
> > Howard Cole wrote:
> > >
> > > >>>> Which you can do, no? I thought pg_ctl's kill option was invented
> > > >>>> specifically to make this less painful on Windows.
> > > > I shall look into the pg_ctl options to see if the kill option does
> > > > what taskill cannot (thanks for the heads up on that)
> > > >
> > > Using
> > > $ pg_ctl kill TERM [pid]
> > > worked great. Since very few people seem to know about this, could I
> > > suggest making it more prominent in the server administration pages.
> >
> > Agreed. I have added the second sentence to our 8.3 beta docs:
> >
> > Alternatively, you can send the signal directly using <command>kill</>
> > (or <command>pg_ctl kill TERM [process id]</> on <productname>Windows</>).
> >
> > You can actually use pg_ctl kill on Unix too but it seems awkward to
> > suggest it in the existing sentence.
>
> Huh, why is it awkward?
>
> Alternatively, you can send the signal directly using <command>kill</>
> (or <command>pg_ctl kill TERM [process id]</>).
I think we should mention Windows in there somewhere, because it isn't
"alternatively" on Windows.
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://postgres.enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2007-12-17 13:56:11 | Re: Killing a session in windows |
Previous Message | Alvaro Herrera | 2007-12-17 13:43:14 | Re: Killing a session in windows |