Search Postgresql Archives
Re: (Never?) Kill Postmaster?
[
Date Prev
][
Date Next
][
Thread Prev
][
Thread Next
][
Date Index
][
Thread Index
]
To
: "Stefan Schwarzer" <
stefan.schwarzer@xxxxxxxxxxxx
>
Subject
: Re: (Never?) Kill Postmaster?
From
: "Vyacheslav Kalinin" <
vka@xxxxxxxx
>
Date
: Wed, 24 Oct 2007 10:06:08 +0400
Cc
:
pgsql-general@xxxxxxxxxxxxxx
In-reply-to
: <
3C786E4E-E2AB-4C55-ABCB-05F60E8860A6@xxxxxxxxxxxx
>
Postgres starts separate process for each connection and you can just `kill` (not `kill -9`) the unwanted process. Or you can do `select pg_cancel_backend(pid)` from another session.
[
Date Prev
][
Date Next
][
Thread Prev
][
Thread Next
][
Date Index
][
Thread Index
]
References
:
(Never?) Kill Postmaster?
From:
Stefan Schwarzer
Prev by Date:
postgresql in PHP
Next by Date:
postgres bash prompt error while user creation
Previous by thread:
Re: (Never?) Kill Postmaster?
Next by thread:
deadlock detected, only selects (not select-for-update)
Index(es):
Date
Thread
[Index of Archives]
[Postgresql Jobs]
[Postgresql Admin]
[Postgresql Performance]
[Linux Clusters]
[PHP Home]
[PHP on Windows]
[Kernel Newbies]
[PHP Classes]
[PHP Books]
[PHP Databases]
[Postgresql & PHP]
[Yosemite]
