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

From: Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Oleg Bartunov <oleg(at)sai(dot)msu(dot)su>, hackers(at)postgreSQL(dot)org
Subject: Re: [HACKERS] destroydb doesn't close connection with client (httpd <-> pg)
Date: 1999-06-13 00:54:16
Message-ID: 199906130054.UAA15694@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


Added to TODO.

> 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
>
>

--
Bruce Momjian | http://www.op.net/~candle
maillist(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 1999-06-13 00:57:37 Re: [HACKERS] destroydb doesn't close connection with client (httpd <-> pg)
Previous Message Tatsuo Ishii 1999-06-13 00:10:17 Re: [HACKERS] Re: [PORTS] Patch for m68k architecture