Re: Template1 is locked when pgAdminIII is open

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk>
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 16:40:02
Message-ID: 20247.1107189602@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

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

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Andreas Pflug 2005-01-31 16:53:21 Re: Template1 is locked when pgAdminIII is open
Previous Message Tom Lane 2005-01-31 16:21:31 Re: BUG #1440: ecpg seg faults