At 08:35 13/11/01 +0000, you wrote:
>In pgAdmin II there is a long running bug that I can't
>resolve that prevents dropping a database because I can't persuade *all*
>connections to the specified database to close.

Dear all,

The same problem arises when working in psql after the closing of Php 
socket connections.
I have to do a 'service postgresql restart' server-side, and then psql 
template1 < drop database xxxx;

Does anyone know a simpler solution?

Cheers,
Jean-Michel

Tue, 13 Nov 2001 10:33:08 +0100
Jean-Michel POURE <jm.poure@freesurf.fr>
Re: Last inserted id 
I believe that in the release notes for the most recent version, it states
that this problem is known and can't really be worked around.

Chris

> -----Original Message-----
> From: pgsql-hackers-owner@postgresql.org
> [mailto:pgsql-hackers-owner@postgresql.org]On Behalf Of Jean-Michel
> POURE
> Sent: Tuesday, 13 November 2001 5:33 PM
> To: pgsql-odbc@postgresql.org
> Cc: pgsql-hackers@postgresql.org
> Subject: Re: [HACKERS] [ODBC] Last inserted id
>
>
> At 08:35 13/11/01 +0000, you wrote:
> >In pgAdmin II there is a long running bug that I can't
> >resolve that prevents dropping a database because I can't persuade *all*
> >connections to the specified database to close.
>
> Dear all,
>
> The same problem arises when working in psql after the closing of Php
> socket connections.
> I have to do a 'service postgresql restart' server-side, and then psql
> template1 < drop database xxxx;
>
> Does anyone know a simpler solution?
>
> Cheers,
> Jean-Michel
>
> ---------------------------(end of broadcast)---------------------------
> TIP 3: if posting/reading through Usenet, please send an appropriate
> subscribe-nomail command to majordomo@postgresql.org so that your
> message can get through to the mailing list cleanly
>


Wed, 14 Nov 2001 09:27:18 +0800
"Christopher Kings-Lynne" <chriskl@familyhealth.com.au>
Re: [HACKERS] Last inserted id 