Howard Cole wrote:
> > Wow, yea, I see that now, but it is alone a paragraph above. I updated
> > the text to:
> >
> >The program provides a convenient
> >interface for sending these signals to shut down the server.
> >Alternatively, you can send the signal directly using
> >kill
Bruce Momjian wrote:
Alvaro Herrera wrote:
Bruce Momjian wrote:
Alvaro Herrera wrote:
Huh, why is it awkward?
Alternatively, you can send the signal directly using kill
(or pg_ctl kill TERM [process id]).
I think we should mention Windows in there somewhere, b
Alvaro Herrera wrote:
> Bruce Momjian wrote:
> > Alvaro Herrera wrote:
>
> > > Huh, why is it awkward?
> > >
> > > Alternatively, you can send the signal directly using kill
> > > (or pg_ctl kill TERM [process id]).
> >
> > I think we should mention Windows in there somewhere, because it
Bruce Momjian wrote:
> Alvaro Herrera wrote:
> > Huh, why is it awkward?
> >
> > Alternatively, you can send the signal directly using kill
> > (or pg_ctl kill TERM [process id]).
>
> I think we should mention Windows in there somewhere, because it isn't
> "alternatively" on Windows.
Ac
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
> > > >
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
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
>
Thomas H. wrote:
wasn't the OP asking for a way to kill active connections to a db?
afaik pgAdmin3 does provide this functionality:
pgadmin3 > tools > server status
there you can easily terminate connections & transactions to a
particular db. works pretty well in my test, i can kill active
c
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 v
wasn't the OP asking for a way to kill active connections to a db?
afaik pgAdmin3 does provide this functionality:
pgadmin3 > tools > server status
there you can easily terminate connections & transactions to a
particular db. works pretty well in my test, i can kill active
connections and dro
Thomas H. wrote:
On Tue, Dec 11, 2007 at 05:50:46PM -0500, Tom Lane wrote:
Alvaro Herrera <[EMAIL PROTECTED]> writes:
Howard Cole wrote:
I take it from the lack of response that nobody knows how to kill
a connection from the postgresql side on windows?
You can't, short of sending a signal t
Dann Corbit wrote:
What happens if you disable the net card on your server machine?
Hi Dann,
The connection is from IIS worker process running on the same machine.
My problem is that I want to disable connections for a single database.
Disabling the pgsql service or disabling the card (can
On Tue, Dec 11, 2007 at 05:50:46PM -0500, Tom Lane wrote:
Alvaro Herrera <[EMAIL PROTECTED]> writes:
Howard Cole wrote:
I take it from the lack of response that nobody knows how to kill a
connection from the postgresql side on windows?
You can't, short of sending a signal to the process or r
On Tue, Dec 11, 2007 at 05:50:46PM -0500, Tom Lane wrote:
> Alvaro Herrera <[EMAIL PROTECTED]> writes:
> > Howard Cole wrote:
> >> I take it from the lack of response that nobody knows how to kill a
> >> connection from the postgresql side on windows?
>
> > You can't, short of sending a signal to
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:pgsql-general-
> [EMAIL PROTECTED] On Behalf Of Howard Cole
> Sent: Tuesday, December 11, 2007 2:21 PM
> To: 'PgSql General'
> Subject: Re: [GENERAL] Killing a session in windows
>
> Hello everyon
Alvaro Herrera <[EMAIL PROTECTED]> writes:
> Howard Cole wrote:
>> I take it from the lack of response that nobody knows how to kill a
>> connection from the postgresql side on windows?
> You can't, short of sending a signal to the process or restarting the
> service.
Which you can do, no? I th
Howard Cole wrote:
> Hello everyone,
>
> I take it from the lack of response that nobody knows how to kill a
> connection from the postgresql side on windows?
You can't, short of sending a signal to the process or restarting the
service.
--
Alvaro Herrera Valdivia, Chile ICBM: S 39ยบ 49'
Hello everyone,
I take it from the lack of response that nobody knows how to kill a
connection from the postgresql side on windows? Is there another way
around this? In the end I created another database and changed all my
code to use the new database, the original database is still there (now
Hi,
I've written about this problem before and thanks to Bill Bartlett and
Richard Huxton for previous replies, but the problem keeps coming up...
I'm running postgresql V8.2.5 (I think!) on W2K3 Server and occasionally
I want to rebuild a database. However I cannot drop the database because
Of Howard Cole
Sent: Thursday, November 29, 2007 5:55 AM
To: 'PgSql General'
Subject: [GENERAL] Killing a session on windows
I have a database I want to drop on a windows server. Unfortunately I
cannot restart postgres because it is running several live database.
To kill the offending
Howard Cole wrote:
I have a database I want to drop on a windows server. Unfortunately I
cannot restart postgres because it is running several live database.
To kill the offending session, I tried select * from pg_stat_activity to
find the PID of the session, and then tried to kill it with c
I have a database I want to drop on a windows server. Unfortunately I
cannot restart postgres because it is running several live database.
To kill the offending session, I tried select * from pg_stat_activity to
find the PID of the session, and then tried to kill it with command line:
taskk
Even better. Thanks =).
On Sat, 21 Aug 2004 20:14:53 -0400, Tom Lane <[EMAIL PROTECTED]> wrote:
>
>
> Vitaly Belman <[EMAIL PROTECTED]> writes:
> > Is there a way to kill a session in PostrgeSQL? I ran a bad query by
> > mistake and I don't want to shut the whole database just to quit using
> >
Vitaly Belman <[EMAIL PROTECTED]> writes:
> Is there a way to kill a session in PostrgeSQL? I ran a bad query by
> mistake and I don't want to shut the whole database just to quit using
> the whole CPU.
ISTM what you really want is query cancel, not whole-session kill.
Try "kill -INT ".
variants, though.
HTH
Greg Williamson
DBA
GlobeXplorer LLC
-Original Message-
From: Vitaly Belman [mailto:[EMAIL PROTECTED]
Sent: Sat 8/21/2004 1:32 PM
To: [EMAIL PROTECTED]
Cc:
Subject:[GENERAL] Killing a session
Is there a way to kill a session in PostrgeSQL? I ran a bad
Is there a way to kill a session in PostrgeSQL? I ran a bad query by
mistake and I don't want to shut the whole database just to quit using
the whole CPU.
--
ICQ: 1912453
AIM: VitalyB1984
MSN: [EMAIL PROTECTED]
Yahoo!: VitalyBe
---(end of broadcast)---
26 matches
Mail list logo
