Re: 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
Import Notes
Reply to msg id not found: AA30E7BCCA5C1D4E88A231900F8325C00C7D@dogbert.vale-housing.co.uk
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
Show quoted text
-----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 idAt 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