Re: [BUGS] Template1 is locked when pgAdminIII is open

2005-01-31 Thread Mehul Doshi-A20614
the way it refreshes when you drop a db. Thanks & Regards, Mehul -Original Message- From: Tom Lane [mailto:[EMAIL PROTECTED] Sent: Monday, January 31, 2005 10:10 PM To: Dave Page Cc: Mehul Doshi-A20614; pgsql-bugs@postgresql.org Subject: Re: [BUGS] Template1 is locked when pgAdminI

Re: [BUGS] Template1 is locked when pgAdminIII is open

2005-01-31 Thread Dave Page
> -Original Message- > From: Tom Lane [mailto:[EMAIL PROTECTED] > Sent: 31 January 2005 17:29 > To: Dave Page > Cc: Mehul Doshi-A20614; pgsql-bugs@postgresql.org > Subject: Re: [BUGS] Template1 is locked when pgAdminIII is open > > Hmm. Would it be possible t

Re: [BUGS] Template1 is locked when pgAdminIII is open

2005-01-31 Thread Tom Lane
Alvaro Herrera <[EMAIL PROTECTED]> writes: > On Mon, Jan 31, 2005 at 12:29:12PM -0500, Tom Lane wrote: >> Of course, sooner or later we should fix the underlying locking >> mechanism so we don't have to have this constraint, but I'm not sure >> when that will happen. > What needs to be locked? So

Re: [BUGS] Template1 is locked when pgAdminIII is open

2005-01-31 Thread Andreas Pflug
Tom Lane wrote: "Dave Page" 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 conn

Re: [BUGS] Template1 is locked when pgAdminIII is open

2005-01-31 Thread Alvaro Herrera
On Mon, Jan 31, 2005 at 12:29:12PM -0500, Tom Lane wrote: > Of course, sooner or later we should fix the underlying locking > mechanism so we don't have to have this constraint, but I'm not sure > when that will happen. Hm, can we use LockSharedObject? It's on my shared dependency patch. What n

Re: [BUGS] Template1 is locked when pgAdminIII is open

2005-01-31 Thread Tom Lane
"Dave Page" 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 > connec

Re: [BUGS] Template1 is locked when pgAdminIII is open

2005-01-31 Thread Dave Page
> -Original Message- > From: Tom Lane [mailto:[EMAIL PROTECTED] > Sent: 31 January 2005 16:40 > To: Dave Page > Cc: Mehul Doshi-A20614; pgsql-bugs@postgresql.org > Subject: Re: [BUGS] Template1 is locked when pgAdminIII is open > > "Dave Page" wri

Re: [BUGS] Template1 is locked when pgAdminIII is open

2005-01-31 Thread Andreas Pflug
Tom Lane wrote: "Dave Page" 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 t

Re: [BUGS] Template1 is locked when pgAdminIII is open

2005-01-31 Thread Tom Lane
"Dave Page" 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

Re: [BUGS] Template1 is locked when pgAdminIII is open

2005-01-31 Thread Dave Page
> -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Mehul > Doshi-A20614 > Sent: 31 January 2005 12:58 > To: 'pgsql-bugs@postgresql.org' > Subject: [BUGS] Template1 is locked when pgAdminIII is open > > In the

[BUGS] Template1 is locked when pgAdminIII is open

2005-01-31 Thread Mehul Doshi-A20614
In the PostgreSQL RC-1, whenever we have the pgAdminIII open and try to create a database, it says that template1 is locked up and hence the database cannot be created. I believe it shouldn't lock it up and allow the database to be created. If this bug has already been raised and fixed in subse