From: | "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk> |
---|---|
To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | "Mehul Doshi-A20614" <mehul(at)motorola(dot)com>, <pgsql-bugs(at)postgresql(dot)org> |
Subject: | Re: Template1 is locked when pgAdminIII is open |
Date: | 2005-01-31 21:21:56 |
Message-ID: | E7F85A1B5FF8D44C8A1AF6885BC9A0E45287D8@ratbert.vale-housing.co.uk |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
> -----Original Message-----
> From: Tom Lane [mailto:tgl(at)sss(dot)pgh(dot)pa(dot)us]
> Sent: 31 January 2005 17:29
> To: Dave Page
> Cc: Mehul Doshi-A20614; pgsql-bugs(at)postgresql(dot)org
> Subject: Re: [BUGS] Template1 is locked when pgAdminIII is open
>
> Hmm. Would it be possible to teach pgAdmin to close extra connections
> to template1 whenever it's doing CREATE DATABASE?
Hmm, it's possible but not particularly friendly - it would stop any
ongoing user queries (not that there are likely to be many of those in
template1), and the server status window (which periodically selects
from pg_stat_activity among other things). I think it would be nicer for
pgAdmin to give a more helpful error message (in most cases it simply
passes on such messages as they come from the server).
Regards, Dave.
From | Date | Subject | |
---|---|---|---|
Next Message | m.woehling | 2005-01-31 23:55:16 | BUG #1453: NULLs in UNION query |
Previous Message | Greg Stark | 2005-01-31 19:35:58 | Re: [BUGS] Bug in create operator and/or initdb |