Re: [HACKERS] destroydb doesn't close connection with client (httpd <-> pg)

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Oleg Bartunov <oleg(at)sai(dot)msu(dot)su>
Cc: hackers(at)postgreSQL(dot)org
Subject: Re: [HACKERS] destroydb doesn't close connection with client (httpd <-> pg)
Date: 1999-06-12 20:04:30
Message-ID: 16850.929217870@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Oleg Bartunov <oleg(at)sai(dot)msu(dot)su> writes:
> I don't know is it DBI/DBD problem or backend must close
> all connections to DB when it destroyed.

You cannot destroy a DB while there are backends connected to it;
all hell breaks loose if you do. See thread "How to destroy your entire
Postgres installation" in pg-hackers in late Sept. 1998.

The correct fix is to add an interlock that prevents "destroydb" when
there are connected backends. I don't know just how that might be done,
however.

There should be a TODO item for this, but I don't see one:
* Prevent destroydb when there are backends active in that database

regards, tom lane

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Oleg Bartunov 1999-06-12 20:04:43 Re: [HACKERS] destroydb doesn't close connection with client (httpd <-> pg)
Previous Message Oliver Elphick 1999-06-12 20:02:06 Re: [HACKERS] Re: [PORTS] Patch for m68k architecture