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 16:53:21
Message-ID: 41FE6281.7010907@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:
> 
>>pgAdmin uses template1 by default as it is the only accessible database
>>that we can be sure will exist. There are 2 solutions to your problem:
> 
> 
>>1) Change your pgAdmin connection to use a different default database.
> 
> 
>>2) Select a different database to use as the template when creating a
>>new one.
> 
> 
> He shouldn't really be getting that error though, as CREATE DATABASE
> only complains if there is another connection *besides your own* to
> the template database.
> 
> I think the real answer is something more along the lines of "don't run
> two copies of pgAdmin at once".

Which is still not the whole truth.
pgAdmin may open more connections to the "initial database", e.g. to 
show the server status.

So the advice is "don't use the template1 database for pgadmin 
connections if you're creating databases frequently"

Regards,
Andreas

In response to

pgsql-bugs by date

Next:From: Dave PageDate: 2005-01-31 16:59:54
Subject: Re: Template1 is locked when pgAdminIII is open
Previous:From: Tom LaneDate: 2005-01-31 16:40:02
Subject: Re: Template1 is locked when pgAdminIII is open

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