> > Anyway, you can use `psql' to query the activity tables using something
> > like "SELECT procpid FROM pg_stat_activity WHERE datname = 'dbtodrop'"
> > and see which backend pids need to be killed, then use 'pg_ctl kill
> > signame pid' to kill them. A bit of powershell, cmd.exe, etc should do
>
On Apr 6, 1:34 pm, [EMAIL PROTECTED] (Craig Ringer) wrote:
> Kev wrote:
> > So I tried to do this in Perl, but for some reason neither
> > kill() nor Win32::Process::KillProcess() actually terminate the
> > threads.
>
> Threads? Each backend is a distinct process. I haven't the foggiest why
> they
Kev wrote:
> So I tried to do this in Perl, but for some reason neither
> kill() nor Win32::Process::KillProcess() actually terminate the
> threads.
Threads? Each backend is a distinct process. I haven't the foggiest why
they might be ignoring the signal, but then I'm very far from clueful
about
Hi everyone,
I'd like to drop a database to which users have idle connections. I'm
running pgsql 8.2 on win32, soon 8.3, using mod_perl2 and
connect_cached.
I know this issue has been brought up several times over the past few
years, but I don't quite understand the reason for it not being
suppo
