Skip site navigation (1) Skip section navigation (2)

Re: Template1 is locked when pgAdminIII is open

From: Andreas Pflug <pgadmin(at)pse-consulting(dot)de>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Dave Page <dpage(at)vale-housing(dot)co(dot)uk>,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 18:04:55
Message-ID: 41FE7347.4020404@pse-consulting.de (view raw or flat)
Thread:
Lists: pgsql-bugs
Tom Lane wrote:
> "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk> writes:
> 
>>Tom Lane wrote:
>>
>>>I think the real answer is something more along the lines of 
>>>"don't run two copies of pgAdmin at once".
> 
> 
>>He might not be. pgAdmin uses a master connection (normally to
>>template1) and one connection to each database browsed (minus the master
>>connection which is reused). However, each SQL Query window opened will
>>also open a new connection to the currently selected database, which is
>>what might have happened in this case. Of course, the easy answer is to
>>close any SQL windows in template1 as well...
> 
> 
> Hmm.  Would it be possible to teach pgAdmin to close extra connections
> to template1 whenever it's doing CREATE DATABASE?

If those connections were guaranteed to be idle, we wouldn't need them. 
They are independent windows, so we can't kill the conn.


Regards,
Andreas

In response to

pgsql-bugs by date

Next:From: Matthew WakelingDate: 2005-01-31 18:19:24
Subject: Bad planner decision in Postgres
Previous:From: Tom LaneDate: 2005-01-31 18:04:21
Subject: Re: Template1 is locked when pgAdminIII is open

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group