| From: | "Heikki Linnakangas" <heikki(at)enterprisedb(dot)com> |
|---|---|
| To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | "Gregory Stark" <stark(at)enterprisedb(dot)com>, "Michael Fuhr" <mike(at)fuhr(dot)org>, "Postgres" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: DROP DATABASE always seeing database in use |
| Date: | 2008-08-04 15:55:29 |
| Message-ID: | 48972671.50505@enterprisedb.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Tom Lane wrote:
> Gregory Stark <stark(at)enterprisedb(dot)com> writes:
>> "Michael Fuhr" <mike(at)fuhr(dot)org> writes:
>>> Are any prepared transactions still open?
>
>> Uh, yes, I did notice that but didn't put two and two together. That does make
>> sense now that you mention it.
>
> I've been bit by that too, and so have other people. Maybe it'd be
> worth the trouble to improve the message so that it explicitly tells you
> when there are prepared transactions blocking the DROP.
Yes, that should be easy enough.
> Another possibility is to let the DROP automatically roll back the
> conflicting prepared xacts, but that seems a bit dangerous.
Yeah, the prepared xact might have modified shared catalogs, for example.
--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2008-08-04 16:09:51 | Re: DROP DATABASE always seeing database in use |
| Previous Message | Tom Lane | 2008-08-04 15:42:10 | Re: DROP DATABASE always seeing database in use |